HL7 Terminology (THO)
6.0.2 - Publication
HL7 Terminology (THO)
6.0.2 - Publication
This page is part of the HL7 Terminology (v6.0.2: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
| Active as of 2019-03-20 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="v3-hl7PublishingDomain"/>
<language value="en"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p class="res-header-id"><b>Generated Narrative: CodeSystem v3-hl7PublishingDomain</b></p><a name="v3-hl7PublishingDomain"> </a><a name="hcv3-hl7PublishingDomain"> </a><a name="v3-hl7PublishingDomain-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Language: en</p></div><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Specializes</td><td>Specializes</td><td/><td>Coding</td><td>The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric.</td></tr><tr><td>Generalizes</td><td>Generalizes</td><td/><td>Coding</td><td>Inverse of Specializes. Only included as a derived relationship.</td></tr><tr><td>Subsection containment relationship</td><td>OwningSubSection</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#OwningSubSection</td><td>Coding</td><td>Identifies the sub-section (target concept) of which this domain (source concept) is a part. ConceptRelationshipProperites: [isNavigable: false; functionalism: functional; reflexivity: irreflexive; symmetry: antisymetric; connected: false; transitivity: antitransitive; allowedForTargets: all codes from the hl7PublishingSubSection code system; requiredForSources: all codes from hl7PublishingDomain code system;]</td></tr><tr><td>internalId</td><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>code</td><td>The internal identifier for the concept in the HL7 Access database repository.</td></tr><tr><td>Status</td><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>Designation of a concept's state. Normally is not populated unless the state is retired.</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-hl7PublishingDomain</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>Subsection containment relationship</b></td><td><b>internalId</b></td><td><b>Status</b></td></tr><tr><td style="white-space:nowrap">AB<a name="v3-hl7PublishingDomain-AB"> </a></td><td>accounting & billing</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports accounting and billing functions - and "provides support for the creation and management of patient billing accounts and the post of financial transactions against patient billing accounts for the purpose of aggregating financial transactions that will be submitted as claims or invoices for reimbursemen"</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>FI</td><td>23172</td><td>active</td></tr><tr><td style="white-space:nowrap">AI<a name="v3-hl7PublishingDomain-AI"> </a></td><td>trigger event control act infrastructure</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports trigger event control act infrastructure - and "covers the alternate structures of the message Trigger Event Control Acts in the HL7 Composite Message."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>MC</td><td>23173</td><td>active</td></tr><tr><td style="white-space:nowrap">AL<a name="v3-hl7PublishingDomain-AL"> </a></td><td>artificial listing for test purposes - faux Domain for testing</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that was defined as an "artificial listing" domain to support publication testing.</p>
</div></td><td>RE</td><td>23174</td><td>active</td></tr><tr><td style="white-space:nowrap">BB<a name="v3-hl7PublishingDomain-BB"> </a></td><td>blood tissue and organ</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports blood tissue and organ domain - and "comprises the models, messages, and other artIfacts that are needed to support messaging related to the process of blood, tissue, and organ banking operations such as donations, eligibility, storage, dispense, administration/transfusion, explantation, and implantation. "</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23175</td><td>active</td></tr><tr><td style="white-space:nowrap">CD<a name="v3-hl7PublishingDomain-CD"> </a></td><td>clinical document architecture</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports the clinical document architecture.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23176</td><td>active</td></tr><tr><td style="white-space:nowrap">CG<a name="v3-hl7PublishingDomain-CG"> </a></td><td>clinical genomics</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports clinical genomics - and includes " standards to enable the exchange of interrelated clinical and personalized genomic data between interested parties."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23178</td><td>active</td></tr><tr><td style="white-space:nowrap">CI<a name="v3-hl7PublishingDomain-CI"> </a></td><td>transmission infrastructure</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports transmission infrastructure - and " is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>MC</td><td>23177</td><td>active</td></tr><tr><td style="white-space:nowrap">CO<a name="v3-hl7PublishingDomain-CO"> </a></td><td>coverage</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Coverage - and provides support for managing health care coverage in the reimbursement system(s).</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>FI</td><td>23260</td><td>active</td></tr><tr><td style="white-space:nowrap">CP<a name="v3-hl7PublishingDomain-CP"> </a></td><td>common product model</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports the common product model - which "is used to improve the alignment between the different representations of products used within the body of HL7 Version 3 models."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23179</td><td>active</td></tr><tr><td style="white-space:nowrap">CR<a name="v3-hl7PublishingDomain-CR"> </a></td><td>claims and reimbursement</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Claims and Reimbursement - and "provides support for Generic, Pharmacy, Preferred Accommodation, Physician, Oral Health Vision Care and Hospital claims for eligibility, authorization, coverage extension, pre-determination, invoice adjudication, payment advice and Statement of Financial Activity (SOFA) Release 3 of this document adds claims messaging support for Physician, Oral Health Vision Care and Hospital claims."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>FI</td><td>23180</td><td>active</td></tr><tr><td style="white-space:nowrap">CS<a name="v3-hl7PublishingDomain-CS"> </a></td><td>clinical statement</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports a common clinical statement pattern - and "is a 'pattern' designed to be used within multiple HL7 Version 3 domain models. This pattern is intended to facilitate the consistent design of communications that convey clinical information to meet specific use cases."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>CO</td><td>23181</td><td>active</td></tr><tr><td style="white-space:nowrap">CT<a name="v3-hl7PublishingDomain-CT"> </a></td><td>common types</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports common model types - and "are a work product produced by a particular committee for expressing a common, useful and reusable concept."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>CO</td><td>23182</td><td>active</td></tr><tr><td style="white-space:nowrap">DD<a name="v3-hl7PublishingDomain-DD"> </a></td><td>dummy domain</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that was created to support testing and initial set-up functions.</p>
</div></td><td>UU</td><td>23171</td><td>active</td></tr><tr><td style="white-space:nowrap">DI<a name="v3-hl7PublishingDomain-DI"> </a></td><td>diagnostic imaging</td><td><div><p><strong>Description:</strong> This domain has been retired in favor of "imaging integration" (II).</p>
</div></td><td>PO</td><td>23183</td><td>active</td></tr><tr><td style="white-space:nowrap">DS<a name="v3-hl7PublishingDomain-DS"> </a></td><td>decision support</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that provides decision support.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>RE</td><td>23184</td><td>active</td></tr><tr><td style="white-space:nowrap">EM<a name="v3-hl7PublishingDomain-EM"> </a></td><td>emergency medical services</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Emergency Medical Services.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23261</td><td>active</td></tr><tr><td style="white-space:nowrap">II<a name="v3-hl7PublishingDomain-II"> </a></td><td>imaging integration</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports imaging integration - and is "comprises the models, implementation guides, sample documents and images that are needed to illustrate the transformation of DICOM structured reports to CDA Release 2 as well as the creation of CDA diagnostic imaging reports."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23185</td><td>active</td></tr><tr><td style="white-space:nowrap">IZ<a name="v3-hl7PublishingDomain-IZ"> </a></td><td>immunization</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports immunization - and "describes communication of information about immunization: the administration of vaccines (and/or antisera) to individuals to prevent infectious disease."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23186</td><td>active</td></tr><tr><td style="white-space:nowrap">LB<a name="v3-hl7PublishingDomain-LB"> </a></td><td>laboratory</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports clinical laboratory functions - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to laboratory tests or observations. "</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23187</td><td>active</td></tr><tr><td style="white-space:nowrap">ME<a name="v3-hl7PublishingDomain-ME"> </a></td><td>medication</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports medication - and "deals with the description of a medicine for the purposes of messaging information about medicines" and the applications of these descriptions.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23188</td><td>active</td></tr><tr><td style="white-space:nowrap">MI<a name="v3-hl7PublishingDomain-MI"> </a></td><td>masterfile infrastructure</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports master file infrastructure - and is "comprises the classes and attributes needed to support Master Files and Registries."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>MF</td><td>23189</td><td>active</td></tr><tr><td style="white-space:nowrap">MM<a name="v3-hl7PublishingDomain-MM"> </a></td><td>materials management</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Materials Management - and is "supports the simple scenario of a Materials Management application sending requests, notifications and queries to an auxiliary application. The intent is to establish a standard for the minimum functionality that is useful and comprehensive enough to explore the important concepts relative to inventory management."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PR</td><td>23190</td><td>active</td></tr><tr><td style="white-space:nowrap">MR<a name="v3-hl7PublishingDomain-MR"> </a></td><td>medical records</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports medical records - and is "supports clinical document management, and document querying."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>RC</td><td>23191</td><td>active</td></tr><tr><td style="white-space:nowrap">MT<a name="v3-hl7PublishingDomain-MT"> </a></td><td>shared messages</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports shared messages - and "are a work product produced for expressing common, useful and reusable message types."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>CO</td><td>23192</td><td>active</td></tr><tr><td style="white-space:nowrap">OB<a name="v3-hl7PublishingDomain-OB"> </a></td><td>observations</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports observations - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to resulting basic healthcare diagnostic services. "</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23193</td><td>active</td></tr><tr><td style="white-space:nowrap">OO<a name="v3-hl7PublishingDomain-OO"> </a></td><td>orders & observations</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports orders and observations - and will provide over-arching support information for the "Orders" (OR) and "Observations" (OB) domains.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23194</td><td>active</td></tr><tr><td style="white-space:nowrap">OR<a name="v3-hl7PublishingDomain-OR"> </a></td><td>orders</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports orders - and "comprises the models, messages, and other artifacts that are needed to support messaging related to ordering basic healthcare services."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23195</td><td>active</td></tr><tr><td style="white-space:nowrap">PA<a name="v3-hl7PublishingDomain-PA"> </a></td><td>patient administration</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Patient Administration - and "defines person and patient demographics and visit information about patients"</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PR</td><td>23196</td><td>active</td></tr><tr><td style="white-space:nowrap">PC<a name="v3-hl7PublishingDomain-PC"> </a></td><td>care provision</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Care Provision - and "addresses the information that is needed for the ongoing care of individuals, populations, and other targets of care."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>RE</td><td>23197</td><td>active</td></tr><tr><td style="white-space:nowrap">PH<a name="v3-hl7PublishingDomain-PH"> </a></td><td>public health</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports public health - and is "the source of a number of Common Model Element Types (CMET) designed to meet the needs of public health data exchange."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23198</td><td>active</td></tr><tr><td style="white-space:nowrap">PM<a name="v3-hl7PublishingDomain-PM"> </a></td><td>personnel management</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Personnel Management - and "spans a variety of clinical-administrative information functions associated with the organizations, individuals, animals and devices involved in the delivery and support of healthcare services."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PR</td><td>23199</td><td>active</td></tr><tr><td style="white-space:nowrap">QI<a name="v3-hl7PublishingDomain-QI"> </a></td><td>query infrastructure</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports query infrastructure - and "specifies the formation of information queries and the responses to these queries to meet the needs of healthcare applications using the HL7 version 3 messaging standard."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>QU</td><td>23200</td><td>active</td></tr><tr><td style="white-space:nowrap">QM<a name="v3-hl7PublishingDomain-QM"> </a></td><td>quality measures</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Quality Measures - and "is a standard for representing a health quality measure as an electronic document."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23201</td><td>active</td></tr><tr><td style="white-space:nowrap">RG<a name="v3-hl7PublishingDomain-RG"> </a></td><td>registries</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Registries - and "collects HL7 artifacts for administrative registries."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PR</td><td>23202</td><td>active</td></tr><tr><td style="white-space:nowrap">RI<a name="v3-hl7PublishingDomain-RI"> </a></td><td>informative public health</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Informative Public Health.</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23203</td><td>active</td></tr><tr><td style="white-space:nowrap">RP<a name="v3-hl7PublishingDomain-RP"> </a></td><td>regulated products</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Regulated Products - and "includes standards developed as part of the family of messages targeted for the exchange of information about regulated products and the exchange of the data needed to provide approval for such products."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23204</td><td>active</td></tr><tr><td style="white-space:nowrap">RR<a name="v3-hl7PublishingDomain-RR"> </a></td><td>public health reporting</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Public Health Reporting - and "includes messages and documents that are specifically designed to support managment, reporting and investigation in the public health context."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23205</td><td>active</td></tr><tr><td style="white-space:nowrap">RT<a name="v3-hl7PublishingDomain-RT"> </a></td><td>regulated studies</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Regulated Studies - and is "includes standards developed as part of the family of messages targeted for the exchange of information about the conduct of regulated studies, and the exchange of the data collected during those studies."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23206</td><td>active</td></tr><tr><td style="white-space:nowrap">RX<a name="v3-hl7PublishingDomain-RX"> </a></td><td>pharmacy</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports pharmacy - and is a "model used to derive message patterns to describe and communicate processes related to medication."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23207</td><td>active</td></tr><tr><td style="white-space:nowrap">SC<a name="v3-hl7PublishingDomain-SC"> </a></td><td>scheduling</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Scheduling - and "offers a generic set of messages and behavior to implement any number of Scheduling scenarios."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PR</td><td>23208</td><td>active</td></tr><tr><td style="white-space:nowrap">SP<a name="v3-hl7PublishingDomain-SP"> </a></td><td>specimen</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Specimen - and "comprises the models and artifacts that are needed to support the creation of messaging related to specimen."</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23209</td><td>active</td></tr><tr><td style="white-space:nowrap">TD<a name="v3-hl7PublishingDomain-TD"> </a></td><td>therapeutic devices</td><td><div><p><strong>Description:</strong> Represents the HL7 content "domain" that supports Therapeutic Devices - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to therapy delivery and observations made by a medical device. "</p>
<p><em>UsageNote:</em> V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications.</p>
</div></td><td>PO</td><td>23210</td><td>active</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingDomain"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.5.1136"/>
</identifier>
<version value="3.0.0"/>
<name value="Hl7PublishingDomain"/>
<title value="HL7PublishingDomain"/>
<status value="active"/>
<experimental value="false"/>
<date value="2019-03-20"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description
value="**Description:** Codes for HL7 publishing domains (specific content area)"/>
<copyright
value="This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
<caseSensitive value="true"/>
<hierarchyMeaning value="is-a"/>
<content value="complete"/>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Specializes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Generalizes"/>
</extension>
<code value="Specializes"/>
<description
value="The child code is a more narrow version of the concept represented by the parent code. I.e. Every child concept is also a valid parent concept. Used to allow determination of subsumption. Must be transitive, irreflexive, antisymmetric."/>
<type value="Coding"/>
</property>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
<valueCode value="antisymmetric"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
<valueCode value="transitive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
<valueCode value="irreflexive"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
<valueBoolean value="true"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Generalizes"/>
</extension>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
<valueString value="Specializes"/>
</extension>
<code value="Generalizes"/>
<description
value="Inverse of Specializes. Only included as a derived relationship."/>
<type value="Coding"/>
</property>
<property>
<extension
url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
<valueCode value="Other"/>
</extension>
<code value="OwningSubSection"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#OwningSubSection"/>
<description
value="Identifies the sub-section (target concept) of which this domain (source concept) is a part. ConceptRelationshipProperites: [isNavigable: false; functionalism: functional; reflexivity: irreflexive; symmetry: antisymetric; connected: false; transitivity: antitransitive; allowedForTargets: all codes from the hl7PublishingSubSection code system; requiredForSources: all codes from hl7PublishingDomain code system;]"/>
<type value="Coding"/>
</property>
<property>
<code value="internalId"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/>
<description
value="The internal identifier for the concept in the HL7 Access database repository."/>
<type value="code"/>
</property>
<property>
<code value="status"/>
<uri value="http://hl7.org/fhir/concept-properties#status"/>
<description
value="Designation of a concept's state. Normally is not populated unless the state is retired."/>
<type value="code"/>
</property>
<concept>
<code value="AB"/>
<display value="accounting & billing"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports accounting and billing functions - and "provides support for the creation and management of patient billing accounts and the post of financial transactions against patient billing accounts for the purpose of aggregating financial transactions that will be submitted as claims or invoices for reimbursemen"
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="FI"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23172"/>
</property>
</concept>
<concept>
<code value="AI"/>
<display value="trigger event control act infrastructure"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports trigger event control act infrastructure - and "covers the alternate structures of the message Trigger Event Control Acts in the HL7 Composite Message."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="MC"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23173"/>
</property>
</concept>
<concept>
<code value="AL"/>
<display
value="artificial listing for test purposes - faux Domain for testing"/>
<definition
value="**Description:** Represents the HL7 content "domain" that was defined as an "artificial listing" domain to support publication testing."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="RE"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23174"/>
</property>
</concept>
<concept>
<code value="BB"/>
<display value="blood tissue and organ"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports blood tissue and organ domain - and "comprises the models, messages, and other artIfacts that are needed to support messaging related to the process of blood, tissue, and organ banking operations such as donations, eligibility, storage, dispense, administration/transfusion, explantation, and implantation. "
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23175"/>
</property>
</concept>
<concept>
<code value="CD"/>
<display value="clinical document architecture"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports the clinical document architecture.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23176"/>
</property>
</concept>
<concept>
<code value="CG"/>
<display value="clinical genomics"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports clinical genomics - and includes " standards to enable the exchange of interrelated clinical and personalized genomic data between interested parties."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23178"/>
</property>
</concept>
<concept>
<code value="CI"/>
<display value="transmission infrastructure"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports transmission infrastructure - and " is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="MC"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23177"/>
</property>
</concept>
<concept>
<code value="CO"/>
<display value="coverage"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Coverage - and provides support for managing health care coverage in the reimbursement system(s).
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="FI"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23260"/>
</property>
</concept>
<concept>
<code value="CP"/>
<display value="common product model"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports the common product model - which "is used to improve the alignment between the different representations of products used within the body of HL7 Version 3 models."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23179"/>
</property>
</concept>
<concept>
<code value="CR"/>
<display value="claims and reimbursement"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Claims and Reimbursement - and "provides support for Generic, Pharmacy, Preferred Accommodation, Physician, Oral Health Vision Care and Hospital claims for eligibility, authorization, coverage extension, pre-determination, invoice adjudication, payment advice and Statement of Financial Activity (SOFA) Release 3 of this document adds claims messaging support for Physician, Oral Health Vision Care and Hospital claims."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="FI"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23180"/>
</property>
</concept>
<concept>
<code value="CS"/>
<display value="clinical statement"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports a common clinical statement pattern - and "is a 'pattern' designed to be used within multiple HL7 Version 3 domain models. This pattern is intended to facilitate the consistent design of communications that convey clinical information to meet specific use cases."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="CO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23181"/>
</property>
</concept>
<concept>
<code value="CT"/>
<display value="common types"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports common model types - and "are a work product produced by a particular committee for expressing a common, useful and reusable concept."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="CO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23182"/>
</property>
</concept>
<concept>
<code value="DD"/>
<display value="dummy domain"/>
<definition
value="**Description:** Represents the HL7 content "domain" that was created to support testing and initial set-up functions."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="UU"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23171"/>
</property>
</concept>
<concept>
<code value="DI"/>
<display value="diagnostic imaging"/>
<definition
value="**Description:** This domain has been retired in favor of "imaging integration" (II)."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23183"/>
</property>
</concept>
<concept>
<code value="DS"/>
<display value="decision support"/>
<definition
value="**Description:** Represents the HL7 content "domain" that provides decision support.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="RE"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23184"/>
</property>
</concept>
<concept>
<code value="EM"/>
<display value="emergency medical services"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Emergency Medical Services.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23261"/>
</property>
</concept>
<concept>
<code value="II"/>
<display value="imaging integration"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports imaging integration - and is "comprises the models, implementation guides, sample documents and images that are needed to illustrate the transformation of DICOM structured reports to CDA Release 2 as well as the creation of CDA diagnostic imaging reports."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23185"/>
</property>
</concept>
<concept>
<code value="IZ"/>
<display value="immunization"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports immunization - and "describes communication of information about immunization: the administration of vaccines (and/or antisera) to individuals to prevent infectious disease."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23186"/>
</property>
</concept>
<concept>
<code value="LB"/>
<display value="laboratory"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports clinical laboratory functions - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to laboratory tests or observations. "
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23187"/>
</property>
</concept>
<concept>
<code value="ME"/>
<display value="medication"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports medication - and "deals with the description of a medicine for the purposes of messaging information about medicines" and the applications of these descriptions.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23188"/>
</property>
</concept>
<concept>
<code value="MI"/>
<display value="masterfile infrastructure"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports master file infrastructure - and is "comprises the classes and attributes needed to support Master Files and Registries."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="MF"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23189"/>
</property>
</concept>
<concept>
<code value="MM"/>
<display value="materials management"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Materials Management - and is "supports the simple scenario of a Materials Management application sending requests, notifications and queries to an auxiliary application. The intent is to establish a standard for the minimum functionality that is useful and comprehensive enough to explore the important concepts relative to inventory management."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PR"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23190"/>
</property>
</concept>
<concept>
<code value="MR"/>
<display value="medical records"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports medical records - and is "supports clinical document management, and document querying."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="RC"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23191"/>
</property>
</concept>
<concept>
<code value="MT"/>
<display value="shared messages"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports shared messages - and "are a work product produced for expressing common, useful and reusable message types."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="CO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23192"/>
</property>
</concept>
<concept>
<code value="OB"/>
<display value="observations"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports observations - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to resulting basic healthcare diagnostic services. "
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23193"/>
</property>
</concept>
<concept>
<code value="OO"/>
<display value="orders & observations"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports orders and observations - and will provide over-arching support information for the "Orders" (OR) and "Observations" (OB) domains.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23194"/>
</property>
</concept>
<concept>
<code value="OR"/>
<display value="orders"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports orders - and "comprises the models, messages, and other artifacts that are needed to support messaging related to ordering basic healthcare services."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23195"/>
</property>
</concept>
<concept>
<code value="PA"/>
<display value="patient administration"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Patient Administration - and "defines person and patient demographics and visit information about patients"
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PR"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23196"/>
</property>
</concept>
<concept>
<code value="PC"/>
<display value="care provision"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Care Provision - and "addresses the information that is needed for the ongoing care of individuals, populations, and other targets of care."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="RE"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23197"/>
</property>
</concept>
<concept>
<code value="PH"/>
<display value="public health"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports public health - and is "the source of a number of Common Model Element Types (CMET) designed to meet the needs of public health data exchange."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23198"/>
</property>
</concept>
<concept>
<code value="PM"/>
<display value="personnel management"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Personnel Management - and "spans a variety of clinical-administrative information functions associated with the organizations, individuals, animals and devices involved in the delivery and support of healthcare services."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PR"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23199"/>
</property>
</concept>
<concept>
<code value="QI"/>
<display value="query infrastructure"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports query infrastructure - and "specifies the formation of information queries and the responses to these queries to meet the needs of healthcare applications using the HL7 version 3 messaging standard."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="QU"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23200"/>
</property>
</concept>
<concept>
<code value="QM"/>
<display value="quality measures"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Quality Measures - and "is a standard for representing a health quality measure as an electronic document."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23201"/>
</property>
</concept>
<concept>
<code value="RG"/>
<display value="registries"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Registries - and "collects HL7 artifacts for administrative registries."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PR"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23202"/>
</property>
</concept>
<concept>
<code value="RI"/>
<display value="informative public health"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Informative Public Health.
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23203"/>
</property>
</concept>
<concept>
<code value="RP"/>
<display value="regulated products"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Regulated Products - and "includes standards developed as part of the family of messages targeted for the exchange of information about regulated products and the exchange of the data needed to provide approval for such products."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23204"/>
</property>
</concept>
<concept>
<code value="RR"/>
<display value="public health reporting"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Public Health Reporting - and "includes messages and documents that are specifically designed to support managment, reporting and investigation in the public health context."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23205"/>
</property>
</concept>
<concept>
<code value="RT"/>
<display value="regulated studies"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Regulated Studies - and is "includes standards developed as part of the family of messages targeted for the exchange of information about the conduct of regulated studies, and the exchange of the data collected during those studies."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23206"/>
</property>
</concept>
<concept>
<code value="RX"/>
<display value="pharmacy"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports pharmacy - and is a "model used to derive message patterns to describe and communicate processes related to medication."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23207"/>
</property>
</concept>
<concept>
<code value="SC"/>
<display value="scheduling"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Scheduling - and "offers a generic set of messages and behavior to implement any number of Scheduling scenarios."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PR"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23208"/>
</property>
</concept>
<concept>
<code value="SP"/>
<display value="specimen"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Specimen - and "comprises the models and artifacts that are needed to support the creation of messaging related to specimen."
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23209"/>
</property>
</concept>
<concept>
<code value="TD"/>
<display value="therapeutic devices"/>
<definition
value="**Description:** Represents the HL7 content "domain" that supports Therapeutic Devices - and is "comprises the models, messages, and other artifacts that are needed to support messaging related to therapy delivery and observations made by a medical device. "
*UsageNote:* V3 Specifications are published in a set of "domains", which contain interactions and related specifications for a single area of health care within which can be supported by a single, coherent set of interoperability specifications."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="OwningSubSection"/>
<valueCoding>
<system
value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSubSection"/>
<code value="PO"/>
</valueCoding>
</property>
<property>
<code value="internalId"/>
<valueCode value="23210"/>
</property>
</concept>
</CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#6.0.2 based on FHIR 5.0.0. Generated 2024-07-21
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change