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-ActMoodRequest-for-R4B.json
FHIR VersionR4B
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/ValueSet-R5-v3-ActMoodRequest-for-R4B.html
URLhttp://hl7.org/fhir/5.0/ValueSet/R5-v3-ActMoodRequest-for-R4B
Version0.0.1-snapshot-2
Statusactive
Date2025-09-01T22:37:04.918407+10:00
NameR5_v3_ActMoodRequest_for_R4B
TitleCross-version VS for R5.ActMoodRequest for use in FHIR R4B
Realmuv
Authorityhl7
DescriptionThis cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActMoodRequest|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-ActMoodActMood

Narrative

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

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

This value set expansion contains 1 concepts.

CodeSystemDisplayDefinition
  RQOhttp://terminology.hl7.org/CodeSystem/v3-ActMoodrequest

Definition: A request act that is specialized for an event request/fulfillment cycle.

UsageNotes: The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.

UsageNotes: The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request."

Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.

The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.


Source1

{
  "resourceType": "ValueSet",
  "id": "R5-v3-ActMoodRequest-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-ActMoodRequest-for-R4B",
  "version": "0.0.1-snapshot-2",
  "name": "R5_v3_ActMoodRequest_for_R4B",
  "title": "Cross-version VS for R5.ActMoodRequest for use in FHIR R4B",
  "status": "active",
  "experimental": false,
  "date": "2025-09-01T22:37:04.918407+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-ActMoodRequest|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-ActMood",
        "version": "2.1.0",
        "concept": [
          {
            "code": "RQO",
            "display": "request"
          }
        ]
      }
    ]
  },
  "expansion": {
    "timestamp": "2025-09-01T22:37:04.918408+10:00",
    "contains": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActMood",
        "version": "2.1.0",
        "code": "RQO",
        "display": "request"
      }
    ]
  }
}