FHIR Release 3 (STU) R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.0.2: STU 3). (v3.3.0: R4 Ballot 2). 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: R4 R3

4.3.2.20471 HL7 v3 Value Set SecurityControlObservationValue

Vocabulary Work Group   Maturity Level : N/A External Use Context : Any

This value set (http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue) is defined as part of HL7 v3. Related FHIR content: SecurityControlObservationValue .

Summary

Defining URL: http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue
Name: SecurityControlObservationValue
Definition:

Security observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy,V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required to comply.

OID: 2.16.840.1.113883.1.11.20471 (for OID based terminology systems)
Source Resource XML / JSON

This value set is not currently used

4.3.2.20471.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.2.20471.2 Expansion

This expansion generated 19 03 Apr 2017 2018

This value set contains 91 111 concepts

Expansion based on http://hl7.org/fhir/v3/ActCode version 2016-11-11, 2018-04-01, http://hl7.org/fhir/ValueSet/v3-RefrainPolicy version 2014-03-26, http://hl7.org/fhir/ValueSet/v3-SecurityPolicy version 2014-03-26, http://hl7.org/fhir/v3/ActReason version 2016-11-11, 2018-04-01, http://hl7.org/fhir/ValueSet/v3-GeneralPurposeOfUse version 2014-03-26, http://hl7.org/fhir/ValueSet/v3-PurposeOfUse version 2014-03-26, http://hl7.org/fhir/ValueSet/v3-ObligationPolicy version 2014-03-26

