ResMed Core Implementation Guide
0.37.0 - ci-build
ResMed Core Implementation Guide
0.37.0 - ci-build
ResMed Core Implementation Guide - Local Development build (v0.37.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://resmed.com/fhir/core/ValueSet/rmd-fhirHoseRole-vs | Version: 0.37.0 | |||
| Draft as of 2024-01-11 | Computable Name: ValueSetResMedFhirHoseRole | |||
A value set of roles of entities contributing to a FHIR Hose Provenance
References
http://hl7.org/fhir/provenance-entity-role| Code | Display | Definition |
| source | Source | A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. |
| removal | Removal | A derivation for which the entity is removed from accessibility usually through the use of the Delete operation. |
Expansion based on codesystem ProvenanceEntityRole v4.0.1 (CodeSystem)
This value set contains 2 concepts
| Code | System | Display | Definition |
| source | http://hl7.org/fhir/provenance-entity-role | Source | A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. |
| removal | http://hl7.org/fhir/provenance-entity-role | Removal | A derivation for which the entity is removed from accessibility usually through the use of the Delete operation. |
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 |