This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Reconciliation post January 2012 of Patient"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "Back to Patient_Administration#Submission / Proposals This page holds action items after analysis of the January 2012 Patient R-MIMs in relation to each other, to [[Reconcil...")
 
Line 11: Line 11:
 
#'''Action item''': Replace content from patientEntityChoiceSubject with the current [http://www.hl7.org/v3ballot/html/domains/uvpa/editable/PRPA_RM101301UV.html Activate Person R-MIM]
 
#'''Action item''': Replace content from patientEntityChoiceSubject with the current [http://www.hl7.org/v3ballot/html/domains/uvpa/editable/PRPA_RM101301UV.html Activate Person R-MIM]
  
The new R-MIM would like this:<br/>
+
Click on the thumbnail to see the resulting R-MIM<br/>
[[File:PRPA_RM201301UV_PostJan2012.png]]
+
[[File:PRPA_RM201301UV_PostJan2012.png| thumb]]
  
 
Non-exhaustive list of changes versus the current Patient Activate:
 
Non-exhaustive list of changes versus the current Patient Activate:

Revision as of 10:05, 21 February 2012

Back to Patient_Administration#Submission / Proposals

This page holds action items after analysis of the January 2012 Patient R-MIMs in relation to each other, to Person and the D-MIM Author: --[User:Alexander Henket|Alexander Henket] 14:21, 20 February 2012 (UTC)

D-MIM PRPA_DM000000UV

  1. Action item: <>

R-MIM PRPA_RM201301UV02 Patient Activate

This R-Mim is completely out of sync with Person, and does not align with the D-MIM for at least the relationship PatientOfOtherProvider that has a CMET A_PrincipalCareProvision that was replaced by a class CareProvision in the D-MIM

  1. Action item: Replace content from patientEntityChoiceSubject with the current Activate Person R-MIM

Click on the thumbnail to see the resulting R-MIM

PRPA RM201301UV PostJan2012.png

Non-exhaustive list of changes versus the current Patient Activate:

  • Removed CareGiver -- this is open for debate, but if we leave it in here we should consider adding it to Person
  • Replace PatientOfOtherProvider.A_PrincipalCareProvision with Role.CareProvision.performer.R_ResponsibleParty -- this could be open for debate but A_PrincipalCareProvision was removed form the D-MIM as well
  • Changed PersonalRelationship relationship from E_LivingSubject to E_Person -- this should align with Person Activate so change both or none.
  • Added Member2 and relationship to ObservationEvent to support conveying households
  • Added Citizen.code
  • Added Employee.code
  • Added Guardian.code

R-MIM PRPA_RM201302UV02 Patient Revise

  1. Action item: Give this R-MIM the exact same content below the patientEntityChoiceSubject as Activate Patient

R-MIM PRPA_RM201303UV02 Patient Demographics

  1. Action item: Give this R-MIM the exact same content below the patientEntityChoiceSubject as Activate Patient

R-MIM PRPA_RM201304UV02 Patient Identifiers

  1. Action item: Replace comparable content in this R-MIM with Person Identifiers (PRPA_RM101304UV02

R-MIM PRPA_RM201305UV02 Patient Nullify

  1. Action item: Replace comparable content in this R-MIM with Person Nullify (PRPA_RM101305UV02

R-MIM PRPA_RM201306UV02 Patient Registry Query By Demographics

  1. Action item: Document why most query parameters are 0..*, which means AND logic. It is unlikely that someone has e.g. multiple birthTime, or deceasedInd values. All value attributes are already 1..*, so the OR logic is covered.

R-MIM PRPA_RM201307UV02 Patient Registry Query By Identifier

  1. Action item: Document why query parameter PatientIdentifier is 0..* (AND logic), while its value attribute is also 1..* (OR logic). Use case could be "Patient with id 1 AND id 2" versus "Patient with id 1 OR id 2".

R-MIM PRPA_RM201310UV02 Patient Registry Find Candidates Response

  1. Action item: Give this R-MIM the exact same content below the patientEntityChoiceSubject as Activate Patient, with the exception of QueryMatchObservation