FHIR IG analytics| Package | hl7.fhir.uv.xver-r4.r3 |
| Resource Type | ValueSet |
| Id | ValueSet-R4-v3-PurposeOfUse-for-R3.json |
| FHIR Version | R3 |
| Source | http://hl7.org/fhir/uv/xver-r4.r3/0.1.0/ValueSet-R4-v3-PurposeOfUse-for-R3.html |
| URL | http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-PurposeOfUse-for-R3 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T21:02:03.8104715+00:00 |
| Name | R4V3PurposeOfUseForR3 |
| Title | Cross-version ValueSet R4.v3.PurposeOfUse for use in FHIR STU3 |
| Realm | uv |
| Authority | hl7 |
| Description | This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2014-03-26 for use in FHIR STU3 that is appropriate for use but unavailable in `http://hl7.org/fhir/ValueSet/v3-PurposeOfUse|2014-03-26`. |
| Purpose | This value set is part of the cross-version definitions generated to enable use of the value set `http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2014-03-26` as defined in FHIR R4 in FHIR STU3. The source value set is bound to the following FHIR R4 elements: * `AuditEvent.agent.purposeOfUse` * `AuditEvent.purposeOfEvent` * `Consent.provision.purpose` * `Contract.term.action.intent` * `Contract.term.action.reasonCode` * `Provenance.reason` Note that there are 43 concepts not included in this cross-version definition because they have valid representations. Following are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source value set has more active concepts (60) than the target (43), so the source is broader than the target. |
| StructureDefinition | ||
| hl7.fhir.uv.xver-r4.r3#0.1.0 | extension-Consent.provision | R4: Constraints to the base Consent.policyRule |
| hl7.fhir.uv.xver-r4.r3#0.1.0 | extension-Contract.term.action.intent | R4: Purpose for the Contract Term Action (new) |
| hl7.fhir.uv.xver-r4.r3#0.1.0 | extension-Provenance.reason | R4: reason additional types |
| CodeSystem | ||
| hl7.terminology#current | v3-ActReason | ActReason |
Note: links and images are rebased to the (stated) source
Generated Narrative: ValueSet R4-v3-PurposeOfUse-for-R3
This value set expansion contains 17 concepts.
| System | Version | Code | Display | Definition |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | BIORCH | biomedical research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified biomedical basic or applied research. For example, research on rare plants to determine whether biologic properties may be useful for pharmaceutical development. May be used in combination with clinical trial and other healthcare research purposes of use. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | BTG | break the glass | To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access.
The ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | CLINTRCHNPC | clinical trial research without patient care | To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge without provision of patient care. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, a clinical trial conducted on laboratory specimens collected from a specified patient population. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | CLINTRCHPC | clinical trial research with patient care | To perform one or more operations on information for conducting scientific investigations with patient care in accordance with clinical trial protocols to obtain health care knowledge. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, an "off-label" drug used for cancer therapy administer to a specified patient population. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | COC | coordination of care | To perform one or more actions on information in order to organize the provision and case management of an individual’s healthcare, including: Monitoring a person's goals, needs, and preferences; acting as the communication link between two or more participants concerned with a person's health and wellness; organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person; and ensuring safe, appropriate, non-duplicative, and effective integrated care.
|
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | DSRCH | disease specific healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified conditions, diagnosis, or disease healthcare research. For example, conducting cancer research by testing reaction of tumor cells to certain biologics. May be used in combination with clinical trial and other healthcare research purposes of use. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | ERTREAT | emergency room treatment | To perform one or more operations on information for provision of immediately needed health care for an emergent condition in an emergency room or similar emergent care context by end users provisioned for this purpose, which does not constitute as policy override such as in a "Break the Glass" purpose of use.
|
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | HDM | healthcare delivery management | To perform one or more actions on information used for conducting administrative and contractual activities by or on behalf of organizational entities responsible for delivery of an individual's benefits in a healthcare program, health plan or insurance. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment.
|
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | HTEST | test health data | To perform one or more operations on information that is simulated or synthetic health data used for testing system capabilities outside of a production or operational system environment.
|
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | LABELING | labeling | To perform one or more operations on information to assign, persist, and manage labels to healthcare data to characterize various aspects, such as its security classification, sensitivity, compartment, integrity, and provenance; applicable privacy, consent, security, provenance, and trust policies; and handling caveats such as purpose of use, obligations, and refrain policies.
|
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | METAMGT | metadata management | To perform one or more operations on information to assign, persist, and manage metadata to healthcare data to characterize various aspects used for its indexing, discovery, retrieval, and processing by systems, applications, and end users. For example, master index identifier, media type, and location. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | MILCDM | military command | To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | MILDCRG | military discharge | To perform one or more operations on information for the process of releasing military personnel from their service obligations, which may include determining service merit, discharge benefits, and disability assessment. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | POARCH | population origins or ancestry healthcare research | To perform one or more operations on information, including genealogical pedigrees, historical records, surveys, family health data, health records, and genetic information, for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to population origins and/or ancestry healthcare research. For example, gathering genetic specimens from a specific population in order to determine the ancestry and population origins of that group. May be used in combination with clinical trial and other healthcare research purposes of use. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | PRECLINTRCH | preclinical trial research | To perform one or more operations on information in preparation for conducting scientific investigation to obtain health care knowledge, such as research on animals or review of patient health records, to determine the feasibility of a clinical trial study; assist with protocol design; or in preparation for institutional review board or ethics committee approval process. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | SYSDEV | system development | To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application. |
http://terminology.hl7.org/CodeSystem/v3-ActReason | 2018-08-12 | TRANSRCH | translational healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge related to evidence based medicine during the course of providing healthcare treatment. Sometimes referred to as "bench to bedside", which is the iterative feedback loop between healthcare research and clinical trials with input from information collected in the course of routine provision of healthcare. For example, by extending a patient encounter to conduct a survey related to a research topic such as attitudes about use of a wellness device that a patient agreed to use. May be used in combination with clinical trial and other healthcare research purposes of use. |
{
"resourceType": "ValueSet",
"id": "R4-v3-PurposeOfUse-for-R3",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 3
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "sec"
},
{
"extension": [
{
"url": "packageId",
"valueId": "hl7.fhir.uv.xver-r4.r3"
},
{
"url": "version",
"valueString": "0.1.0"
},
{
"url": "uri",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r3"
}
],
"url": "http://hl7.org/fhir/StructureDefinition/package-source"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r3"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-PurposeOfUse-for-R3",
"version": "0.1.0",
"name": "R4V3PurposeOfUseForR3",
"title": "Cross-version ValueSet R4.v3.PurposeOfUse for use in FHIR STU3",
"status": "active",
"experimental": false,
"date": "2026-03-17T21:02:03.8104715+00:00",
"publisher": "Security",
"contact": [
{
"name": "Security",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/secure"
}
]
}
],
"description": "This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2014-03-26 for use in FHIR STU3 that is appropriate for use but unavailable in `http://hl7.org/fhir/ValueSet/v3-PurposeOfUse|2014-03-26`.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"purpose": "This value set is part of the cross-version definitions generated to enable use of the\r\nvalue set `http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|2014-03-26` as defined in FHIR R4\r\nin FHIR STU3.\r\n\r\nThe source value set is bound to the following FHIR R4 elements:\r\n* `AuditEvent.agent.purposeOfUse`\n* `AuditEvent.purposeOfEvent`\n* `Consent.provision.purpose`\n* `Contract.term.action.intent`\n* `Contract.term.action.reasonCode`\n* `Provenance.reason`\r\n\r\nNote that there are 43 concepts not included in this cross-version definition because they have valid representations.\r\n\r\nFollowing are the generation technical comments:\r\nOne or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened.\nThe source value set has more active concepts (60) than the target (43), so the source is broader than the target.",
"compose": {
"include": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"concept": [
{
"code": "BIORCH",
"display": "biomedical research"
},
{
"code": "BTG",
"display": "break the glass"
},
{
"code": "CLINTRCHNPC",
"display": "clinical trial research without patient care"
},
{
"code": "CLINTRCHPC",
"display": "clinical trial research with patient care"
},
{
"code": "COC",
"display": "coordination of care"
},
{
"code": "DSRCH",
"display": "disease specific healthcare research"
},
{
"code": "ERTREAT",
"display": "emergency room treatment"
},
{
"code": "HDM",
"display": "healthcare delivery management"
},
{
"code": "HTEST",
"display": "test health data"
},
{
"code": "LABELING",
"display": "labeling"
},
{
"code": "METAMGT",
"display": "metadata management"
},
{
"code": "MILCDM",
"display": "military command"
},
{
"code": "MILDCRG",
"display": "military discharge"
},
{
"code": "POARCH",
"display": "population origins or ancestry healthcare research"
},
{
"code": "PRECLINTRCH",
"display": "preclinical trial research"
},
{
"code": "SYSDEV",
"display": "system development"
},
{
"code": "TRANSRCH",
"display": "translational healthcare research"
}
]
}
]
},
"expansion": {
"timestamp": "2026-03-17T21:02:03.8104715+00:00",
"contains": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "BIORCH",
"display": "biomedical research"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "BTG",
"display": "break the glass"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "CLINTRCHNPC",
"display": "clinical trial research without patient care"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "CLINTRCHPC",
"display": "clinical trial research with patient care"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "COC",
"display": "coordination of care"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "DSRCH",
"display": "disease specific healthcare research"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "ERTREAT",
"display": "emergency room treatment"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "HDM",
"display": "healthcare delivery management"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "HTEST",
"display": "test health data"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "LABELING",
"display": "labeling"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "METAMGT",
"display": "metadata management"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "MILCDM",
"display": "military command"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "MILDCRG",
"display": "military discharge"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "POARCH",
"display": "population origins or ancestry healthcare research"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "PRECLINTRCH",
"display": "preclinical trial research"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "SYSDEV",
"display": "system development"
},
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"version": "2018-08-12",
"code": "TRANSRCH",
"display": "translational healthcare research"
}
]
}
}