PCC TF-2/Trailer
Appendix A - Examples Using PCC Content Profiles
Example documents conforming to each profile can be found on the IHE wiki at the following URLs.
| Profile and Content | URL |
|---|---|
| XDS-MS | |
| Referral Summary | XDSMS Example1 |
| Discharge Summary | XDSMS Example1 |
| XPHR | |
| XPHR Content | XPHR Example1 |
| XPHR Update | XPHR Example2 |
| (EDR) ED Referral | EDR Example |
| (APS) Antepartum Summary | APS Example |
| (EDES) | |
| Triage Note | EDES Example1 |
| ED Nursing Note | EDES Example2 |
| Composite Triage and Nursing Note | EDES Example3 |
| ED Physician Note | EDES Example4 |
| (FSA) Functional Status Section | FSA Example |
Appendix B - Validating CDA Documents using the Framework
Many of the constraints specified by the content modules defined in the PCC Technical Framework can be validated automatically by software. Automated validation is a very desirable capability, as it makes it easier for implementers to test the correctness of their implementations. With regard to validation of the content module, the PCC Technical Framework narrative is the authoritative specification, not any automated software tool. Having said that, it is still very easy to create a validation framework for the IHE PCC Technical Framework using a XML validation tool such as Schematron. Since each content module has a name (the template identifier), any XML instance that reports itself to be of that "class" can be validated by creating assertions that must be true for each constraint indicated for the content module. In the XML representation, the <templateId> element is a child of the element that is claiming conformance to the template named. Thus the general pattern of a Schematron that validates a specific template is shown below:
<schema xmlns="http://www.ascc.net/xml/schematron" xmlns:cda="urn:hl7-org:v3">
<ns prefix="cda" uri="urn:hl7-org:v3" />
<pattern name='ReferralSummary'>
<rule context='*[cda:templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.1.3]"'>
<!-- one or more assertions made by the content module -->
</rule>
</pattern>
</schema>
Validating Documents
For document content modules, the pattern can be extended to support common document content module constraints as shown below:
<schema xmlns="http://www.ascc.net/xml/schematron" xmlns:cda="urn:hl7-org:v3">
<ns prefix="cda" uri="urn:hl7-org:v3" />
<pattern name='ReferralSummary'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.1.3]"'>
<!-- Verify that the template id is used on the appropriate type of object -->
<assert test='../ClinicalDocument'>
Error: The referral content module can only be used on Clinical Documents.
</assert>
<!-- Verify that the parent templateId is also present. -->
<assert test='templateId[@root="1.3.6.1.4.1.19376.1.5.3.1.1.2"]'>
Error: The parent template identifier for medical summary is not present.
</assert>
<!-- Verify the document type code -->
<assert test='code[@code = "34133-9"]'>
Error: The document type code of a referral summary must be
34133-9 SUMMARIZATION OF EPISODE NOTE.
</assert>
<assert test='code[@codeSystem = "2.16.840.1.113883.6.1"]'>
Error: The document type code must come from the LOINC code
system (2.16.840.1.113883.6.1).
</assert>
<!-- Verify that all required data elements are present -->
<assert test='.//templateId[@root = "1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
Error: A referral summary must contain a reason for referral.
</assert>
<!-- Alert on any missing required if known elements -->
<assert test='.//templateId[@root = "1.3.6.1.4.1.19376.1.5.3.1.3.8"]'>
Warning: A referral summary should contain a list of history of past illnesses.
</assert>
<!-- Note any missing optional elements -->
<assert test='.//templateId[@root = "1.3.6.1.4.1.19376.1.5.3.1.3.18"]'>
Note: This referral summary does not contain the pertinent review of systems.
</assert>
</rule>
</pattern>
</schema>
Validating Sections
The same pattern can be also applied to sections with just a few minor alterations.
<schema xmlns="http://www.ascc.net/xml/schematron" xmlns:cda="urn:hl7-org:v3">
<ns prefix="cda" uri="urn:hl7-org:v3" />
<pattern name='ReasonForReferralUncoded'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
<!-- Verify that the template id is used on the appropriate type of object -->
<assert test='section'>
Error: The coded reason for referral module can only be used on a section.
</assert>
<assert test='false'>
Manual: Manually verify that this section contains narrative providing the
reason for referral.
</assert>
<!-- Verify that the parent templateId is also present. -->
<assert test='templateId[@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
Error: The parent template identifier for the reason for referral
module is not present.
</assert>
<!-- Verify the section type code -->
<assert test='code[@code = "42349-1"]'>
Error: The section type code of the reason for referral section must be 42349-1
REASON FOR REFERRAL.
</assert>
<assert test='code[@codeSystem = "2.16.840.1.113883.6.1"]'>
Error: The section type code must come from the LOINC code
system (2.16.840.1.113883.6.1).
</assert>
</pattern>
<pattern name='ReasonForReferralCoded'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.3.2"]'>
<!-- The parent template will have already verified the type of object -->
<!-- Verify that the parent templateId is also present. -->
<assert test='templateId[@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
Error: The parent template identifier for the reason for referral
module is not present.
</assert>
<!-- Don't bother with the section type code, as the parent template caught it -->
<!-- Verify that all required data elements are present -->
<assert test='.//templateId[@root = "1.3.6.1.4.1.19376.1.5.3.1.4.13"]'>
Error: A coded reason for referral section must contain an simple observation.
</assert>
<!-- Alert on any missing required if known elements -->
<!-- Note any missing optional elements -->
</rule>
</pattern>
</schema>
A similar pattern can also be followed for Entry and Header content modules, and these are left as an exercise for the reader.
Phases of Validation and Types of Errors
Note that each message in the Schematrons shown above start with a simple text string that indicates whether the message indicates one of the following conditions:
- An error, e.g., the failure to transmit a required element,
- A warning, e.g., the failure to transmit a required if known element,
- A note, e.g., the failure to transmit an optional element.
- A manual test, e.g., a reminder to manually verify some piece of content.
Schematron supports the capability to group sets of rules into phases by the pattern name, and to specify which phases of validation should be run during processing. To take advantage of this capability, one simply breaks each <pattern> element above up into separate patterns depending upon whether the assertion indicates an error, warning, note or manual test, and then associate each pattern with a different phase. This is shown in the figure below.
<schema xmlns="http://www.ascc.net/xml/schematron" xmlns:cda="urn:hl7-org:v3">
<ns prefix="cda" uri="urn:hl7-org:v3" />
<phase id="errors">
<active pattern="ReasonForReferralUncoded_Errors"/>
<active pattern="ReasonForReferralCoded_Errors"/>
</phase>
<phase id="manual">
<active pattern="ReasonForReferralUncoded_Manual"/>
</phase>
<pattern name='ReasonForReferralUncoded_Errors'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
<assert test='section'>
Error: The coded reason for referral module can only be used on a section.
</assert>
<assert test='code[@code = "42349-1"]'>
Error: The section type code of the reason for referral section must be 42349-1
REASON FOR REFERRAL.
</assert>
<assert test='code[@codeSystem = "2.16.840.1.113883.6.1"]'>
Error: The section type code must come from the LOINC code
system (2.16.840.1.113883.6.1).
</assert>
</rule>
</pattern>
<pattern name='ReasonForReferralUncoded_Manual'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
<assert test='false'>
Manual: Manually verify that this section contains narrative providing the
reason for referral.
</assert>
</pattern>
<pattern name='ReasonForReferralCoded_Errors'>
<rule context='*[templateId/@root="1.3.6.1.4.1.19376.1.5.3.1.3.2"]'>
<assert test='templateId[@root="1.3.6.1.4.1.19376.1.5.3.1.3.1"]'>
Error: The parent template identifier for the reason for referral not present.
</assert>
<assert test='.//templateId[@root = "1.3.6.1.4.1.19376.1.5.3.1.4.13"]'>
Error: A coded reason for referral section must contain an simple observation.
</assert>
</rule>
</pattern>
</schema>
Using these simple "templates" for template validation one can simply create a collection of Schematron patterns that can be used to validate the content modules in the PCC Technical Framework. Such Schematrons are expected to be made available as part of the MESA test tools that are provided to IHE Connectathon participants, and which will also be made available to the general public after connectathon.
Appendix C - Extensions to CDA Release 2.0
This section describes extensions to CDA Release 2.0 that are used by the IHE Patient Care Coordination Technical Framework.
IHE PCC Extensions
All Extensions to CDA Release 2.0 created by the IHE PCC Technical Committee are in the namespace urn:ihe:pcc:hl7v3.
The approach used to create extension elements created for the PCC Technical Framework is the same as was used for the HL7 Care Record Summary (see Appendix E) and the ASTM/HL7 Continuity of Care Document (see secion 7.2).
replacementOf
The <replacementOf> extension element is applied to a section appearing in a PHR Update Document to indicate that that section's content should replace that of a previously existing section. The identifier of the previously existing section is given so that the PHR Manager receiving the Update content will know which section to replace. The model for this extension is shown below.
Use of this extension is shown below. The <replacementOf> element appears after all other elements within the <section> element. The <id> element appearing in the <externalDocumentSection> element shall provide the identifier of the section being replaced in the parent document.
<section>
<id root=' ' extension=' '/>
|
Extensions Defined Elsewhere used by IHE PCC
Entity Identifiers
There is often a need to record an identifer for an entity so that it can be subsequently referenced. This extension provides a mechnism to store that identifier. The element appears after any <realm>, <typeId> or <templateId> elements, but before all others in the entity where it is used:
<playingEntity classCode='ENT' determinerCode='INSTANCE'> <sdtc:id root='1.3.6.4.1.4.1.2835.2' extension='EntityID'/> : . </playingEntity>
Patient Identifier
There is a need to record the identifer by which a patient is known to another healthcare provider. This extension provides a role link between the assigned, related or associated entity, and the patient role.
Use of this extension to record the identifier under which the patient is known to a provider is shown below.
<assignedEntity>
<id extension='1' root='1.3.6.4.1.4.1.2835.1'/>
|
The <patient> element records the link between the related, assigned or associated entity and the patient. The <id> element provides the identifier for the patient. The root attribute of the <id> should be the namespace used for patient identifiers by the entity. The extension attribute of the <id> element shall be the patient's medical record number or other identifier used by the entity to identify the patient.