This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Proposal: Person Registry, add GroupId parameter"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Summary== | ==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 [http://www.hl7.org/v3ballot2008sep/html/domains/uvpa/editable/PRPA_RM101310UV.htm GroupIdentifier | + | 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 [http://www.hl7.org/v3ballot2008sep/html/domains/uvpa/editable/PRPA_RM101310UV.htm asMember.GroupIdentifier as contained in the response model]. This proposal seeks to add such a query parameter. |
==Use-case== | ==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. | 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 | + | The initial version of this proposal suggested that we use the administrativeObservation to identify the region. During discussion in September 2009 it was suggested that the use case could be covered by the existing Member and Group classes: a person is a member of a group, the group being "all persons within 1 specific administrative region". ISO 3166 Part 2 (country subdivisions) is used as the identifier of the administrative region. |
| − | Example | + | |
| − | + | * xxxx XML Example | |
| − | |||
| − | |||
| − | |||
| − | |||
==Proposed change== | ==Proposed change== | ||
*Add a new queryParameter to the existing query: | *Add a new queryParameter to the existing query: | ||
| − | **Name: | + | **Name: GroupID, with the @value attribute an II datatype (to be consistent with the existing model), and semanticsText to be equal to the string ''Group.id''. |
==Proposed documentation update== | ==Proposed documentation update== | ||
| Line 22: | Line 18: | ||
Add the following to the (model/walkthrough) of the payload MT of the ''Person Registry Find Candidates Query''(PRPA_IN101305UV02) interaction, i.e. the PRPA_RM101306UV02 R-MIM: | Add the following to the (model/walkthrough) of the payload MT of the ''Person Registry Find Candidates Query''(PRPA_IN101305UV02) interaction, i.e. the PRPA_RM101306UV02 R-MIM: | ||
#Add a new QueryParameter class, with 0..* cardinality | #Add a new QueryParameter class, with 0..* cardinality | ||
| − | #*Name: | + | #*Name: GroupID, with the @value attribute an II datatype, and semanticsText to be equal to the default string ''Group.id''. |
#Add the following text to the walkthrough, in the bullet list below the heading ParameterList: | #Add the following text to the walkthrough, in the bullet list below the heading ParameterList: | ||
| − | #*''' | + | #*'''GroupID''' - this parameter can limit the search to persons that are a member of a particular group. |
==Discussion== | ==Discussion== | ||
| − | + | ||
===WGM Kyoto 200905=== | ===WGM Kyoto 200905=== | ||
Revision as of 09:37, 10 December 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 asMember.GroupIdentifier 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.
The initial version of this proposal suggested that we use the administrativeObservation to identify the region. During discussion in September 2009 it was suggested that the use case could be covered by the existing Member and Group classes: a person is a member of a group, the group being "all persons within 1 specific administrative region". ISO 3166 Part 2 (country subdivisions) is used as the identifier of the administrative region.
- xxxx XML Example
Proposed change
- Add a new queryParameter to the existing query:
- Name: GroupID, with the @value attribute an II datatype (to be consistent with the existing model), and semanticsText to be equal to the string Group.id.
Proposed documentation update
Add the following to the (model/walkthrough) of the payload MT of the Person Registry Find Candidates Query(PRPA_IN101305UV02) interaction, i.e. the PRPA_RM101306UV02 R-MIM:
- Add a new QueryParameter class, with 0..* cardinality
- Name: GroupID, with the @value attribute an II datatype, and semanticsText to be equal to the default string Group.id.
- Add the following text to the walkthrough, in the bullet list below the heading ParameterList:
- GroupID - this parameter can limit the search to persons that are a member of a particular group.
Discussion
WGM Kyoto 200905
- (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)
- (PA, WGM Kyoto, May 2009 - THU Q3): ACTION: Rene to write descriptive text for the walkthrough and the attribute level documentation
WGM Atlanta 200909
- Discussion: probably better done by using the Group mechanism. Member of a group with scoper administrative region.
- MOTION: 200909 WGM WED Q4 - A motion was made by Irma to set aside the Kyoto motion and ask Rene to amend the proposal to use the Group structure instead of the administrativeObservation. Seconded by Jay Zimmerman. (7-0-2)
