Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B - Downloaded Version null See the Directory of published versions

ValueSet: R2V3SecurityControlObservationValueForR4B

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R2-v3-SecurityControlObservationValue-for-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2V3SecurityControlObservationValueForR4B

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26 for use in FHIR R4B.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26 as defined in FHIR DSTU2 in FHIR R4B.

The source value set is bound to the following FHIR DSTU2 elements:

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26
  • http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26
  • http://terminology.hl7.org/ValueSet/v3-SecurityControlObservationValue|2014-03-26

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments: All concepts in the comparison are listed as identical. The source value set has fewer active concepts (85) than the target (91), so the source is narrower than the target. All concepts in the comparison are have code literals listed as identical. The source value set has fewer active concepts (91) than the target (111), so the source is narrower than the target. FHIR ValueSet http://hl7.org/fhir/ValueSet/v3-SecurityControlObservationValue|2014-03-26, defined in FHIR DSTU2 does not have any mapping to FHIR R4B

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://hl7.org/fhir/v3/ActCode version 📍1.0.2
    CodeDisplayDefinition
    ANONYanonymizeCustodian system must remove any information that could result in identifying the information subject.
    AODaccounting of disclosureCustodian 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.
    AUDITauditCustodian system must monitor systems to ensure that all users are authorized to operate on information objects.
    AUDTRaudit trailCustodian system must monitor and maintain retrievable log for each user and operation on information.
    CPLYCCcomply with confidentiality codeCustodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.
    CPLYCDcomply with consent directiveCustodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
    CPLYJPPcomply with jurisdictional privacy policyCustodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
    CPLYOPPcomply with organizational privacy policyCustodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
    CPLYOSPcomply with organizational security policyCustodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
    CPLYPOLcomply with policyCustodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
    DEIDdeidentifyCustodian system must strip information of data that would allow the identification of the source of the information or the information subject.
    DELAUdelete after useCustodian system must remove target information from access after use.
    ENCRYPTencryptCustodian 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.)
    ENCRYPTRencrypt at restCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
    ENCRYPTTencrypt in transitCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.
    ENCRYPTUencrypt in useCustodian 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.
    HUAPRVhuman approvalCustodian system must require human review and approval for permission requested.
    MASKmaskCustodian 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".
    MINECminimum necessaryCustodian 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 to know" in order to perform permitted workflow or purpose of use.
    NOAUTHno disclosure without subject authorizationProhibition on disclosure without information subject's authorization.
    NOCOLLECTno collectionProhibition on collection or storage of the information.
    NODSCLCDno disclosure without consent directiveProhibition on disclosure without organizational approved patient restriction.
    NODSCLCDSno disclosure without information subject's consent directiveProhibition on disclosure without a consent directive from the information subject.
    NOINTEGRATEno integrationProhibition on Integration into other records.
    NOLISTno unlisted entity disclosureProhibition on disclosure except to entities on specific access list.
    NOMOUno disclosure without MOUProhibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
    NOORGPOLno disclosure without organizational authorizationProhibition on disclosure without organizational authorization.
    NOPATno disclosure to patient, family or caregivers without attending provider's authorizationProhibition 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 information from 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).
    NOPERSISTPno collection beyond purpose of useProhibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
    NORDSCLCDno redisclosure without consent directiveProhibition on redisclosure without patient consent directive.
    NORDSCLCDSno redisclosure without information subject's consent directiveProhibition on redisclosure without a consent directive from the information subject.
    NORDSCLWno disclosure without jurisdictional authorizationProhibition on disclosure without authorization under jurisdictional law.
    NORELINKno relinkingProhibition 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.
    NOREUSEno reuse beyond purpose of useProhibition on use of the information beyond the purpose of use initially authorized.
    NOVIPno unauthorized VIP disclosureProhibition on disclosure except to principals with access permission to specific VIP information.
    ORCONno disclosure without originator authorizationProhibition on disclosure except as permitted by the information originator.
    ObligationPolicyobligation policyConveys 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.
    PRIVMARKprivacy markCustodian 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 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."
    PSEUDpseudonymizeCustodian 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.
    REDACTredactCustodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.
    RefrainPolicyrefrain policyConveys 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 actions the subjects must refrain from 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.
    SecurityPolicysecurity policyTypes of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
  • Include these codes as defined in http://hl7.org/fhir/v3/ActReason version 📍1.0.2
    CodeDisplayDefinition
    CAREMGT Care Management To perform one or more operations on information for provision of health care coordination.
    CLINTRCH 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.
    CLINTRL clinical trial To perform health care as part of the clinical trial protocol.
    CLMATTCH 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 coverage authorization To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services.
    COVERAGE coverage under policy or program To perform one or more operations on information for conducting activities related to coverage under a program or policy.
    DISASTER 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.
    DONAT donation To perform one or more operations on information used for cadaveric organ, eye or tissue donation.
    ELIGDTRM 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 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 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.
    ETREAT Emergency Treatment To perform one or more operations on information for provision of immediately needed health care for an emergent condition.
    FAMRQT family requested To perform one or more operations on information in response to a request by a family member authorized by the patient.
    FRAUD fraud To perform one or more operations on information used for fraud detection and prevention processes.
    GOV government To perform one or more operations on information used within government processes.
    HACCRED health accreditation To perform one or more operations on information for conducting activities related to meeting accreditation criteria.
    HCOMPL health compliance To perform one or more operations on information used for conducting activities required to meet a mandate.
    HDECD decedent To perform one or more operations on information used for handling deceased patient matters.
    HDIRECT 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
    HLEGAL legal To perform one or more operations on information for conducting activities required by legal proceeding.
    HMARKT healthcare marketing To perform one or more operations on information for marketing services and products related to health care.
    HOPERAT healthcare operations To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care.
    HOUTCOMS 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.
    HPAYMT healthcare payment To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care.
    HPRGRP health program reporting To perform one or more operations on information used for conducting activities to meet program accounting requirements.
    HQUALIMP health quality improvement To perform one or more operations on information used for conducting administrative activities to improve health care quality.
    HRESCH healthcare research To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge.
    HSYSADMIN health system administration To perform one or more operations on information to administer the electronic systems used for the delivery of health care.
    MEMADMIN member administration To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program.
    PATADMIN 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.
    PATRQT patient requested To perform one or more operations on information in response to a patient's request.
    PATSFTY patient safety To perform one or more operations on information in processes related to ensuring the safety of health care.
    PERFMSR performance measure To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions.
    POPHLTH 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.
    PUBHLTH public health To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions.
    PWATRNY 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.
    PurposeOfUse 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.
    RECORDMGT records management To perform one or more operations on information used within the health records management process.
    REMITADV remittance advice To perform one or more operations on information about the amount remitted for a health care claim.
    SUPNWK support network To perform one or more operations on information in response to a request by a person authorized by the patient.
    THREAT 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.
    TRAIN training To perform one or more operations on information used in training and education.
    TREAT treatment To perform one or more operations on information for provision of health care.

 

