FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r4.r3
Resource TypeValueSet
IdValueSet-R4-security-labels-for-R3.json
FHIR VersionR3
Sourcehttp://hl7.org/fhir/uv/xver-r4.r3/0.1.0/ValueSet-R4-security-labels-for-R3.html
URLhttp://hl7.org/fhir/uv/xver/ValueSet/R4-security-labels-for-R3
Version0.1.0
Statusactive
Date2026-03-17T21:02:03.8104715+00:00
NameR4SecurityLabelsForR3
TitleCross-version ValueSet R4.All Security Labels for use in FHIR STU3
Realmuv
Authorityhl7
DescriptionThis cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/security-labels|4.0.1 for use in FHIR STU3 that is appropriate for use but unavailable in `http://hl7.org/fhir/ValueSet/security-labels|3.0.2`.
PurposeThis value set is part of the cross-version definitions generated to enable use of the value set `http://hl7.org/fhir/ValueSet/security-labels|4.0.1` as defined in FHIR R4 in FHIR STU3. The source value set is bound to the following FHIR R4 elements: * `AuditEvent.entity.securityLabel` * `Consent.provision.securityLabel` * `DocumentReference.securityLabel` * `Meta.security` Note that there are 337 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 (207) than the target (170), so the source is broader than the target.

Resources that use this resource

StructureDefinition
hl7.fhir.uv.xver-r4.r3#0.1.0extension-Consent.provisionR4: Constraints to the base Consent.policyRule

Resources that this resource uses

CodeSystem
hl7.terminology#currentv3-ActCodeActCode
hl7.terminology#currentv3-ActReasonActReason

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet R4-security-labels-for-R3

This value set expansion contains 38 concepts.

SystemVersionCodeDisplayDefinition
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  ACCESSCONSCHEMEaccess control scheme

An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies.

                       Usage Note: Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service.

                    There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also.

                    An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these.  An access control scheme is a component of an access control mechanism or "service") along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a PDP). (Based on ISO/IEC 10181-3:1996)


                       Examples: 



                       Attribute Based Access Control (ABAC)
                       Discretionary Access Control (DAC)
                       History Based Access Control (HBAC)
                       Identity Based Access Control (IBAC)
                       Mandatory Access Control (MAC)
                       Organization Based Access Control (OrBAC)
                       Relationship Based Access Control (RelBac)
                       Responsibility Based Access Control (RespBAC)
                       Risk Adaptable Access Control (RAdAC)
                    >
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  ACOCOMPTaccountable care organization compartment

A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who coordinate care for reimbursement based on quality metrics for improving outcomes and lowering costs, and may be authorized to access the consumer's health information because of membership in that group.

                    Security Compartment Labels assigned to a consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a an accountable care workflow who is requesting access to that information
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  AUTHPOLauthorization policy

Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system.

                    A positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions.  (Based on PONDERS)
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  BHbehavioral health information sensitivity

Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  COGNcognitive disability information sensitivity

Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.

                    Examples may include dementia, traumatic brain injury, attention deficit, hearing and visual disability such as dyslexia and other disorders and related conditions which impair learning and self-sufficiency.  However, the cognitive disabilities to which this term may apply  versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  CTCOMPTcare team compartment

Care coordination across participants in a care plan requires sharing of a healthcare consumer's information specific to that workflow. A care team member should only have access to that information while participating in that workflow or for other authorized uses.

                    Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  DELEPOLdelegation policy

Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated.

                    Delegation policies are aimed at subjects delegating rights to servers or third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden.

                    A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of delegation policy, positive and negative. (Based on PONDERS)
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  DVDdevelopmental disability information sensitivity

Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.

                    A diverse group of chronic conditions that are due to mental or physical impairments impacting activities of daily living, self-care, language acuity, learning, mobility, independent living and economic self-sufficiency. Examples may include Down syndrome and  Autism spectrum. However, the developmental disabilities to which this term applies versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions.  Implementers should constrain to those diagnoses applicable in the domain in which this code is used.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  EMOTDISemotional disturbance information sensitivity

Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.

                    Typical used to characterize behavioral and mental health issues of adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  ETHUDalcohol use disorder information sensitivity

Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  FMCOMPTfinancial management compartment

Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows.

                    Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a financial management workflow who is requesting access to that information.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  LRCOMPTlegitimate relationship compartment

Providers and care givers who have an established relationship per criteria determined by policy are considered to have an established care provision relations with a healthcare consumer, and may be authorized to access the consumer's health information because of that relationship. Providers and care givers should only have access to that information while participating in legitimate relationship workflows or for other authorized uses.

                    Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  MHmental health information sensitivity

Policy for handling information related to psychological disorders, which is afforded heightened confidentiality. Mental health information may be deemed specifically sensitive and distinct from physical health, substance use disorders, and behavioral disabilities and disorders in some jurisdictions.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  MSTmilitary sexual trauma information sensitivity

