FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.us.davinci-hrex
Resource TypeCodeSystem
IdCodeSystem-hrex-temp.json
FHIR VersionR4
Sourcehttps://build.fhir.org/ig/HL7/davinci-ehrx/CodeSystem-hrex-temp.html
URLhttp://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
Version1.2.0-snapshot
Statusactive
Date2026-01-30T17:35:03+00:00
NameHRexTempCodes
TitleHRex Temporary Code System
Realmus
Authorityhl7
DescriptionCodes temporarily defined as part of the HRex implementation guide. These will eventually migrate into an officially maintained terminology (likely HL7's UTG code systems).
Contentcomplete

Resources that use this resource

ValueSet
cs-categoriesHRex Conformance Statement Categories

Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: CodeSystem hrex-temp

Properties

This code system defines the following properties for its concepts

NameCodeURIType
Not Selectableabstracthttp://hl7.org/fhir/concept-properties#notSelectableboolean

Concepts

This case-sensitive code system http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp defines the following codes in a Is-A hierarchy:

LvlCodeDisplayDefinitionNot Selectable
1data-request data request taskA type of Task asking the owner to deliver the data corresponding to the characteristics defined by the Task.inputs to the Task.beneficiary
1data-query data query inputIndicates the parameters of a FHIR RESTful search to be executed whose results are requested. The content will be the query URL following the 'base'. E.g. `Observation?...`
1data-code data code inputA code for a document or otherwise describing the characteristics of the information requested
1data-value data values outputThe result of a data request
1UMB Unique Product-independent Payer Person IdentifierA unique identifier assigned to an individual that is consistent regardless of the individual irrespective of their role (subscriber, dependent, etc.) or which product(s) they have with that payer.
1_reqcat Requirements CategoriesCodes that help to categorize requirements statementstrue
2  business businessRequirements relating to the business operations of the entities responsible for a system
2  exchange exchangeRequirements relating to when or how data is exchanged with other systems
2  processing processingRequirements related to how data is dealt with internally to a system
2  storage storageRequirements relating to when or how data is or is not persisted within a system
2  ui uiRequirements relating to the appearance of information on a user interface

Source1

{
  "resourceType": "CodeSystem",
  "id": "hrex-temp",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "cic"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 3,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/davinci-hrex"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/davinci-hrex"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp",
  "identifier": [
    {
      "system": "urn:ietf:rfc:3986",
      "value": "urn:oid:2.16.840.1.113883.4.642.40.19.16.1"
    }
  ],
  "version": "1.2.0-snapshot",
  "name": "HRexTempCodes",
  "title": "HRex Temporary Code System",
  "status": "active",
  "experimental": false,
  "date": "2026-01-30T17:35:03+00:00",
  "publisher": "HL7 International / Clinical Interoperability Council",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/cic"
        }
      ]
    }
  ],
  "description": "Codes temporarily defined as part of the HRex implementation guide.  These will eventually migrate into an officially maintained terminology (likely HL7's UTG code systems).",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "urn:iso:std:iso:3166",
          "code": "US"
        }
      ]
    }
  ],
  "caseSensitive": true,
  "hierarchyMeaning": "is-a",
  "content": "complete",
  "count": 11,
  "property": [
    {
      "code": "abstract",
      "uri": "http://hl7.org/fhir/concept-properties#notSelectable",
      "type": "boolean"
    }
  ],
  "concept": [
    {
      "code": "data-request",
      "display": "data request task",
      "definition": "A type of Task asking the owner to deliver the data corresponding to the characteristics defined by the Task.inputs to the Task.beneficiary"
    },
    {
      "code": "data-query",
      "display": "data query input",
      "definition": "Indicates the parameters of a FHIR RESTful search to be executed whose results are requested.  The content will be the query URL following the 'base'.  E.g. `Observation?...`"
    },
    {
      "code": "data-code",
      "display": "data code input",
      "definition": "A code for a document or otherwise describing the characteristics of the information requested"
    },
    {
      "code": "data-value",
      "display": "data values output",
      "definition": "The result of a data request"
    },
    {
      "code": "UMB",
      "display": "Unique Product-independent Payer Person Identifier",
      "definition": "A unique identifier assigned to an individual that is consistent regardless of the individual irrespective of their role (subscriber, dependent, etc.) or which product(s) they have with that payer."
    },
    {
      "code": "_reqcat",
      "display": "Requirements Categories",
      "definition": "Codes that help to categorize requirements statements",
      "property": [
        {
          "code": "abstract",
          "valueBoolean": true
        }
      ],
      "concept": [
        {
          "code": "business",
          "display": "business",
          "definition": "Requirements relating to the business operations of the entities responsible for a system"
        },
        {
          "code": "exchange",
          "display": "exchange",
          "definition": "Requirements relating to when or how data is exchanged with other systems"
        },
        {
          "code": "processing",
          "display": "processing",
          "definition": "Requirements related to how data is dealt with internally to a system"
        },
        {
          "code": "storage",
          "display": "storage",
          "definition": "Requirements relating to when or how data is or is not persisted within a system"
        },
        {
          "code": "ui",
          "display": "ui",
          "definition": "Requirements relating to the appearance of information on a user interface"
        }
      ]
    }
  ]
}