This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/research-subject-state-type |
Version: | 4.1.0 |
Name: | ResearchSubjectStateType |
Status: | draft |
Title: | ResearchSubjectStateType |
Definition: | Identifies the kind of state being refered to. |
Publisher: | HL7 (FHIR Project) |
Committee: | Biomedical Research and Regulation |
OID: | 2.16.840.1.113883.4.642.3.0 (for OID based terminology systems) |
Maturity: | 1 |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/research-subject-state-type
This value set contains 2 concepts
Expansion based on ResearchSubjectStateType v4.2.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/research-subject-state-type
Code | Display | Definition |
Milestone | Milestone status | One of a set of milestone events that once they have occurred remain true thereafter. For example once a subject has reached the "Signed Informed Consent" milestone they achieve a status of "Consented" that will be true thereafter, even when they have left the study. For a subject a number of these states can be simulataneously true and should be recorded. |
Enrollment | Enrollment status | This is a status that can only have a single value at a given point in time. The subject is either on-study or off-study. |
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 |
Source | 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
Date | Action | Custodian | Author | Comment |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |