HL7 CDA Core Principles - Versionsgeschichte

Aheidel am 21. Juni 2019 um 08:59 Uhr

2019-06-21T08:59:28Z

Aheidel am 21. Juni 2019 um 08:58 Uhr

2019-06-21T08:58:04Z

Dammon: /* Use of XML */

2019-06-16T11:49:00Z

‎Use of XML

Dammon: /* Common aspects */

2019-06-16T11:47:20Z

‎Common aspects

Dammon: /* Value Sets */

2019-06-16T11:36:33Z

‎Value Sets

Dammon: /* Code Systems */

2019-06-16T11:32:43Z

‎Code Systems

Dammon: /* Object Identifiers (OIDs) */

2019-06-16T11:25:24Z

‎Object Identifiers (OIDs)

Dammon: /* Interval of time (IVL_TS) */

2019-06-16T11:19:17Z

‎Interval of time (IVL_TS)

Dammon: /* Intervals (IVL) */

2019-06-16T11:17:39Z

‎Intervals (IVL)

Dammon: /* Point in Time (TS) */

2019-06-16T11:15:52Z

‎Point in Time (TS)

@@ Zeile 30: / Zeile 30: @@
 | [[File:Faq.svg|50px]] || This is a frequently asked question (FAQ) with answer
 |-
-| [[File:Conformance.svg|50px]] || This is a constraint; in some situations also the rule identification is specified, e.g. dtr1-1-ANY, which links to the corresponding validation rule.
+| [[File:Conformance.svg|50px]] || This is a constraint; in some situations the rule identification is also specified, e.g. dtr1-1-ANY, which links to the corresponding validation rule.
 |}

@@ Zeile 17: / Zeile 17: @@
 === Background ===
-In many (European) countries, implementation guides for the use of data types in HL7 V3 are published. They take into account country specific constraints on the data types.
+In many (European) countries, implementation guides for the use of data types in HL7 V3 are published. They take into account country-specific constraints on the data types.
 === Legend of symbols ===

@@ Zeile 46: / Zeile 46: @@
 === Use of XML ===
-HL7 Version 3 CDA uses the Extensible Markup Language (XML) as the exchange format. It is assumed that the reader is familiar with common XML aspects <ref>World Wide Web Consortium. Extensible Markup Language, 1.0, 2nd Edition: http://www.w3.org/TR/REC-xml</ref><ref>World Wide Web Consortium. XML Schema:<br />http://www.w3.org/TR/xmlschema-0/<br />http://www.w3.org/TR/xmlschema-1/<br />http://www.w3.org/TR/xmlschema-2/</ref>. However, some constraints are made regarding the use of CDA.
+HL7 Version 3 CDA uses the Extensible Markup Language (XML) as the exchange format. It is assumed that the reader is familiar with common XML aspects <ref>World Wide Web Consortium. Extensible Markup Language, 1.0, 2nd Edition: http://www.w3.org/TR/REC-xml</ref><ref>World Wide Web Consortium. XML Schema: http://www.w3.org/TR/xmlschema-0/,&nbsp;&nbsp; http://www.w3.org/TR/xmlschema-1/,&nbsp;&nbsp; http://www.w3.org/TR/xmlschema-2/</ref>. However, some constraints are made regarding the use of CDA.
 ==== Character Set ====

@@ Zeile 46: / Zeile 46: @@
 === Use of XML ===
-HL7 Version 3 CDA uses the Extensible Markup Language (XML) as the exchange format. It is assumed that the reader is familiar with common XML aspects. However, some constraints are made regarding the use of CDA.
+HL7 Version 3 CDA uses the Extensible Markup Language (XML) as the exchange format. It is assumed that the reader is familiar with common XML aspects <ref>World Wide Web Consortium. Extensible Markup Language, 1.0, 2nd Edition: http://www.w3.org/TR/REC-xml</ref><ref>World Wide Web Consortium. XML Schema:<br />http://www.w3.org/TR/xmlschema-0/<br />http://www.w3.org/TR/xmlschema-1/<br />http://www.w3.org/TR/xmlschema-2/</ref>. However, some constraints are made regarding the use of CDA.
 ==== Character Set ====

@@ Zeile 1.203: / Zeile 1.203: @@
 A ''Value Set'' represents a uniquely identifiable set of valid concept representations, where any concept representation can be tested to determine whether or not it is a member of the value set.
 Value set complexity may range from a simple flat list of concept codes drawn from a single code system, to an unbounded hierarchical set of possibly post-coordinated expressions drawn from multiple code systems.
 Value sets exist to constrain the content for a coded element in an HL7 static model or data type property. Value sets cannot have null content and must contain at least one concept representation where any given concept is generally (but not required to be) represented by only a single code within the Value Set.
@@ Zeile 1.213: / Zeile 1.215: @@
 | [[File:Pfeil_rechts.png|50px]]
 |Please note that value set OIDs never appear in a CDA Release 2 document. They are used for constraint expressions, for example in implementation guides.
 In order to send a specific code drawn from a value set, the corresponding code system has to be conveyed.
 An example, in the implementation specification the constraint on the model element ''maritalStatusCode'' is expressed as “to be drawn from value set 2.16.840.1.113883.5.2 ''MaritalStatus''”.
 To actually send a marital status of “M” (married) that is shown in the value set figure above, the corresponding HL7 CDA instance would say:
 <syntaxhighlight lang="xml">
   <maritalStatusCode code="M" codeSystem="2.16.840.1.113883.5.2"/>
