This wiki has undergone a migration to Confluence found Here

Difference between revisions of "CDA Format Codes for IHE XDS"

From HL7Wiki
Jump to navigation Jump to search
Line 3: Line 3:
 
; From IHE : ''Globally unique code specifying the format of the document. Along with the typeCode, it should provide sufficient information to allow potential consumer to know if it will be able to process the document. The formatCode shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template (e.g., for a CDA Document, the fact that it complies with a CDA schema, possibly a template and the choice of a content-specific style sheet).''
 
; From IHE : ''Globally unique code specifying the format of the document. Along with the typeCode, it should provide sufficient information to allow potential consumer to know if it will be able to process the document. The formatCode shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template (e.g., for a CDA Document, the fact that it complies with a CDA schema, possibly a template and the choice of a content-specific style sheet).''
  
For C-CDA Release 2.1, the Structured Documents Workgroup agreed to the following:
+
For C-CDA Release 2.1, the Structured Documents Workgroup discussed the following on 10/27/2016 (no agreement yet!):
 
; <nowiki>urn:hl7-org:sdwg:ccda-structuredBody:2.1</nowiki> : For documents following C-CDA constraints using a structured body.
 
; <nowiki>urn:hl7-org:sdwg:ccda-structuredBody:2.1</nowiki> : For documents following C-CDA constraints using a structured body.
 
; <nowiki>urn:hl7-org:sdwg:ccda-nonXMLBody:2.1</nowiki> : For documents following C-CDA constraints using a non structured body.
 
; <nowiki>urn:hl7-org:sdwg:ccda-nonXMLBody:2.1</nowiki> : For documents following C-CDA constraints using a non structured body.

Revision as of 14:43, 27 October 2016

The formatCode metadata attribute in Integrating the Healthcare Enterprise's (IHE) Cross Enterprise Document Sharing (XDS) and related profiles.

From IHE 
Globally unique code specifying the format of the document. Along with the typeCode, it should provide sufficient information to allow potential consumer to know if it will be able to process the document. The formatCode shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template (e.g., for a CDA Document, the fact that it complies with a CDA schema, possibly a template and the choice of a content-specific style sheet).

For C-CDA Release 2.1, the Structured Documents Workgroup discussed the following on 10/27/2016 (no agreement yet!):

urn:hl7-org:sdwg:ccda-structuredBody:2.1 
For documents following C-CDA constraints using a structured body.
urn:hl7-org:sdwg:ccda-nonXMLBody:2.1 
For documents following C-CDA constraints using a non structured body.

For C-CDA Release 1.1, the Structured Documents Workgroup agreed to the following format at the May 2014 Working group meeting:

urn:hl7-org:sdwg:ccda-structuredBody:1.1 
For documents following C-CDA constraints using a structured body.
urn:hl7-org:sdwg:ccda-nonXMLBody:1.1 
For documents following C-CDA constraints using a non structured body.

We further recommended that the following pattern would be used going forward for other structured content:

urn:hl7-org[:workgroup]:IG[:supplement]:release 
For format codes created by other workgroups or implementation guides.