HL7 Terminology (THO)
6.1.0 - Publication
This page is part of the HL7 Terminology (v6.1.0: 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-hl7PublishingSection"/>
<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-hl7PublishingSection</b></p><a name="v3-hl7PublishingSection"> </a><a name="hcv3-hl7PublishingSection"> </a><a name="v3-hl7PublishingSection-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>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-hl7PublishingSection</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>internalId</b></td><td><b>Status</b></td></tr><tr><td style="white-space:nowrap">AM<a name="v3-hl7PublishingSection-AM"> </a></td><td>administrative management</td><td><div><p><strong>Description:</strong> Represents the HL7 V3 publishing section that deals with the administration and management of health care activities and organizations.</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>
<p>For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets.</p>
</div></td><td>23156</td><td>active</td></tr><tr><td style="white-space:nowrap">HM<a name="v3-hl7PublishingSection-HM"> </a></td><td>health and clinical management</td><td><div><p><strong>Description:</strong> Represents the HL7 V3 publishing section that deals with the health care provision and clinical 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>
<p>For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets.</p>
</div></td><td>23155</td><td>active</td></tr><tr><td style="white-space:nowrap">IM<a name="v3-hl7PublishingSection-IM"> </a></td><td>infrastructure management</td><td><div><p><strong>Description:</strong> Represents the HL7 V3 publishing section that deals with the definition and management of the computing and communication infrastructure necessary to support health 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>
<p>For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets.</p>
</div></td><td>23157</td><td>active</td></tr><tr><td style="white-space:nowrap">UU<a name="v3-hl7PublishingSection-UU"> </a></td><td>unknown</td><td><div><p><strong>Description:</strong> Represents the HL7 V3 publishing section that holds specifications that are unassigned - that have not yet been assigned to one of the formal publishing sections.</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>
<p>For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets.</p>
</div></td><td>23158</td><td>active</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSection"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.5.1133"/>
</identifier>
<version value="3.0.0"/>
<name value="Hl7PublishingSection"/>
<title value="HL7PublishingSection"/>
<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 sections (major business categories)"/>
<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>
<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="AM"/>
<display value="administrative management"/>
<definition
value="**Description:** Represents the HL7 V3 publishing section that deals with the administration and management of health care activities and organizations.
*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.
For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="23156"/>
</property>
</concept>
<concept>
<code value="HM"/>
<display value="health and clinical management"/>
<definition
value="**Description:** Represents the HL7 V3 publishing section that deals with the health care provision and clinical 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.
For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="23155"/>
</property>
</concept>
<concept>
<code value="IM"/>
<display value="infrastructure management"/>
<definition
value="**Description:** Represents the HL7 V3 publishing section that deals with the definition and management of the computing and communication infrastructure necessary to support health 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.
For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="23157"/>
</property>
</concept>
<concept>
<code value="UU"/>
<display value="unknown"/>
<definition
value="**Description:** Represents the HL7 V3 publishing section that holds specifications that are unassigned - that have not yet been assigned to one of the formal publishing sections.
*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.
For publishing purposes, these domains are aggregated into sub-sections of related health care areas and these sub-sections are further aggregated into three major sets."/>
<property>
<code value="status"/>
<valueCode value="active"/>
</property>
<property>
<code value="internalId"/>
<valueCode value="23158"/>
</property>
</concept>
</CodeSystem>