PCCR-003-Synchronize with Clinical Statement
|Description||Synchronize with Clinical Statement|
|Submitted by||Results from analysis "Evaluating HL7 Care Provision DSTU"|
cmt#1: In the implementation it has been a problem that there are differences in the Clinical Statement and the Care Statement of Care Provision. This is mainly a computability problem. The exchangeability between Care Provision and CDA and the Clinical Statement pattern is complex.
cmt#2: There are too many differences now. Exchange between Care Provision, Clinical Statement Pattern and CDA is only possible if there is a transformation. This only concerns the technical part, the content is the same.
cmt#3: All changes in the Clinical Statement should be processed in the Care Provision Care Statement. This related to the consistency and improved implementability.
Clinical Statement and the Care Statement of Care Provision should be the same. This also concerns the classes in the choice box. The content of a class in this box differs from the content in other topics that use the same class. For instance: Patient and Person and Assigned entity differ. More differences can probably be found. Also in this topic there is data that concerns the patient or person and have nothing to do with the context or condition at that moment. These data cannot be entered in the patient or person CMET’s.
Patient Care Topic / Artefact
Recommended Action Items
Patient Care decided in May 2011 workgroup that the Care statement structure be replaced with A_SupportingClinicalStatement CMET universal (COCT_MT530000UV).
This will solve the three issues mentioned we hope. See further PCCR-000 on this topic.