Difference between revisions of "Structured Document Architecture"

Latest revision as of 12:07, 13 December 2008

(main entry to be created)

For other architectures based on HL7 artefacts see HL7 Messaging Architecture and Services Oriented Architecture.

The CDA is created by the Structured Documents TC.

See CDA FAQ for a FAQ related to CDA models as well as CDA implementation.

@@ Line 1: / Line 1: @@
 ''(main entry to be created)''
-== FAQ ==
+For other architectures based on HL7 artefacts see [[HL7 Messaging Architecture]] and [[Services Oriented Architecture]].
-=== CDA R2 using a non-XML ITS ===
+The CDA is created by the [[Structured Documents TC]].
-*In how far is CDA R2 "abstract"? - In other words: if one were to attempt to apply a different ITS (assuming there was one, e.g. ASN.1 or CORBA), what would the "open issues list" look like?
-There are 3 known issues:
+See also [[CDA for Common Document Types (CDA4CDT)]]
-*Structure of the Narrative Block
-*IIref mechanism
-(CDA R2 Documentation) ''"Specific enhancements to the CDA Schema, above and beyond those defined in the HL7 V3 XML ITS, are described [..] in CDA XML Implementation (§ 6 )."'' Section 6 states: ''"The CDA Narrative Block, which is the XML content model of section.text, is manually crafted, as described above (see Section Narrative Block (§ 4.3.5 ))."''
+== FAQ ==
-(Charlie McKay) The way that references between parts of the narrative block and the structured content are done in an XML specific way (reasonably enough because HL7 itself -as an standard- does not have an IIref mechanism agreed yet).  This is the rationale for the schema edit: Add "ID" attribute, of type XML ID, to Section, ObservationMedia, RegionOfInterest
+See [[CDA FAQ]] for a FAQ related to CDA models as well as CDA implementation.