1.3 CDA consistency

NOTE: ReferHL7 v3Complete discussion on improvements and LocalizationV3.

ConsistentCDAA document is verified to a minimumCDAArchitecture, which limits itsCodeUse of words to values. However, computers cannot verify consistency in all aspects. The focus in this regard is to highlightCDAAspects that cannot be verified by the computer-especially thoseCDAHuman beings can understand the demand-related aspects.

A document originated from a system role that createdCDADocumentation.CDAThe document can be created by converting from other formats as an applicationProgram. Communication with permanent storage locations is usually the source of the document, usually used
HL7 V2 MdmOrHL7 v3Medical records. Document cause guarantee generatedCDAThis document is highly consistent with this specification.

Receiving a document is also a system role that receives status updates and documents from a document builder or document management system. The document recipient is responsible for ensuring that the received documents are parsed according to this specification.

BecauseCDAIt is an exchange standard and may not represent the original form of the document. In this specificationCDAThere is no permanent storage requirement for documents. However, as mentioned earlier, document management andCDAThe specification has a strong dependency relationship. InCDAThe owner defined in the header participates in the maintenance of the original document. This original document may beCDAOther formats.

1.3.1Recipient's Responsibilities

Suppose the default value defined in this specification, and where the instance does not contain the value: InCDAWhere the default value is defined, the receiver must assume that these values in the event do not contain any values. (Note that the default value is marked as"[Default]")

Parse and describe the completeCDAHeader:CDAThe recipient of the document must be able to parse and describe the entire header. Because applications may selectively display population informatics extracted from a central Home Directory and otherCDAHeader information, CDAThe description of the document header is determined by the recipient. In addition, the description of the header information may depend on the local business logic and application context (such as the electronic health file, without identification ). One or more descriptions can be recommended in the source document.XMLStyle sheet. How to use theseXMLThe style sheet depends onCDAThe recipient of the document.

Resolution and descriptionCDAEnough text to translateCDADocumentation:CDAThe recipient of the document must be able to fully parse and describe the documentCDAThe document subject uses the following rules:

(1) IfCDAThe subject is notXMLForm, you need to use a specialMimeMedia software tools to parse it;

(2) IfCDAThe subject is structured. The label and title of a section must be parsed.Section. Title
Is a non-label section.

(3) IfCDAThe subject is structured,Section. TextThe domain content must comply with the rules defined in the descriptive section.

not required CDA receiver parsing and description of the document CDA all CDA entries. Within the scope of local implementation, business partners may require recipients to parse and describe various entries