Datatypes R2 Issue 87

Introducting ED Datatype flavors

A number of affiliate apecifications use various constraints on the contents of ED. There has also been interest expressed in imposing some of these constraints within universal specifications. While not true datatypes, the definition of datatype flavors for universal HL7 consumption falls within the province of the HL7 datatype specification.

Proposed flavors:

ED.DOC: An ED constrained to contain actual document content. Content of the ED is mandatory and "reference" is prohibited. “mediaType” values are restricted to “text/plain”, “text/html”, “text/xml” and “application/pdf”. If the mediaType is text/xml, the content must be a compliant HL7 CDA document.

ED.DOCREF: An ED constrained to be a reference to a document. Content of the ED is prohibited and "reference" is mandatory. “mediaType” values are restricted to “text/plain”, “text/html”, “text/xml” and “application/pdf”. If the mediaType is text/xml, the content must be a compliant HL7 CDA document.

ED.DOCORREF: An ED constrained to be a document or a reference to one. Either content or reference must be present but not both. “mediaType” values are restricted to “text/plain”, “text/html”, “text/xml” and “application/pdf”. If the mediaType is text/xml, the content must be a compliant HL7 CDA document.

ED.SIGNATURE: An ED constrained to an XML digital signature. Reference, charset, integrityCheck, thumbnail, compression, and language are prohibited. ED.mediaType is constrained to text/xml. ED content is mandatory and must conform to the w3c XML digital signature specification.

Links

Back to Data Types R2 issues