Policy for handling information related to sexual assault or repeated, threatening sexual harassment that occurred while the patient was in the military, which is afforded heightened confidentiality.

                    Access control concerns for military sexual trauma is based on the patient being subject to control by a higher ranking military perpetrator and/or censure by others within the military unit.  Due to the relatively unfettered access to healthcare information by higher ranking military personnel and those who have command over the patient, there is a need to sequester this information outside of the typical controls on access to military health records.


                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  OPIOIDUDopioid use disorder information sensitivity

Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  PACOMPTpatient administration compartment

Patient administration members who have access to healthcare consumer information as part of a patient administration workflows.

                    Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a patient administration workflow who is requesting access to that information.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  PHYphysician requested information sensitivity

Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the provider, this may trigger alerts for follow up actions according to organizational policy or jurisdictional law.

                       Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a physician as sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.

                    Use cases in which this code could be used are, e.g.,  in systems that lack the ability to automatically detect sensitive information and must rely on manual tagging; a system that lacks an applicable sensitivity tag, or for ad hoc situations where criticality of the situation requires that the tagging be done immediately by the provider before coding or transcription of consult notes can be completed, e.g., upon detection of a patient with suicidal tendencies or potential for violence.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  PSYTHPNpsychotherapy note information sensitivity

Policy for handling psychotherapy note information, which is afforded heightened confidentiality.

                       Usage Note: In some jurisdiction, disclosure of psychotherapy notes requires patient consent.

                    If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  SPIspecially protected information sensitivity

Policy for handling information deemed specially protected by law or policy including substance abuse, substance use, psychiatric, mental health, behavioral health, and cognitive disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  SUDsubstance use disorder information sensitivity

Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality.

                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActCode2018-08-12  VIOviolence information sensitivity

Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person.

                    Access control concerns for information about mental or physical harm resulting from violence caused by an unrelated person may include manipulation of care givers or access to records that enable the perpetrator contact or locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. 


                       Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  BIORCHbiomedical 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-ActReason2018-08-12  BTGbreak 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.

                       Map: Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the  policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care."

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-ActReason2018-08-12  CLINTRCHNPCclinical 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-ActReason2018-08-12  CLINTRCHPCclinical 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-ActReason2018-08-12  COCcoordination 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.

                       Usage Note: Use when describing these functions: 1. Monitoring a person’s goals, needs, and preferences.   2. Acting as the communication link between two or more participants concerned with a person's health and wellness.  3. Organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person.  4. Ensuring safe, appropriate, non-duplicative, and effective integrated care.

                    The goal is to clearly differentiate this type of coordination of care from HIPAA Operations by specifying that these actions on information are undertaken in the provision of healthcare treatment.

                    For similar uses of this concept, see SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking, which differentiates concepts of care coordination and case management for the provision of treatment as specifically distinct from activities related to health care delivery management and the operations of organizational entities involved in the delivery of healthcare.


                       Map: Maps to ISO 14265 Classification Terms: "Support of care activities within the provider organisation for an individual subject of care" described as "To inform persons or processes enabling others to provide health care services to the subject of care."  "Subject of Care Uses" described as "To inform the subject of care in support of his or her own interests."
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  DSRCHdisease 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-ActReason2018-08-12  ERTREATemergency 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.

                    Map:Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the  policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care."

                    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. 

                    There is a semantic gap in concepts.  This classification term is described as activities “to inform persons� rather than the rationale for performing actions/operations on information related to the activity.
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  HDMhealthcare 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.

                       Usage Note: Examples of activities conducted under this purpose of use: provider profiling, risk adjustment, underwriting, fraud and abuse, quality improvement population health and care management. Aligns with HIPAA Operation POU minus coordination of care or other treatment related activities. Similar to the description in SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking.


                       Map: Maps to ISO 14265 Classification Term  "Administration of care for an individual subject of care" described as "To inform persons or processes responsible for enabling the availability of resources or funding or permissions for providing health care services to the subject of care."

                    However, this classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity.
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  HTESTtest 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.

                       Usage Note: Data marked with a HTEST security label enables an access control system to permit interfacing systems or end users provisioned with a clearance, which includes a HTEST purpose of use attribute, to test, verify, or validate that a system or application will operate in production as intended based on design specifications.
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  LABELINGlabeling

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.

                    Label management includes classification of target data by constructing and binding of a label set per applicable policies, security policy information file semantics, and classification guides.  Label management also includes process and procedures for subsequent revision of a label for, e.g., reclassification, downgrading classification, and declassification.

                    Label revisions may be triggered by, e.g., expiry of classification period; changes in applicable policy, e.g., revocation of a consent directive; or changes in the governing policy domain in which the data is relocated or a copy of the data is sent.  If a label is revised, an audit log should be kept and the provenance of the label changes should be tracked.
