1.3.6.1.4.1.19376.1.5.3.1.1.1: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{CDA Document| | {{CDA Document|Medical Documents|1.3.6.1.4.1.19376.1.5.3.1.1.1|Draft| | ||
This section defines the base set of constraints used by almost all medical document profiles described the PCC Technical Framework. | |||
| | |||
Standards= | |||
{{Std|CDAR2|Clinical Document Architecture, Release 2.0, 2005, HL7}} | |||
{{Std|CRS|Implementation Guide for CDA Release 2 – Level 1 and 2 – Care Record Summary (US realm), 2006, HL7.}} | |||
| | |||
Data= | Data= | ||
{{CDA Document Content|Sample Document|Sample Section|R|SampleSectionOID|Comment on section}} | {{CDA Document Content|Sample Document|Sample Section|R|SampleSectionOID|Comment on section}} | ||
{{CDA Document Content|Sample Document|Sample Entry|R2|SampleEntryOID|Comment on entry}} | {{CDA Document Content|Sample Document|Sample Entry|R2|SampleEntryOID|Comment on entry}}| | ||
}} | }} | ||
Revision as of 15:07, 11 May 2007
Development Only
The PCC Wiki Content is used only for development of IHE PCC Content. The Normative content of the PCC Technical Framework and the current supplements can be found at http://www.ihe.net/Technical_Framework/index.cfm#PCC
Medical Documents Specification 1.3.6.1.4.1.19376.1.5.3.1.1.1
This section defines the base set of constraints used by almost all medical document profiles described the PCC Technical Framework.
Standards
| CDAR2 | Clinical Document Architecture, Release 2.0, 2005, HL7 |
| CRS | Implementation Guide for CDA Release 2 – Level 1 and 2 – Care Record Summary (US realm), 2006, HL7. |
Specification
| Data Element Name | Opt | Template ID |
|---|---|---|
| Sample Section Comment on section |
R | SampleSectionOID |
| Sample Entry Comment on entry |
R2 | SampleEntryOID |
Conformance
CDA Release 2.0 documents that conform to the requirements of this content module shall indicate their conformance by the inclusion of the appropriate <templateId> elements in the header of the document. This is shown in the sample document below.
<ClinicalDocument xmlns='urn:hl7-org:v3'> <typeId extension="POCD_HD000040" root="2.16.840.1.113883.1.3"/> <templateId root='1.3.6.1.4.1.19376.1.5.3.1.1.1'/> <id root=' ' extension=' '/> <code code=' ' displayName=' ' codeSystem='2.16.840.1.113883.6.1' codeSystemName='LOINC'/> <title>Medical Documents</title> <effectiveTime value='20260407012005'/> <confidentialityCode code='N' displayName='Normal' codeSystem='2.16.840.1.113883.5.25' codeSystemName='Confidentiality' /> <languageCode code='en-US'/> : <component><structuredBody> </structuredBody></component> </ClinicalDocument> |
<!-- Verify the document type code -->
<assert test='cda:code[@code = "{{{LOINC}}}"]'>
Error: The document type code of a Medical Documents must be {{{LOINC}}}
</assert>
<assert test='cda: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>