@@ Zeile 1.229: / Zeile 1.235: @@
 Please note: the formerly supported values CNE (Coded No Extensibility) and CWE (Coded With Extensibility) in ART-DECOR are deprecated as of December 2017. Specification CNE is handled as required and CWE is handled as extensible.
-{| class="hl7table"
+{| class="hl7table" style="width:50%"
 |+<ref group="Table">Binding Strengths</ref> ''Binding Strengths''
 ! Strength !! Description

@@ Zeile 1.193: / Zeile 1.193: @@
 Within HL7, a ''Code System'' is defined as a collection of codes with associated designations and meanings. Examples of code systems include ICD-10, SNOMED CT, and LOINC.
 To meet the requirements of a code system as defined by HL7, a given code must resolve to one and only one meaning within the code system. Given this definition, each code table in the HL7 Version 3 standard represents a different code system since codes are sometimes used in different tables to have different meanings.
 For example, “M” in the administrative gender table (''AdministrativeGender'', OID 2.16.840.1.113883.5.1) means “male”, while “M” in the marital status table (''MaritalStatus'', OID 2.16.840.1.113883.5.2) means “married”.
 In this specification, code system tables are not presented in detail.

@@ Zeile 1.051: / Zeile 1.051: @@
 It is important to understand the difference between identification of instances (ids) and code concepts (classifications). Within the context of HL7 interactions OIDs are quite often used.
 An id points to a specific instance of an object or identification scheme (a particular methodology for the identification of a class of objects), for example a specific person as the patient or a physician, a specific lab observation or an X-ray photo.
@@ Zeile 1.066: / Zeile 1.067: @@
 {| class="hl7table" style="width:100%"
 | [[File:Pfeil_rechts.png|50px]]
-|All OIDs with an element of 999 or 9999 are for documentation purposes only. They will be replaced by permanent OIDs once these have been as-signed/found/applied for.
+|All OIDs with an element of 999 or 9999 are for documentation purposes only. They will be replaced by permanent OIDs once these have been assigned/found/applied for.
 |}
@@ Zeile 1.077: / Zeile 1.078: @@
 From a policy perspective it is common practice in several healthcare related OID registries (HL7 International at http://www.hl7.org, OID Registry Germany at http://www.dimdi.de, OID registry Switzerland at http://oid.refdata.ch, and OID registry Austria at https://www.gesundheit.gv.at/OID_Frontend) to distinguish at least between the following types of OIDs:
-{| class="hl7table" style="width:60%"
+{| class="hl7table" style="width:50%"
 |+<ref group="Table">Recommended OID sub-branches for different artefacts</ref> ''Recommended OID sub-branches for different artefacts''
 ! Arc !! Description
@@ Zeile 1.104: / Zeile 1.105: @@
 In ART-DECOR a project typically is set into the .77 branch of a governance group. When setting up the project, the OID for that project also determines the artefact OIDs using throughout the ART-DECOR project. The following additional branches are used to distinguish between different OID types:
-{| class="hl7table"
+{| class="hl7table" style="width:50%"
-|+<ref group="Table">Recommended OID sub-branches for ART-DECOR projects</ref> ''Recommended OID sub-branches for different artefacts''
+|+<ref group="Table">Recommended OID sub-branches for ART-DECOR projects</ref> ''Recommended OID sub-branches for ART-DECOR projects''
-! Artefact code	Description !! Recommended !! OID suffix
+! Artefact code	!! Description !! Recommended OID suffix
 |-
 | DS || dataset || .77.1

@@ Zeile 925: / Zeile 925: @@
 {| class="hl7table" style="width:100%"
 | [[File:Pfeil_rechts.png|50px]]
-|It must be noted that intervals of time stamps in HL7 are equally treated as other interval types (e.g. integers). The statement, one may take 1–3 tablets (interval of integers), for example, says that you are allowed to take no more than three tablets, not 3½ or 3.5 tablets. On the other hand, when treat the words “until 12 June 2011” regarding the upper interval limit differently, particularly we assume that the entire day 12 June is still in-cluded in this time interval.
+|It must be noted that intervals of time stamps in HL7 are equally treated as other interval types (e.g. integers). The statement, one may take 1–3 tablets (interval of integers), for example, says that you are allowed to take no more than three tablets, not 3½ or 3.5 tablets. On the other hand, when treat the words “until 12 June 2011” regarding the upper interval limit differently, particularly we assume that the entire day 12 June is still included in this time interval.
-Thus, in human perception time intervals are handled differently com-pared to such as number intervals. This is a situation may lead to inconsist-encies in standardized communication. As a conclusion, an upper limit “12 June 2011” means that only the very first moment of the 12 June is included in the interval, but not, for example, the 12 June 13:00 hours.
 Interpretation does not depend on the accuracy of the time:
 * “after 2004” means “from January 1, 2005 00:00:00.000”,

← Nächstältere Version		Version vom 16. Juni 2019, 11:17 Uhr
Zeile 827:		Zeile 827:

	<ref group="Figure">Several possibilities to determine closed intervals</ref> ''Several possibilities to determine closed intervals''		<ref group="Figure">Several possibilities to determine closed intervals</ref> ''Several possibilities to determine closed intervals''
		+
		+	In addition, there is sometimes the need to specify incomplete intervals (open intervals). For example, an interval with only an upper limit to indicate a maximum dose or a start date and time only to express “since…”.

	{{ConstraintBox\|		{{ConstraintBox\|

@@ Zeile 799: / Zeile 799: @@
 * ss the two-digit second.
 Optional a time zone ZZZZ, the four-digit time alignment with a preceding “-” or a “+” can be specified. If time zone is omitted, local time is assumed.
 The point in time may be right truncated in respect to the precision of the information.