Code System Display Definition
SecurityPolicy http://hl7.org/fhir/v3/ActCode security policy Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
AUTHPOL http://hl7.org/fhir/v3/ActCode authorization 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)
ACCESSCONSCHEME http://hl7.org/fhir/v3/ActCode access 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) >
DELEPOL http://hl7.org/fhir/v3/ActCode delegation 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)
ObligationPolicy http://hl7.org/fhir/v3/ActCode obligation policy Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.
ANONY http://hl7.org/fhir/v3/ActCode anonymize Custodian system must remove any information that could result in identifying the information subject.
AOD http://hl7.org/fhir/v3/ActCode accounting of disclosure Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested.
AUDIT http://hl7.org/fhir/v3/ActCode audit Custodian system must monitor systems to ensure that all users are authorized to operate on information objects.
AUDTR http://hl7.org/fhir/v3/ActCode audit trail Custodian system must monitor and maintain retrievable log for each user and operation on information.
CPLYCC http://hl7.org/fhir/v3/ActCode comply with confidentiality code Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.
CPLYCD http://hl7.org/fhir/v3/ActCode comply with consent directive Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
CPLYJPP http://hl7.org/fhir/v3/ActCode comply with jurisdictional privacy policy Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
CPLYOPP http://hl7.org/fhir/v3/ActCode comply with organizational privacy policy Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
CPLYOSP http://hl7.org/fhir/v3/ActCode comply with organizational security policy Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
CPLYPOL http://hl7.org/fhir/v3/ActCode comply with policy Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
DECLASSIFYLABEL http://hl7.org/fhir/v3/ActCode declassify security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
DEID http://hl7.org/fhir/v3/ActCode deidentify Custodian system must strip information of data that would allow the identification of the source of the information or the information subject.
DELAU http://hl7.org/fhir/v3/ActCode delete after use Custodian system must remove target information from access after use.
DOWNGRDLABEL http://hl7.org/fhir/v3/ActCode downgrade security label Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
DRIVLABEL http://hl7.org/fhir/v3/ActCode derive security label Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
ENCRYPT http://hl7.org/fhir/v3/ActCode encrypt Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.)
ENCRYPTR http://hl7.org/fhir/v3/ActCode encrypt at rest Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" "at rest" or in storage.
ENCRYPTT http://hl7.org/fhir/v3/ActCode encrypt in transit Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" "in transit" or being transported by any means.
ENCRYPTU http://hl7.org/fhir/v3/ActCode encrypt in use Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user.
HUAPRV http://hl7.org/fhir/v3/ActCode human approval Custodian system must require human review and approval for permission requested.
LABEL http://hl7.org/fhir/v3/ActCode assign security label Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes.
MASK http://hl7.org/fhir/v3/ActCode mask Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". "shared secret".
MINEC http://hl7.org/fhir/v3/ActCode minimum necessary Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs "needs to know" know" in order to perform permitted workflow or purpose of use.
PERSISTLABEL http://hl7.org/fhir/v3/ActCode persist security label Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding.
PRIVMARK http://hl7.org/fhir/v3/ActCode privacy mark Custodian must create and/or maintain human readable security label tags as required by policy. Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." security-label."
PSEUD http://hl7.org/fhir/v3/ActCode pseudonymize Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject.
REDACT http://hl7.org/fhir/v3/ActCode redact Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.
UPGRDLABEL http://hl7.org/fhir/v3/ActCode upgrade security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
RefrainPolicy http://hl7.org/fhir/v3/ActCode refrain policy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines "defines actions the subjects must refrain from performing". performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc.
NOAUTH http://hl7.org/fhir/v3/ActCode no disclosure without subject authorization Prohibition on disclosure without information subject's authorization.
NOCOLLECT http://hl7.org/fhir/v3/ActCode no collection Prohibition on collection or storage of the information.
NODSCLCD http://hl7.org/fhir/v3/ActCode no disclosure without consent directive Prohibition on disclosure without organizational approved patient restriction.
NODSCLCDS http://hl7.org/fhir/v3/ActCode no disclosure without information subject's consent directive Prohibition on disclosure without a consent directive from the information subject.
NOINTEGRATE http://hl7.org/fhir/v3/ActCode no integration Prohibition on Integration into other records.
NOLIST http://hl7.org/fhir/v3/ActCode no unlisted entity disclosure Prohibition on disclosure except to entities on specific access list.
NOMOU http://hl7.org/fhir/v3/ActCode no disclosure without MOU Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
NOORGPOL http://hl7.org/fhir/v3/ActCode no disclosure without organizational authorization Prohibition on disclosure without organizational authorization.
NOPAT http://hl7.org/fhir/v3/ActCode no disclosure to patient, family or caregivers without attending provider's authorization Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep "keep information from patient". patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone).
NOPERSISTP http://hl7.org/fhir/v3/ActCode no collection beyond purpose of use Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
NORDSCLCD http://hl7.org/fhir/v3/ActCode no redisclosure without consent directive Prohibition on redisclosure without patient consent directive.
NORDSCLCDS http://hl7.org/fhir/v3/ActCode no redisclosure without information subject's consent directive Prohibition on redisclosure without a consent directive from the information subject.
NORDSCLW http://hl7.org/fhir/v3/ActCode no disclosure without jurisdictional authorization Prohibition on disclosure without authorization under jurisdictional law.
NORELINK http://hl7.org/fhir/v3/ActCode no relinking Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked.
NOREUSE http://hl7.org/fhir/v3/ActCode no reuse beyond purpose of use Prohibition on use of the information beyond the purpose of use initially authorized.
NOVIP http://hl7.org/fhir/v3/ActCode no unauthorized VIP disclosure Prohibition on disclosure except to principals with access permission to specific VIP information.
ORCON http://hl7.org/fhir/v3/ActCode no disclosure without originator authorization Prohibition on disclosure except as permitted by the information originator.
PurposeOfUse http://hl7.org/fhir/v3/ActReason purpose of use Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes.
HMARKT http://hl7.org/fhir/v3/ActReason healthcare marketing To perform one or more operations on information for marketing services and products related to health care.
HOPERAT http://hl7.org/fhir/v3/ActReason healthcare operations To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care.
CAREMGT http://hl7.org/fhir/v3/ActReason care management To perform analytics, evaluation and other secondary uses of treatment and healthcare related information to manage the quality, efficacy, patient safety, population health, and cost effectiveness of healthcare delivery. 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: The concept of care management is narrower than the list of activities related to more general organizational objectives such as provider profiling, education of healthcare and non-healthcare professionals; insurance underwriting, premium rating, reinsurance; organizational legal, medical review, auditing, compliance and fraud and abuse detection; business planning, development, and restructuring; fund-raising; and customer service. Map: Maps to ISO 14265 Classification Term "Health service management and quality assurance" described as "To inform persons or processes responsible for determining the availability, quality, safety, equity and cost-effectiveness of health care services." There is a semantic gap in concepts. 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.
DONAT http://hl7.org/fhir/v3/ActReason donation To perform one or more operations on information used for cadaveric organ, eye or tissue donation.
FRAUD http://hl7.org/fhir/v3/ActReason fraud To perform one or more operations on information used for fraud detection and prevention processes.
GOV http://hl7.org/fhir/v3/ActReason government To perform one or more operations on information used within government processes.
HACCRED http://hl7.org/fhir/v3/ActReason health accreditation To perform one or more operations on information for conducting activities related to meeting accreditation criteria.
HCOMPL http://hl7.org/fhir/v3/ActReason health compliance To perform one or more operations on information used for conducting activities required to meet a mandate.
HDECD http://hl7.org/fhir/v3/ActReason decedent To perform one or more operations on information used for handling deceased patient matters.
HDIRECT http://hl7.org/fhir/v3/ActReason directory To perform one or more operation operations on information used to manage a patient directory. Examples: facility enterprise payer health information exchange patient directory
HDM http://hl7.org/fhir/v3/ActReason 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. 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.
HLEGAL http://hl7.org/fhir/v3/ActReason legal To perform one or more operations on information for conducting activities required by legal proceeding.
HOUTCOMS http://hl7.org/fhir/v3/ActReason health outcome measure To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions.
HPRGRP http://hl7.org/fhir/v3/ActReason health program reporting To perform one or more operations on information used for conducting activities to meet program accounting requirements.
HQUALIMP http://hl7.org/fhir/v3/ActReason health quality improvement To perform one or more operations on information used for conducting administrative activities to improve health care quality.
HSYSADMIN http://hl7.org/fhir/v3/ActReason health system administration To perform one or more operations on information to administer the electronic systems used for the delivery of health care.
LABELING http://hl7.org/fhir/v3/ActReason 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. 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.
METAMGT http://hl7.org/fhir/v3/ActReason 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.
MEMADMIN http://hl7.org/fhir/v3/ActReason member administration To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program.
MILCDM http://hl7.org/fhir/v3/ActReason military command To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law.
PATADMIN http://hl7.org/fhir/v3/ActReason patient administration To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient.
PATSFTY http://hl7.org/fhir/v3/ActReason patient safety To perform one or more operations on information in processes related to ensuring the safety of health care.
PERFMSR http://hl7.org/fhir/v3/ActReason performance measure To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions.
RECORDMGT http://hl7.org/fhir/v3/ActReason records management To perform one or more operations on information used within the health records management process.
SYSDEV http://hl7.org/fhir/v3/ActReason system development To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application.
HTEST http://hl7.org/fhir/v3/ActReason 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. 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.
TRAIN http://hl7.org/fhir/v3/ActReason training To perform one or more operations on information used in training and education.
HPAYMT http://hl7.org/fhir/v3/ActReason healthcare payment To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care.
CLMATTCH http://hl7.org/fhir/v3/ActReason claim attachment To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services.
COVAUTH http://hl7.org/fhir/v3/ActReason coverage authorization To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services.
COVERAGE http://hl7.org/fhir/v3/ActReason coverage under policy or program To perform one or more operations on information for conducting activities related to coverage under a program or policy.
ELIGDTRM http://hl7.org/fhir/v3/ActReason eligibility determination To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment.
ELIGVER http://hl7.org/fhir/v3/ActReason eligibility verification To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays.
ENROLLM http://hl7.org/fhir/v3/ActReason enrollment To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices.
MILDCRG http://hl7.org/fhir/v3/ActReason 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.
REMITADV http://hl7.org/fhir/v3/ActReason remittance advice To perform one or more operations on information about the amount remitted for a health care claim.
HRESCH http://hl7.org/fhir/v3/ActReason healthcare research To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data iincludes basic and applied research such as biomedical, population origin or ancestry, translational research, and disease, discipline, specialty specific healthcare research and clinical trial research.
BIORCH http://hl7.org/fhir/v3/ActReason 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.
CLINTRCH http://hl7.org/fhir/v3/ActReason clinical trial research To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge.
CLINTRCHNPC http://hl7.org/fhir/v3/ActReason 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.
CLINTRCHPC http://hl7.org/fhir/v3/ActReason 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.
PRECLINTRCH http://hl7.org/fhir/v3/ActReason 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.
DSRCH http://hl7.org/fhir/v3/ActReason 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.
POARCH http://hl7.org/fhir/v3/ActReason 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.
TRANSRCH http://hl7.org/fhir/v3/ActReason 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.
PATRQT http://hl7.org/fhir/v3/ActReason patient requested To perform one or more operations on information in response to a patient's request.
FAMRQT http://hl7.org/fhir/v3/ActReason family requested To perform one or more operations on information in response to a request by a family member authorized by the patient.
PWATRNY http://hl7.org/fhir/v3/ActReason power of attorney To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative.
SUPNWK http://hl7.org/fhir/v3/ActReason support network To perform one or more operations on information in response to a request by a person authorized by the patient.
PUBHLTH http://hl7.org/fhir/v3/ActReason public health To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions.
DISASTER http://hl7.org/fhir/v3/ActReason disaster To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone.
THREAT http://hl7.org/fhir/v3/ActReason threat To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence.
TREAT http://hl7.org/fhir/v3/ActReason treatment To perform one or more operations on information for provision of health care.
CLINTRL http://hl7.org/fhir/v3/ActReason clinical trial To perform health care as part of the clinical trial protocol.
CAREMGT COC http://hl7.org/fhir/v3/ActReason 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. 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 Management Uses" described as "To inform the subject of care in support of his or her own interests."
ETREAT http://hl7.org/fhir/v3/ActReason Emergency Treatment To perform one or more operations on information for provision of immediately needed health care coordination. for an emergent condition.
CLINTRL BTG http://hl7.org/fhir/v3/ActReason clinical trial 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. 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 part "To inform persons or processes responsible for providing health care services to the subject of care." The ISO description conflates both of the clinical trial protocol. 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.
ETREAT ERTREAT http://hl7.org/fhir/v3/ActReason Emergency Treatment emergency room treatment To perform one or more operations on information for provision of immediately needed health care for an emergent condition. 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.
POPHLTH http://hl7.org/fhir/v3/ActReason population health To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program.