FHIR Release 3 (STU) 5 Ballot

This page is part of the FHIR Specification (v3.0.2: STU (v5.0.0-ballot: R5 Ballot - see ballot notes 3). ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Valueset-task-performer-type.json Vocabulary
Work Group Vocabulary icon Maturity Level : N/A Ballot Standards Status : Informative

4.0 Terminology Module

4.0.1 Introduction

The Terminology Module provides an overview and guide to the FHIR resources, operations, coded datatypes and externally-defined standard and FHIR-defined terminologies that are used for representing and communicating coded, structured data in the FHIR core specification and profiles. Collectively, these capabilities are used to provide the terminology service functionality required for supporting the use of coded data in FHIR resources throughout the specification as described in the other modules.

The primary terminology-related structures and their relationships are shown below:

Image showing the terminology resources and relationships

Example: Condition profile with Condition.code slice bound to "SNOMED CT fracture codes" value set

[Note: The ElementDefinition type (shown with a dotted box) is described elsewhere in the specification in the Foundation and Conformance modules.]

4.0.2 Index

The Terminology Module covers the following:

Resources

Raw JSON Terminology Service

Operations

  • CodeSystem
  • ValueSet
  • ConceptMap

Coded Datatypes

Definition for Documentation

4.0.3 Security and Privacy

For security considerations for terminology services, see the Terminology Service page Security section . For more general considerations, see the Security and Privacy module .

{ "resourceType": "ValueSet", "id": "task-performer-type", "meta": { "lastUpdated": "2019-10-24T11:53:00+11:00", "profile": [ "http://hl7.org/fhir/StructureDefinition/shareablevalueset" ] }, "text": { "status": "generated", "div": "<div>!-- Snipped for Brevity --></div>" }, "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status", "valueString": "Informative" }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger": 2 }, { "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode": "oo" } ], "url": "http://hl7.org/fhir/ValueSet/task-performer-type", "identifier": [ { "system": "urn:ietf:rfc:3986", "value": "urn:oid:2.16.840.1.113883.4.642.3.771" } ], "version": "3.0.2", "name": "TaskPerformerType", "status": "draft", "experimental": false, "date": "2019-10-24T11:53:00+11:00", "publisher": "HL7 (FHIR Project)", "contact": [ { "telecom": [ { "system": "url", "value": "http://hl7.org/fhir" }, { "system": "email", "value": "fhir@lists.hl7.org" } ] } ], "description": "The type(s) of task performers allowed", "immutable": true, "compose": { "include": [ { "system": "http://hl7.org/fhir/task-performer-type" } ] } }

4.0.4 Common Use Cases

Usage note: every effort has been made

  • Create or reference a code system
  • Create or reference a value set
  • Record data using pre-coordinated codes
  • Record data using post-coordinated expressions
  • Record data using multiple local or standard code systems (translations)
  • Expand a value set
  • Validate a code
  • Look up a display term for a code
  • Translate a code from one value set to ensure that another
  • Maintain a client-side transitive closure table icon on subsumption relationships
  • Test subsumption between concepts
  • For a set of property/concept pairs, return the examples set of concepts for the requested properties
  • Map data between different terminologies
  • Declare the capabilities of a terminology service

4.0.5 Development Roadmap

The following terminology resources have been tested and are correct being used in production tooling and useful, but they now are not a normative part or are expected soon to progress to normative.

Other terminology resources are still in earlier stages of development. We intend to continue to develop and test these resources and advance them through the specification. Maturity Levels at Connectathons and elsewhere.