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

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r4b
Resource TypeValueSet
IdValueSet-R5-v3-xActClassCareProvisionObservation-for-R4B.json
FHIR VersionR4B
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/ValueSet-R5-v3-xActClassCareProvisionObservation-for-R4B.html
URLhttp://hl7.org/fhir/5.0/ValueSet/R5-v3-xActClassCareProvisionObservation-for-R4B
Version0.0.1-snapshot-2
Statusactive
Date2025-09-01T22:37:05.479766+10:00
NameR5_v3_xActClassCareProvisionObservation_for_R4B
TitleCross-version VS for R5.XActClassCareProvisionObservation for use in FHIR R4B
Realmuv
Authorityhl7
DescriptionThis cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-xActClassCareProvisionObservation|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B.

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
v3-ActClassActClass

Narrative

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

Generated Narrative: ValueSet R5-v3-xActClassCareProvisionObservation-for-R4B

This value set expansion contains 2 concepts.

CodeSystemDisplayDefinition
  OBShttp://terminology.hl7.org/CodeSystem/v3-ActClassobservation

**Description:**An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The code attribute of Observation and the value attribute of Observation must be considered in combination to determine the semantics of the observation.

Discussion:

Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.

As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects.

The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.

An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.

Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC.

Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.

Examples:

  • Recording the results of a Family History Assessment
  • Laboratory test and associated result
  • Physical exam test and associated result
  • Device temperature
  • Soil lead level
  PCPRhttp://terminology.hl7.org/CodeSystem/v3-ActClasscare provision

An Act that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care.

Discussion: A care provision event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.

In request (RQO) mood care provision communicates a referral, which is a request:

  • from one party (linked as a participant of type author (AUT)),
  • to another party (linked as a participant of type performer (PRF),
  • to take responsibility for a scope specified by the code attribute,
  • for an entity (linked as a participant of type subject (SBJ)).

The scope of the care for which responsibility is taken is identified by code attribute.

In event (EVN) mood care provision indicates the effective time interval of a specified scope of responsibility by a performer (PRF) or set of performers (PRF) for a subject (SBJ).

Examples:

  1. Referral from GP to a specialist.
  2. Assignment of a patient or group of patients to the case list of a health professional.
  3. Assignment of inpatients to the care of particular nurses for a working shift.

Source1

{
  "resourceType": "ValueSet",
  "id": "R5-v3-xActClassCareProvisionObservation-for-R4B",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "extension": [
        {
          "url": "packageId",
          "valueId": "hl7.fhir.uv.xver-r5.r4b"
        },
        {
          "url": "version",
          "valueString": "0.0.1-snapshot-2"
        }
      ],
      "url": "http://hl7.org/fhir/StructureDefinition/package-source"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
          }
        ]
      }
    },
    {
      "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/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/5.0/ValueSet/R5-v3-xActClassCareProvisionObservation-for-R4B",
  "version": "0.0.1-snapshot-2",
  "name": "R5_v3_xActClassCareProvisionObservation_for_R4B",
  "title": "Cross-version VS for R5.XActClassCareProvisionObservation for use in FHIR R4B",
  "status": "active",
  "experimental": false,
  "date": "2025-09-01T22:37:05.479766+10:00",
  "publisher": "FHIR Infrastructure",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-xActClassCareProvisionObservation|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "compose": {
    "include": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActClass",
        "version": "3.1.1",
        "concept": [
          {
            "code": "OBS",
            "display": "observation"
          },
          {
            "code": "PCPR",
            "display": "care provision"
          }
        ]
      }
    ]
  },
  "expansion": {
    "timestamp": "2025-09-01T22:37:05.479766+10:00",
    "contains": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActClass",
        "version": "3.1.1",
        "code": "OBS",
        "display": "observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActClass",
        "version": "3.1.1",
        "code": "PCPR",
        "display": "care provision"
      }
    ]
  }
}