This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

HL7PublishingSection - XML Representation

(back to description)

Raw xml

Source view

<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"><h2>HL7PublishingSection</h2><div><p><strong>Description:</strong> Codes for HL7 publishing sections (major business categories)</p>
</div><p><b>Properties</b></p><table class="grid"><tr><td><b>Code</b></td><td><b>URL</b></td><td><b>Description</b></td><td><b>Type</b></td></tr><tr><td>Specializes</td><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><td>Coding</td></tr><tr><td>Generalizes</td><td/><td>Inverse of Specializes.  Only included as a derived relationship.</td><td>Coding</td></tr><tr><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>The internal identifier for the concept in the HL7 Access database repository.</td><td>code</td></tr><tr><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>Designation of a concept's state. Normally is not populated unless the state is retired.</td><td>code</td></tr></table><p>This code system http://terminology.hl7.org/CodeSystem/v3-hl7PublishingSection defines the following codes:</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>**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 &quot;domains&quot;, 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.</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>**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 &quot;domains&quot;, 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.</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>**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 &quot;domains&quot;, 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.</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>**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 &quot;domains&quot;, 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.</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="2.0.0"/>
  <name value="Hl7PublishingSection"/>
  <title value="HL7PublishingSection"/>
  <status value="active"/>
  <date value="2019-03-20T00:00:00-04:00"/>
  <publisher value="HL7 International"/>
  <contact>
    <name value="Modeling and Methodology Workgroup"/>
  </contact>
  <description
               value="**Description:** Codes for HL7 publishing sections (major business categories)"/>
  <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&#39;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 &quot;domains&quot;, 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 &quot;domains&quot;, 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 &quot;domains&quot;, 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 &quot;domains&quot;, 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>