http://terminology.hl7.org/CodeSystem/v3-ActReason2018-08-12  METAMGTmetadata 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-ActReason2018-08-12  MILCDMmilitary 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-ActReason2018-08-12  MILDCRGmilitary 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-ActReason2018-08-12  POARCHpopulation 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-ActReason2018-08-12  PRECLINTRCHpreclinical 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-ActReason2018-08-12  SYSDEVsystem 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-ActReason2018-08-12  TRANSRCHtranslational 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.


Source1

{
  "resourceType": "ValueSet",
  "id": "R4-security-labels-for-R3",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 5
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "vocab"
    },
    {
      "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-security-labels-for-R3",
  "version": "0.1.0",
  "name": "R4SecurityLabelsForR3",
  "title": "Cross-version ValueSet R4.All Security Labels for use in FHIR STU3",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T21:02:03.8104715+00:00",
  "publisher": "HL7 International / Terminology Infrastructure",
  "contact": [
    {
      "name": "HL7 International / Terminology Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/Vocab"
        }
      ]
    }
  ],
  "description": "This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/security-labels|4.0.1 for use in FHIR STU3 that is appropriate for use but unavailable in `http://hl7.org/fhir/ValueSet/security-labels|3.0.2`.",
  "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://hl7.org/fhir/ValueSet/security-labels|4.0.1` 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.entity.securityLabel`\n* `Consent.provision.securityLabel`\n* `DocumentReference.securityLabel`\n* `Meta.security`\r\n\r\nNote that there are 337 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 (207) than the target (170), so the source is broader than the target.",
  "compose": {
    "include": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "concept": [
          {
            "code": "ACCESSCONSCHEME",
            "display": "access control scheme"
          },
          {
            "code": "ACOCOMPT",
            "display": "accountable care organization compartment"
          },
          {
            "code": "AUTHPOL",
            "display": "authorization policy"
          },
          {
            "code": "BH",
            "display": "behavioral health information sensitivity"
          },
          {
            "code": "COGN",
            "display": "cognitive disability information sensitivity"
          },
          {
            "code": "CTCOMPT",
            "display": "care team compartment"
          },
          {
            "code": "DELEPOL",
            "display": "delegation policy"
          },
          {
            "code": "DVD",
            "display": "developmental disability information sensitivity"
          },
          {
            "code": "EMOTDIS",
            "display": "emotional disturbance information sensitivity"
          },
          {
            "code": "ETHUD",
            "display": "alcohol use disorder information sensitivity"
          },
          {
            "code": "FMCOMPT",
            "display": "financial management compartment"
          },
          {
            "code": "LRCOMPT",
            "display": "legitimate relationship compartment"
          },
          {
            "code": "MH",
            "display": "mental health information sensitivity"
          },
          {
            "code": "MST",
            "display": "military sexual trauma information sensitivity"
          },
          {
            "code": "OPIOIDUD",
            "display": "opioid use disorder information sensitivity"
          },
          {
            "code": "PACOMPT",
            "display": "patient administration compartment"
          },
          {
            "code": "PHY",
            "display": "physician requested information sensitivity"
          },
          {
            "code": "PSYTHPN",
            "display": "psychotherapy note information sensitivity"
          },
          {
            "code": "SPI",
            "display": "specially protected information sensitivity"
          },
          {
            "code": "SUD",
            "display": "substance use disorder information sensitivity"
          },
          {
            "code": "VIO",
            "display": "violence information sensitivity"
          }
        ]
      },
      {
        "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-ActCode",
        "version": "2018-08-12",
        "code": "ACCESSCONSCHEME",
        "display": "access control scheme"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "ACOCOMPT",
        "display": "accountable care organization compartment"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "AUTHPOL",
        "display": "authorization policy"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "BH",
        "display": "behavioral health information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "COGN",
        "display": "cognitive disability information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "CTCOMPT",
        "display": "care team compartment"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "DELEPOL",
        "display": "delegation policy"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "DVD",
        "display": "developmental disability information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "EMOTDIS",
        "display": "emotional disturbance information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "ETHUD",
        "display": "alcohol use disorder information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "FMCOMPT",
        "display": "financial management compartment"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "LRCOMPT",
        "display": "legitimate relationship compartment"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "MH",
        "display": "mental health information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "MST",
        "display": "military sexual trauma information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "OPIOIDUD",
        "display": "opioid use disorder information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "PACOMPT",
        "display": "patient administration compartment"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "PHY",
        "display": "physician requested information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "PSYTHPN",
        "display": "psychotherapy note information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "SPI",
        "display": "specially protected information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "SUD",
        "display": "substance use disorder information sensitivity"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "2018-08-12",
        "code": "VIO",
        "display": "violence information sensitivity"
      },
      {
        "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"
      }
    ]
  }
}