IHE / ITI.PDQm

The Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications.
https://profiles.ihe.net/ITI/PDQm/index.html
Creative Commons Attribution 4.0 International
4 stars 1 forks source link

Define reasonable response patterns for deprecated Patient identities #86

Closed JohnMoehrke closed 8 months ago

JohnMoehrke commented 2 years ago

PIXm https://github.com/IHE/ITI.PIXm/issues/120

For PDQm, it is possible for someone to query by id, or to get by id. In those cases the reasonable response patterns mentioned for PIXm on merge should also be addressed. right?

Given that PDQm (might) know of prior Patient Identities that have been Merged or simply Deprecated (Deleted). When a query happens requesting specifically that prior identity by Patient.id or Patient.identity Then there should be a set of reasonable response patterns that the server could be configured to use And a client would expect to be able to handle any of these defined reasonable response patterns

Return 404 Return 404 with an OperationOutcome pointing to the surviving id Return redirect to the new identity ???

see https://confluence.hl7.org/display/PA/Merge+Operation

JohnMoehrke commented 2 years ago

follow guidance from HL7. Return 200. Based on query parameter for status return empty (because asked for active), or the old in the bundle with the status inactive/deprecated.

JohnMoehrke commented 2 years ago

CP should be written. Follow example of PMIR - https://profiles.ihe.net/ITI/PMIR/ITI-93.html#23934131-post-mergedelete-expectations

JohnMoehrke commented 1 year ago

Spencer will address this in the $match public-comment