Expansion

This value set expansion contains 85 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/ActCode1.0.2  ANONYanonymizeCustodian system must remove any information that could result in identifying the information subject.
http://hl7.org/fhir/v3/ActCode1.0.2  AODaccounting of disclosureCustodian 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.
http://hl7.org/fhir/v3/ActCode1.0.2  AUDITauditCustodian system must monitor systems to ensure that all users are authorized to operate on information objects.
http://hl7.org/fhir/v3/ActCode1.0.2  AUDTRaudit trailCustodian system must monitor and maintain retrievable log for each user and operation on information.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYCCcomply with confidentiality codeCustodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYCDcomply with consent directiveCustodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYJPPcomply with jurisdictional privacy policyCustodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYOPPcomply with organizational privacy policyCustodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYOSPcomply with organizational security policyCustodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
http://hl7.org/fhir/v3/ActCode1.0.2  CPLYPOLcomply with policyCustodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
http://hl7.org/fhir/v3/ActCode1.0.2  DEIDdeidentifyCustodian system must strip information of data that would allow the identification of the source of the information or the information subject.
http://hl7.org/fhir/v3/ActCode1.0.2  DELAUdelete after useCustodian system must remove target information from access after use.
http://hl7.org/fhir/v3/ActCode1.0.2  ENCRYPTencryptCustodian 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.)
http://hl7.org/fhir/v3/ActCode1.0.2  ENCRYPTRencrypt at restCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
http://hl7.org/fhir/v3/ActCode1.0.2  ENCRYPTTencrypt in transitCustodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.
http://hl7.org/fhir/v3/ActCode1.0.2  ENCRYPTUencrypt in useCustodian 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.
http://hl7.org/fhir/v3/ActCode1.0.2  HUAPRVhuman approvalCustodian system must require human review and approval for permission requested.
http://hl7.org/fhir/v3/ActCode1.0.2  MASKmaskCustodian 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".
http://hl7.org/fhir/v3/ActCode1.0.2  MINECminimum necessaryCustodian 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 to know" in order to perform permitted workflow or purpose of use.
http://hl7.org/fhir/v3/ActCode1.0.2  NOAUTHno disclosure without subject authorizationProhibition on disclosure without information subject's authorization.
http://hl7.org/fhir/v3/ActCode1.0.2  NOCOLLECTno collectionProhibition on collection or storage of the information.
http://hl7.org/fhir/v3/ActCode1.0.2  NODSCLCDno disclosure without consent directiveProhibition on disclosure without organizational approved patient restriction.
http://hl7.org/fhir/v3/ActCode1.0.2  NODSCLCDSno disclosure without information subject's consent directiveProhibition on disclosure without a consent directive from the information subject.
http://hl7.org/fhir/v3/ActCode1.0.2  NOINTEGRATEno integrationProhibition on Integration into other records.
http://hl7.org/fhir/v3/ActCode1.0.2  NOLISTno unlisted entity disclosureProhibition on disclosure except to entities on specific access list.
http://hl7.org/fhir/v3/ActCode1.0.2  NOMOUno disclosure without MOUProhibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
http://hl7.org/fhir/v3/ActCode1.0.2  NOORGPOLno disclosure without organizational authorizationProhibition on disclosure without organizational authorization.
http://hl7.org/fhir/v3/ActCode1.0.2  NOPATno disclosure to patient, family or caregivers without attending provider's authorizationProhibition 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 information from 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).
http://hl7.org/fhir/v3/ActCode1.0.2  NOPERSISTPno collection beyond purpose of useProhibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
http://hl7.org/fhir/v3/ActCode1.0.2  NORDSCLCDno redisclosure without consent directiveProhibition on redisclosure without patient consent directive.
http://hl7.org/fhir/v3/ActCode1.0.2  NORDSCLCDSno redisclosure without information subject's consent directiveProhibition on redisclosure without a consent directive from the information subject.
http://hl7.org/fhir/v3/ActCode1.0.2  NORDSCLWno disclosure without jurisdictional authorizationProhibition on disclosure without authorization under jurisdictional law.
http://hl7.org/fhir/v3/ActCode1.0.2  NORELINKno relinkingProhibition 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.
http://hl7.org/fhir/v3/ActCode1.0.2  NOREUSEno reuse beyond purpose of useProhibition on use of the information beyond the purpose of use initially authorized.
http://hl7.org/fhir/v3/ActCode1.0.2  NOVIPno unauthorized VIP disclosureProhibition on disclosure except to principals with access permission to specific VIP information.
http://hl7.org/fhir/v3/ActCode1.0.2  ORCONno disclosure without originator authorizationProhibition on disclosure except as permitted by the information originator.
http://hl7.org/fhir/v3/ActCode1.0.2  ObligationPolicyobligation policyConveys 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.
http://hl7.org/fhir/v3/ActCode1.0.2  PRIVMARKprivacy markCustodian 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 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."
http://hl7.org/fhir/v3/ActCode1.0.2  PSEUDpseudonymizeCustodian 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.
http://hl7.org/fhir/v3/ActCode1.0.2  REDACTredactCustodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.
http://hl7.org/fhir/v3/ActCode1.0.2  RefrainPolicyrefrain policyConveys 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 actions the subjects must refrain from 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.
http://hl7.org/fhir/v3/ActCode1.0.2  SecurityPolicysecurity policyTypes of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
http://hl7.org/fhir/v3/ActReason1.0.2  CAREMGTCare ManagementTo perform one or more operations on information for provision of health care coordination.
http://hl7.org/fhir/v3/ActReason1.0.2  CLINTRCHclinical trial researchTo perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge.
http://hl7.org/fhir/v3/ActReason1.0.2  CLINTRLclinical trialTo perform health care as part of the clinical trial protocol.
http://hl7.org/fhir/v3/ActReason1.0.2  CLMATTCHclaim attachmentTo 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.
http://hl7.org/fhir/v3/ActReason1.0.2  COVAUTHcoverage authorizationTo perform one or more operations on information for conducting prior authorization or predetermination of coverage for services.
http://hl7.org/fhir/v3/ActReason1.0.2  COVERAGEcoverage under policy or programTo perform one or more operations on information for conducting activities related to coverage under a program or policy.
http://hl7.org/fhir/v3/ActReason1.0.2  DISASTERdisasterTo 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.
http://hl7.org/fhir/v3/ActReason1.0.2  DONATdonationTo perform one or more operations on information used for cadaveric organ, eye or tissue donation.
http://hl7.org/fhir/v3/ActReason1.0.2  ELIGDTRMeligibility determinationTo 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.
http://hl7.org/fhir/v3/ActReason1.0.2  ELIGVEReligibility verificationTo 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.
http://hl7.org/fhir/v3/ActReason1.0.2  ENROLLMenrollmentTo 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.
http://hl7.org/fhir/v3/ActReason1.0.2  ETREATEmergency TreatmentTo perform one or more operations on information for provision of immediately needed health care for an emergent condition.
http://hl7.org/fhir/v3/ActReason1.0.2  FAMRQTfamily requestedTo perform one or more operations on information in response to a request by a family member authorized by the patient.
http://hl7.org/fhir/v3/ActReason1.0.2  FRAUDfraudTo perform one or more operations on information used for fraud detection and prevention processes.
http://hl7.org/fhir/v3/ActReason1.0.2  GOVgovernmentTo perform one or more operations on information used within government processes.
http://hl7.org/fhir/v3/ActReason1.0.2  HACCREDhealth accreditationTo perform one or more operations on information for conducting activities related to meeting accreditation criteria.
http://hl7.org/fhir/v3/ActReason1.0.2  HCOMPLhealth complianceTo perform one or more operations on information used for conducting activities required to meet a mandate.
http://hl7.org/fhir/v3/ActReason1.0.2  HDECDdecedentTo perform one or more operations on information used for handling deceased patient matters.
http://hl7.org/fhir/v3/ActReason1.0.2  HDIRECTdirectoryTo perform one or more operation operations on information used to manage a patient directory. Examples: facility enterprise payer health information exchange patient directory
http://hl7.org/fhir/v3/ActReason1.0.2  HLEGALlegalTo perform one or more operations on information for conducting activities required by legal proceeding.
http://hl7.org/fhir/v3/ActReason1.0.2  HMARKThealthcare marketingTo perform one or more operations on information for marketing services and products related to health care.
http://hl7.org/fhir/v3/ActReason1.0.2  HOPERAThealthcare operationsTo perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care.
http://hl7.org/fhir/v3/ActReason1.0.2  HOUTCOMShealth outcome measureTo perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions.
http://hl7.org/fhir/v3/ActReason1.0.2  HPAYMThealthcare paymentTo perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care.
http://hl7.org/fhir/v3/ActReason1.0.2  HPRGRPhealth program reportingTo perform one or more operations on information used for conducting activities to meet program accounting requirements.
http://hl7.org/fhir/v3/ActReason1.0.2  HQUALIMPhealth quality improvementTo perform one or more operations on information used for conducting administrative activities to improve health care quality.
http://hl7.org/fhir/v3/ActReason1.0.2  HRESCHhealthcare researchTo perform one or more operations on information for conducting scientific investigations to obtain health care knowledge.
http://hl7.org/fhir/v3/ActReason1.0.2  HSYSADMINhealth system administrationTo perform one or more operations on information to administer the electronic systems used for the delivery of health care.
http://hl7.org/fhir/v3/ActReason1.0.2  MEMADMINmember administrationTo perform one or more operations on information to administer health care coverage to an enrollee under a policy or program.
http://hl7.org/fhir/v3/ActReason1.0.2  PATADMINpatient administrationTo perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient.
http://hl7.org/fhir/v3/ActReason1.0.2  PATRQTpatient requestedTo perform one or more operations on information in response to a patient's request.
http://hl7.org/fhir/v3/ActReason1.0.2  PATSFTYpatient safetyTo perform one or more operations on information in processes related to ensuring the safety of health care.
http://hl7.org/fhir/v3/ActReason1.0.2  PERFMSRperformance measureTo perform one or more operations on information used for monitoring performance of recommended health care practices and interventions.
http://hl7.org/fhir/v3/ActReason1.0.2  POPHLTHpopulation healthTo perform one or more operations on information for provision of health care to a population of living subjects, e.g. needle exchange program.
http://hl7.org/fhir/v3/ActReason1.0.2  PUBHLTHpublic healthTo perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions.
http://hl7.org/fhir/v3/ActReason1.0.2  PWATRNYpower of attorneyTo perform one or more operations on information in response to a request by a person appointed as the patient's legal representative.
http://hl7.org/fhir/v3/ActReason1.0.2  PurposeOfUsepurpose of useReason 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.
http://hl7.org/fhir/v3/ActReason1.0.2  RECORDMGTrecords managementTo perform one or more operations on information used within the health records management process.
http://hl7.org/fhir/v3/ActReason1.0.2  REMITADVremittance adviceTo perform one or more operations on information about the amount remitted for a health care claim.
http://hl7.org/fhir/v3/ActReason1.0.2  SUPNWKsupport networkTo perform one or more operations on information in response to a request by a person authorized by the patient.
http://hl7.org/fhir/v3/ActReason1.0.2  THREATthreatTo perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence.
http://hl7.org/fhir/v3/ActReason1.0.2  TRAINtrainingTo perform one or more operations on information used in training and education.
http://hl7.org/fhir/v3/ActReason1.0.2  TREATtreatmentTo perform one or more operations on information for provision of health care.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code