南通网站数据库结构图.pdfVIP

On Translating HL7 V2 to V3: II. XML Schema Wildcard Support Chung-Jen Ho, Ph.D. Chief Software Architect Quovadx, Inc. 2465 Latham Street, suite 100 Mountain View, CA 94040 cho@ Keywords: HL7 V2, HL7 V3, XML Schema Abstract In XML Schema there are structures for “targeted flexibility in content models and attribute declarations.” There are four XML Schema structures that allow this wildcard XML content: any, anyAttribute, anyType, or anySimpleType. The HL7 Version 3 CDA (Clinical Document Architecture) Framework Release 2.0 uses anyType [1], and the HL7 Version 3 XML ITS (Implementation Technology Specification) defines an abstract DataValue type ANY [2]. In this paper, we will present a methodology to represent this wildcard XML content in a hierarchical message layout in order to help the translation between HL7 V2 and HL7 V3. The structure of each HL7 V3 message is set out in an XML schema which is very different from HL7 V2’s hierarchical message layout. XML schema can contain recursive definition of XML elements and abstract types. There is a methodology to map a HL7 v3 schema into hierarchical message layout [3]. It simplifies the translation between HL7 V2 and HL7 V3 into the translation between two hierarchical message layouts. Translation between two hierarchical message layouts such as X12 and HL7 V2 is straight-forward, since hierarchical message layout can be represented by tree structure, and the translation is a mapping from one tree to the other tree. In this paper, we extend the discussion of mapping a HL7 v3 schema into a hierarchical message layout [3] to include XML Schema Wildcard Support. Mapping HL7 v3 Schema into Hierarchical Message Layout We will follow the notation and methodology