Difference between revisions of "Proposal: Person Registry, add GroupId parameter"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 20: | Line 20: | ||
==Discussion== | ==Discussion== | ||
*Note: the proposed query parameter only covers value of the observation, not its code. If in general this is considered to be 'bad modelling' the alternative would be to create a Norwegian-realm specific query parameter for 'administrative region'. Maybe other queries should be studied to find out how (in general) 'querying for observation results' is supported. [[User:Rene spronk|Rene spronk]] 14:08, 4 February 2009 (UTC) | *Note: the proposed query parameter only covers value of the observation, not its code. If in general this is considered to be 'bad modelling' the alternative would be to create a Norwegian-realm specific query parameter for 'administrative region'. Maybe other queries should be studied to find out how (in general) 'querying for observation results' is supported. [[User:Rene spronk|Rene spronk]] 14:08, 4 February 2009 (UTC) | ||
| − | *(PA, WGM Kyoto, May 2009): motion to add a new queryParemeter to the existing query (PRPA_IN101305UV02): name: AdministrativeObservationValue, with the @value attribute an ANY datatype, and semanticsText to be equal to the string ''AdministrativeObservation.value''. (motion Alexander Henket, second Astrid Koenders, 3-0-0) | + | *(PA, WGM Kyoto, May 2009 - THU Q3): motion to add a new queryParemeter to the existing query (PRPA_IN101305UV02): name: AdministrativeObservationValue, with the @value attribute an ANY datatype, and semanticsText to be equal to the string ''AdministrativeObservation.value''. (motion Alexander Henket, second Astrid Koenders, 3-0-0) |
Revision as of 08:33, 15 May 2009
Contents
Summary
The payload-query model as used by the Person Registry Find Candidates Query(PRPA_IN101305UV02) interaction [in the Patient Administration Domain/Person Topic domain] does not contain a parameter which corresponds to the value of the AdministrativeObservation as contained in the response model. This proposal seeks to add such a query parameter.
Use-case
Helse Vest, which implements a wide range of Patient?person registry interactions in the form of services, has a requirement to convey 'the administrative region a person/patient belongs to/ is associated with'. This concept isn't related to postal address: administrative regions are defined in a totally different way and can't be derived from the postal address.
ISO 3166 Part 2 (country subdivisions) is used as the coding system for the identification of the administrative region. Example (from a "new patient was added to the registry Notification" interaction):
<administrativeObservation classCode="OBS"> <code code="ADMREG" codeSystem="2.16.578.1.34.5.1"/> <value xsi:type="CE" code="NO-120108" displayName="Åsane (Bergen, Hordaland)" codeSystem="1.0.3166.2.2" codeSystemName="ISO 3166-2:2007"/> </administrativeObservation>
Proposed change
- Add a new queryParemeter to the existing query:
- Name: AdministrativeObservationValue, with the @value attribute an ANY datatype (to be consistent with the existing model), and semanticsText to be equal to the string AdministrativeObservation.value.
Discussion
- Note: the proposed query parameter only covers value of the observation, not its code. If in general this is considered to be 'bad modelling' the alternative would be to create a Norwegian-realm specific query parameter for 'administrative region'. Maybe other queries should be studied to find out how (in general) 'querying for observation results' is supported. Rene spronk 14:08, 4 February 2009 (UTC)
- (PA, WGM Kyoto, May 2009 - THU Q3): motion to add a new queryParemeter to the existing query (PRPA_IN101305UV02): name: AdministrativeObservationValue, with the @value attribute an ANY datatype, and semanticsText to be equal to the string AdministrativeObservation.value. (motion Alexander Henket, second Astrid Koenders, 3-0-0)
