[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
That may be a simplistic example, but I hope that it at least gets a
point across: we do not relish the thought of many services being
defined that are minor variants of each other. Such variant can, and
should, be handled as parameter-driven response modifications. If not
all of the parameter-driven options are supported by a particular
service provider, that would be included in the "service directory".
While we want to have a fair degree of granularity, we also recognize
that there are natural groupings of services ... such as A and C, above.
We endorse efforts to identify these natural groupings and hierarchies.
But we would rather see more effort directed to establishing the
services rather than the grouping/hierarchy.
2.
For example, very few people would class updating dosage size on a
medication order as a sensible "enterprise service operation" but update
order (or update pharmacy order) would. At the same time "update medical
record" at an operation level is far too coarse grain to be reusable and
useful.
Principal Consultant
CSW Group Ltd
***********************************************
Registered Office and Contact Address:
4240 Nash Court
Oxford Business Park South
Oxford
OX4 2RU
Tel: +44/0 1865 337400 Fax: +44/0 1865 337433
Web: <http://www.csw.co.uk <http://www.csw.co.uk/> >
Registered in England No. 4198197
Legal Disclaimer: <http://www.csw.co.uk/disclaimer.htm>
***********************************************
------=_NextPart_000_0000_01C51347.8792D580
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1480" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>
<TABLE cellSpacing=3D0 cellPadding=3D3 width=3D"100%" bgColor=3D#c0c0c0 =
border=3D0>
<TBODY>
<TR>
<TD width=3D"10%"><FONT size=3D2><B>From:</B></FONT> </TD>
<TD id=3Dfrom colSpan=3D3><FONT size=3D2>Ann Wrightson=20
[SMTP:Ann.Wrightson@csw.co.uk] </FONT></TD></TR>
<TR>
<TD><FONT size=3D2><B>To:</B></FONT> </TD>
<TD id=3Dto colSpan=3D3><FONT size=3D2>servicesBOF@lists.hl7.org;=20
healthcare@omg.org </FONT></TD></TR>
<TR>
<TD><FONT size=3D2><B>Cc:</B></FONT> </TD>
<TD id=3Dcc colSpan=3D3><FONT size=3D2> </FONT></TD></TR>
<TR>
<TD></TD></TR>
<TR>
<TD><FONT size=3D2><B>Subject:</B></FONT> </TD>
<TD id=3Dsubject colSpan=3D3><FONT size=3D2>Service granularity - =
close of=20
action from last telecon </FONT></TD></TR>
<TR>
<TD><FONT size=3D2><NOBR><B>Sent:</B></NOBR> </FONT></TD>
<TD id=3Dsent width=3D"62%"><FONT size=3D2><NOBR>2/15/05 5:59=20
AM </NOBR></FONT><BR></TD>
<TD align=3Dright><FONT size=3D2><NOBR><B>Importance:</B></NOBR> =
</FONT></TD>
<TD id=3Dimportance align=3Dright><FONT =
size=3D2><NOBR>Normal </NOBR>=20
</FONT></TD></TR></TBODY></TABLE><!--- message text ----->
<TABLE cellSpacing=3D2 cellPadding=3D6 width=3D"100%" border=3D1>
<TBODY>
<TR id=3Dbody>
<TD vAlign=3Dtop width=3D"100%" bgColor=3Dwhite colSpan=3D2 =
height=3D300>
<P><FONT size=3D2>Putting together the gist of the two responses =
received,=20
with my own</FONT> <BR><FONT size=3D2>thoughts, then the =
granularity=20
required is such that services we define:</FONT> </P>
<P><FONT size=3D2>- correspond to recognizable service components =
from=20
a</FONT> <BR><FONT size=3D2>business/enterprise perspective (eg: =
is this=20
something that you might</FONT> <BR><FONT size=3D2>pay for? - =
maybe not one=20
at a time, but as a</FONT> <BR><FONT=20
size=3D2>service-of-doing-X-when-I-need-it)</FONT> <BR><FONT =
size=3D2>- are=20
the right size to be a comfortable unit of reuse (not too =
large,</FONT>=20
<BR><FONT size=3D2>not too small)</FONT> <BR><FONT size=3D2>- can =
be=20
characterized as usecases (user-to-system or =
system-to-system)</FONT>=20
<BR><FONT size=3D2>that play a clear role within (different =
national)=20
operational concepts</FONT> <BR><FONT size=3D2>or scenarios =
describing=20
system interoperability in healthcare </FONT><BR><FONT size=3D2>- =
have=20
internal structure that is suited to analysis for quality =
of</FONT>=20
<BR><FONT size=3D2>service, detailed requirements flowdown, =
etc.</FONT> </P>
<P><FONT size=3D2>Ann W.</FONT> </P>
<P><FONT size=3D2>Extracts from responses that give more =
detail:</FONT> </P>
<P><FONT size=3D2>1.</FONT> </P>
<P><FONT size=3D2>a service must provide a complete solution to at =
least one=20
business</FONT> <BR><FONT size=3D2>functional requirement. =
Conversely,=20
a service may provide complete</FONT> <BR><FONT size=3D2>solutions =
to=20
multiple business functional requirement only if those</FONT> =
<BR><FONT=20
size=3D2>requirements are direct extensions of one primary=20
requirement. For</FONT> <BR><FONT size=3D2>example, consider =
the=20
following as Services: </FONT></P>
<P><FONT size=3D2>=3D=3D>[A] Does individual have =
reports/records on file.=20
</FONT></P>
<P><FONT size=3D2>=3D=3D>[B] What type(s) of reports/records =
exist for the=20
individual. </FONT></P>
<P><FONT size=3D2>=3D=3D>[C] Retrieve reports/records for =
individual=20
</FONT></P>
<P><FONT size=3D2>=3D=3D>[D] Retrieve specific report/record =
for individual=20
</FONT></P>
<P><FONT size=3D2>From my/our point of view, services A and B are =
variants=20
and would be</FONT> <BR><FONT size=3D2>consolidated into one =
service with an=20
optional parameter requesting that</FONT> <BR><FONT size=3D2>the =
types of=20
records be included in the response. Similarly, C and =
D</FONT>=20
<BR><FONT size=3D2>are also variants that should be =
consolidated. =20
However, since the</FONT> <BR><FONT size=3D2>business function to =
determine=20
if an individual has reports/records on</FONT> <BR><FONT =
size=3D2>file is=20
distinct from the retrieval of those reports/records, we =
would</FONT>=20
<BR><FONT size=3D2>not consider retrieval as a direct extension of =
report of=20
existence ...</FONT> <BR><FONT size=3D2>A and C would remain as =
two distinct=20
services. </FONT></P>
<P><FONT size=3D2>That may be a simplistic example, but I hope =
that it at=20
least gets a</FONT> <BR><FONT size=3D2>point across: we do =
not relish=20
the thought of many services being</FONT> <BR><FONT =
size=3D2>defined that=20
are minor variants of each other. Such variant can, =
and</FONT>=20
<BR><FONT size=3D2>should, be handled as parameter-driven response =
modifications. If not</FONT> <BR><FONT size=3D2>all of the=20
parameter-driven options are supported by a particular</FONT> =
<BR><FONT=20
size=3D2>service provider, that would be included in the "service=20
directory". </FONT></P>
<P><FONT size=3D2>While we want to have a fair degree of =
granularity, we=20
also recognize</FONT> <BR><FONT size=3D2>that there are natural =
groupings of=20
services ... such as A and C, above.</FONT> <BR><FONT size=3D2>We =
endorse=20
efforts to identify these natural groupings and =
hierarchies.</FONT>=20
<BR><FONT size=3D2>But we would rather see more effort directed to =
establishing the</FONT> <BR><FONT size=3D2>services rather than =
the=20
grouping/hierarchy. </FONT></P>
<P><FONT size=3D2>2.</FONT> </P>
<P><FONT size=3D2>For example, very few people would class =
updating dosage=20
size on a</FONT> <BR><FONT size=3D2>medication order as a sensible =
"enterprise service operation" but update</FONT> <BR><FONT =
size=3D2>order=20
(or update pharmacy order) would. At the same time "update =
medical</FONT>=20
<BR><FONT size=3D2>record" at an operation level is far too coarse =
grain to=20
be reusable and</FONT> <BR><FONT size=3D2>useful. </FONT></P><BR>
<P><FONT size=3D2>Principal Consultant</FONT> <BR><FONT =
size=3D2>CSW Group=20
Ltd</FONT> <BR><FONT=20
size=3D2>***********************************************</FONT> =
<BR><FONT=20
size=3D2>Registered Office and Contact Address:</FONT> <BR><FONT =
size=3D2>4240=20
Nash Court</FONT> <BR><FONT size=3D2>Oxford Business Park =
South</FONT>=20
<BR><FONT size=3D2>Oxford</FONT> <BR><FONT size=3D2>OX4 2RU</FONT> =
<BR><FONT=20
size=3D2>Tel: +44/0 1865 337400 Fax: +44/0 1865 =
337433</FONT>=20
<BR><FONT size=3D2>Web: <<A href=3D"http://www.csw.co.uk/"=20
target=3D_blank>http://www.csw.co.uk</A>></FONT> </P>
<P><FONT size=3D2>Registered in England No. 4198197</FONT> =
<BR><FONT=20
size=3D2> </FONT> <BR><FONT size=3D2>Legal Disclaimer: <<A =
href=3D"http://www.csw.co.uk/disclaimer.htm"=20
target=3D_blank>http://www.csw.co.uk/disclaimer.htm</A>></FONT> =
<BR><FONT=20
size=3D2>*********************************************** =
</FONT><BR><FONT=20
size=3D2> </FONT> </P> =20
</TD></TR></TBODY></TABLE></FONT></DIV></BODY></HTML>
------=_NextPart_000_0000_01C51347.8792D580--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]