HL7 Terminology (THO)
6.0.1 - Publication International flag

This page is part of the HL7 Terminology (v6.0.1: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: x_ActClassCareProvisionEncounter

Official URL: http://terminology.hl7.org/ValueSet/v3-xActClassCareProvisionEncounter Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: XActClassCareProvisionEncounter
Other Identifiers: OID:2.16.840.1.113883.1.11.19887

Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Definition: When identifying the “request” that resulted in an encounter, there is a need to distinguish whether the “request” was a general referral (CareProvisionRequest) or a more specific ordered or scheduled encounter (PatientEncounter).

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Generated Narrative: ValueSet v3-xActClassCareProvisionEncounter

Language: en

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActClass
    CodeDisplayDefinition
    ENCencounterAn interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.
    PCPRcare provisionAn **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.

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActClass v4.0.0 (CodeSystem)

This value set contains 2 concepts

CodeSystemDisplayDefinition
  ENChttp://terminology.hl7.org/CodeSystem/v3-ActClassencounter

An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.

  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.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionAuthorCustodianComment
2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26