FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/usage-context-type (XML)

Clinical Decision Support Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Code SystemUsageContextType

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="usage-context-type"/> 
  <meta> 
    <lastUpdated value="2022-12-04T16:22:11.038+00:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> This code system 
        <code> http://terminology.hl7.org/CodeSystem/usage-context-type</code>  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> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">gender
            <a name="usage-context-type-gender"> </a> 
          </td> 
          <td> Gender</td> 
          <td> The gender of the patient. For this context type, appropriate values can be found
             in the http://hl7.org/fhir/ValueSet/administrative-gender value set.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">age
            <a name="usage-context-type-age"> </a> 
          </td> 
          <td> Age Range</td> 
          <td> The age of the patient. For this context type, the value could be a range that
             specifies the applicable ages or a code from an appropriate value set such as the
             MeSH value set http://terminology.hl7.org/ValueSet/v3-AgeGroupObservationValue.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">focus
            <a name="usage-context-type-focus"> </a> 
          </td> 
          <td> Clinical Focus</td> 
          <td> The clinical concept(s) addressed by the artifact. For example, disease, diagnostic
             test interpretation, medication ordering as in http://hl7.org/fhir/ValueSet/condition-code.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">user
            <a name="usage-context-type-user"> </a> 
          </td> 
          <td> User Type</td> 
          <td> The clinical specialty of the context in which the patient is being treated - For
             example, PCP, Patient, Cardiologist, Behavioral Professional, Oral Health Professional,
             Prescriber, etc... taken from a specialty value set such as the NUCC Health Care
             provider taxonomy value set http://hl7.org/fhir/ValueSet/provider-taxonomy.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">workflow
            <a name="usage-context-type-workflow"> </a> 
          </td> 
          <td> Workflow Setting</td> 
          <td> The settings in which the artifact is intended for use. For example, admission,
             pre-op, etc. For example, the ActEncounterCode value set http://terminology.hl7.org/ValueSet/
            v3-ActEncounterCode.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">task
            <a name="usage-context-type-task"> </a> 
          </td> 
          <td> Workflow Task</td> 
          <td> The context for the clinical task(s) represented by this artifact. For example,
             this could be any task context represented by the HL7 ActTaskCode value set http://terminolog
            y.hl7.org/ValueSet/v3-ActTaskCode. General categories include: order entry, patient
             documentation and patient information review.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">venue
            <a name="usage-context-type-venue"> </a> 
          </td> 
          <td> Clinical Venue</td> 
          <td> The venue in which an artifact could be used. For example, Outpatient, Inpatient,
             Home, Nursing home. The code value may originate from the HL7 ServiceDeliveryLocationRoleType
             value set (http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType).</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">species
            <a name="usage-context-type-species"> </a> 
          </td> 
          <td> Species</td> 
          <td> The species to which an artifact applies. For example, SNOMED - 387961004 | Kingdom
             Animalia (organism).</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">program
            <a name="usage-context-type-program"> </a> 
          </td> 
          <td> Program</td> 
          <td> A program/project of work for which this artifact is applicable.</td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">agreement-scope
            <a name="usage-context-type-agreement-scope"> </a> 
          </td> 
          <td> Agreement Acope</td> 
          <td> Describes the level and scope of agreement within the artifact.  Appropriate values
             can be found in the usage-context-agreement-scope value set.</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="5"/> 
  </extension> 
  <url value="http://terminology.hl7.org/CodeSystem/usage-context-type"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.1.1068"/> 
  </identifier> 
  <version value="5.0.0-cibuild"/> 
  <name value="UsageContextType"/> 
  <title value="UsageContextType"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2022-12-04T16:22:11+00:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="A code that specifies a type of context being specified by a usage context."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://hl7.org/fhir/ValueSet/usage-context-type"/> 
  <content value="complete"/> 
  <concept> 
    <code value="gender"/> 
    <display value="Gender"/> 
    <definition value="The gender of the patient. For this context type, appropriate values can be found
     in the http://hl7.org/fhir/ValueSet/administrative-gender value set."/> 
  </concept> 
  <concept> 
    <code value="age"/> 
    <display value="Age Range"/> 
    <definition value="The age of the patient. For this context type, the value could be a range that
     specifies the applicable ages or a code from an appropriate value set such as the
     MeSH value set http://terminology.hl7.org/ValueSet/v3-AgeGroupObservationValue."/> 
  </concept> 
  <concept> 
    <code value="focus"/> 
    <display value="Clinical Focus"/> 
    <definition value="The clinical concept(s) addressed by the artifact. For example, disease, diagnostic
     test interpretation, medication ordering as in http://hl7.org/fhir/ValueSet/condition-code."/> 
  </concept> 
  <concept> 
    <code value="user"/> 
    <display value="User Type"/> 
    <definition value="The clinical specialty of the context in which the patient is being treated - For
     example, PCP, Patient, Cardiologist, Behavioral Professional, Oral Health Professional,
     Prescriber, etc... taken from a specialty value set such as the NUCC Health Care
     provider taxonomy value set http://hl7.org/fhir/ValueSet/provider-taxonomy."/> 
  </concept> 
  <concept> 
    <code value="workflow"/> 
    <display value="Workflow Setting"/> 
    <definition value="The settings in which the artifact is intended for use. For example, admission,
     pre-op, etc. For example, the ActEncounterCode value set http://terminology.hl7.org/ValueSet/
    v3-ActEncounterCode."/> 
  </concept> 
  <concept> 
    <code value="task"/> 
    <display value="Workflow Task"/> 
    <definition value="The context for the clinical task(s) represented by this artifact. For example,
     this could be any task context represented by the HL7 ActTaskCode value set http://terminolog
    y.hl7.org/ValueSet/v3-ActTaskCode. General categories include: order entry, patient
     documentation and patient information review."/> 
  </concept> 
  <concept> 
    <code value="venue"/> 
    <display value="Clinical Venue"/> 
    <definition value="The venue in which an artifact could be used. For example, Outpatient, Inpatient,
     Home, Nursing home. The code value may originate from the HL7 ServiceDeliveryLocationRoleType
     value set (http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType)."/> 
  </concept> 
  <concept> 
    <code value="species"/> 
    <display value="Species"/> 
    <definition value="The species to which an artifact applies. For example, SNOMED - 387961004 | Kingdom
     Animalia (organism)."/> 
  </concept> 
  <concept> 
    <code value="program"/> 
    <display value="Program"/> 
    <definition value="A program/project of work for which this artifact is applicable."/> 
  </concept> 
  <concept> 
    <code value="agreement-scope"/> 
    <display value="Agreement Acope"/> 
    <definition value="Describes the level and scope of agreement within the artifact.  Appropriate values
     can be found in the usage-context-agreement-scope value set."/> 
  </concept> 
</CodeSystem> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.