HL7 Terminology (THO)
5.1.0 - Publication International flag

This page is part of the HL7 Terminology (v5.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: v3 Code System ActReason

Official URL: http://terminology.hl7.org/ValueSet/v3-ActReason Version: 2.0.0
Active as of 2018-08-12 Maturity Level: 1 Responsible: HL7, Inc Computable Name: ActReason

A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type “has reason” linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: “routine requirement”, “infectious disease reporting requirement”, “on patient request”, “required by law”.

References

Logical Definition (CLD)

 

Expansion

This value set contains 248 concepts

Expansion based on ActReason v2.1.0 (CodeSystem)

CodeSystemDisplayDefinition
  _ActAccommodationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActAccommodationReason

Identifies the reason the patient is assigned to this accommodation type

  ACCREQNAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonAccommodation Requested Not Available

Accommodation requested is not available.

  FLRCNVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonFloor Convenience

Accommodation is assigned for floor convenience.

  MEDNEChttp://terminology.hl7.org/CodeSystem/v3-ActReasonMedical Necessity

Required for medical reasons(s).

  PAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonPatient request

The Patient requested the action

  _ActCoverageReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActCoverageReason

**Description:**Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties.

  _EligibilityActReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonEligibilityActReasonCode

Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam.

Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status.

  _ActIneligibilityReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActIneligibilityReason

Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy.

Examples are client deceased & adopted client has been given a new policy identifier.

  COVSUShttp://terminology.hl7.org/CodeSystem/v3-ActReasoncoverage suspended

When a client has no contact with the health system for an extended period, coverage is suspended. Client will be reinstated to original start date upon proof of identification, residency etc.

Example: Coverage may be suspended during a strike situation, when employer benefits for employees are not covered (i.e. not in effect).

  DECSDhttp://terminology.hl7.org/CodeSystem/v3-ActReasondeceased

Client deceased.

  REGERRhttp://terminology.hl7.org/CodeSystem/v3-ActReasonregistered in error

Client was registered in error.

  _CoverageEligibilityReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonCoverageEligibilityReason

Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam.

Examples: A person is a claimant under an automobile insurance policy are client deceased & adopted client has been given a new policy identifier. A new employee is eligible for health insurance as an employment benefit. A person meets a government program eligibility criteria for financial, age or health status.

  AGEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonage eligibility

A person becomes eligible for a program based on age.

Example: In the U.S., a person who is 65 years of age or older is eligible for Medicare.

  CRIMEhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncrime victim

A person becomes eligible for insurance or a program because of crime related health condition or injury.

Example: A person is a claimant under the U.S. Crime Victims Compensation program.

  DIShttp://terminology.hl7.org/CodeSystem/v3-ActReasondisability

A person becomes a claimant under a disability income insurance policy or a disability rehabilitation program because of a health condition or injury which limits the person's ability to earn an income or function without institutionalization.

  EMPLOYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonemployment benefit

A person becomes eligible for insurance provided as an employment benefit based on employment status.

  FINANhttp://terminology.hl7.org/CodeSystem/v3-ActReasonfinancial eligibility

A person becomes eligible for a program based on financial criteria.

Example: A person whose family income is below a financial threshold for eligibility for Medicaid or SCHIP.

  HEALTHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth status

A person becomes eligible for a program because of a qualifying health condition or injury.

Examples: A person is determined to have a qualifying health conditions include pregnancy, HIV/AIDs, tuberculosis, end stage renal disease, breast or cervical cancer, or other condition requiring specialized health services, hospice, institutional or community based care provided under a program

  MULTIhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmultiple criteria eligibility

A person becomes eligible for a program based on more than one criterion.

Examples: In the U.S., a child whose familiy income meets Medicaid financial thresholds and whose age is less than 18 is eligible for the Early and Periodic Screening, Diagnostic, and Treatment program (EPSDT). A person whose family income meets Medicaid financial thresholds and whose age is 65 years or older is eligible for Medicaid and Medicare, and are referred to as dual eligibles.

  PNChttp://terminology.hl7.org/CodeSystem/v3-ActReasonproperty and casualty condition

A person becomes a claimant under a property and casualty insurance policy because of a related health condition or injury resulting from a circumstance covered under the terms of the policy.

Example: A person is a claimant under a homeowners insurance policy because of an injury sustained on the policyholderaTMs premises.

  STATUTORYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonstatutory eligibility

A person becomes eligible for a program based on statutory criteria.

Examples: A person is a member of an indigenous group, a veteran of military service, or in the U.S., a recipient of adoption assistance and foster care under Title IV-E of the Social Security.

  VEHIChttp://terminology.hl7.org/CodeSystem/v3-ActReasonmotor vehicle accident victim

A person becomes a claimant under a motor vehicle accident insurance because of a motor vehicle accident related health condition or injury.

  WORKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonwork related

A person becomes eligible for insurance or a program because of a work related health condition or injury.

Example: A person is a claimant under the U.S. Black Lung Program.

  _ActCoverageProviderReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActCoverageProviderReason

**Description:**Identifies the reason or rationale for coverage of a service or product based on characteristics of the provider, e.g., contractual relationship to payor, such as in or out-of-network; relationship of the covered party to the provider.

**Example:**In closed managed care plan, a covered party is assigned a primary care provider who provides primary care services and authorizes referrals and ancillary and non-primary care services.

  _ActCoverageServiceReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActCoverageServiceReason

**Description:**Identifies the reason or rationale for coverage of a service or product based on clinical efficacy criteria or practices prescribed by the payor.

  _CoverageExclusionReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonCoverageExclusionReason

Definition: Identifies the reason or rationale for coverage of a service or product based on coverage exclusions related to the risk of adverse selection by covered parties.

  _CoverageFinancialParticipationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonCoverageFinancialParticipationReason

**Description:**Identifies the reason or rationale for coverage of a service or product based on financial participation responsibilities of the covered party.

  _CoverageLimitationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonCoverageLimitationReason

**Description:**Identifies the reason or rationale for limitations on the coverage of a service or product based on coverage contract provisions.

**Example:**The maximum cost per unit; or the maximum number of units per period, which is typically the policy or program effective time.

  _ActInformationManagementReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActInformationManagementReason

**Description:**The rationale or purpose for an act relating to information management, such as archiving information for the purpose of complying with an enterprise data retention policy.

  _ActHealthInformationManagementReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActHealthInformationManagementReason

**Description:**The rationale or purpose for an act relating to health information management, such as archiving information for the purpose of complying with an organization policy or jurisdictional law relating to data retention.

  _ActConsentInformationAccessOverrideReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActConsentInformationAccessOverrideReason

To perform one or more operations on information to which the patient has not consented as deemed necessary by authorized entities for providing care in the best interest of the patient; providing immediately needed health care for an emergent condition; or for protecting public or third party safety.

Usage Notes: Used to convey the reason that a provider or other entity may or has accessed personal healthcare information. Typically, this involves overriding the subject's consent directives.

  OVRERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonemergency treatment override

To perform one or more operations on information to which the patient has not consented by authorized entities for treating a condition which poses an immediate threat to the patient's health and which requires immediate medical intervention.

Usage Notes: The patient is unable to provide consent, but the provider determines they have an urgent healthcare related reason to access the record.

  OVRINCOMPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonincompetency override

To perform one or more operations on information to which the patient has not consented because deemed incompetent to provide consent.

Usage Note: Maps to v2 CON-16 Subject Competence Indicator (ID) 01791 Definition: Identifies whether the subject was deemed competent to provide consent. Refer to table HL7 Table 0136 - Yes/No Indicator and CON-23 Non-Subject Consenter Reason User-defined Table 0502 - Non-Subject Consenter Reason code NC "Subject is not competent to consent".

  OVRPJhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprofessional judgment override

To perform one or more operations on information to which the patient declined to consent for providing health care.

Usage Notes: The patient, while able to give consent, has not. However the provider believes it is in the patient's interest to access the record without patient consent.

  OVRPShttp://terminology.hl7.org/CodeSystem/v3-ActReasonpublic safety override

To perform one or more operations on information to which the patient has not consented for public safety reasons.

Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to public safety.

  OVRTPShttp://terminology.hl7.org/CodeSystem/v3-ActReasonthird party safety override

To perform one or more operations on information to which the patient has not consented for third party safety.

Usage Notes: The patient, while able to give consent, has not. However, the provider believes that access to masked patient information is justified because of concerns related to the health and safety of one or more third parties.

  PurposeOfUsehttp://terminology.hl7.org/CodeSystem/v3-ActReasonpurpose 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.

  HMARKThttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealthcare marketing

To perform one or more operations on information for marketing services and products related to health care.

  HOPERAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealthcare operations

To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care.

  CAREMGThttp://terminology.hl7.org/CodeSystem/v3-ActReasoncare 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.

  DONAThttp://terminology.hl7.org/CodeSystem/v3-ActReasondonation

To perform one or more operations on information used for cadaveric organ, eye or tissue donation.

  FRAUDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonfraud

To perform one or more operations on information used for fraud detection and prevention processes.

  GOVhttp://terminology.hl7.org/CodeSystem/v3-ActReasongovernment

To perform one or more operations on information used within government processes.

  HACCREDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth accreditation

To perform one or more operations on information for conducting activities related to meeting accreditation criteria.

  HCOMPLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth compliance

To perform one or more operations on information used for conducting activities required to meet a mandate.

  HDECDhttp://terminology.hl7.org/CodeSystem/v3-ActReasondecedent

To perform one or more operations on information used for handling deceased patient matters.

  HDIRECThttp://terminology.hl7.org/CodeSystem/v3-ActReasondirectory

To perform one or more operation operations on information used to manage a patient directory.

Examples:

  • facility
  • enterprise
  • payer
  • health information exchange patient directory
  HDMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealthcare 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.

  HLEGALhttp://terminology.hl7.org/CodeSystem/v3-ActReasonlegal

To perform one or more operations on information for conducting activities required by legal proceeding.

  HOUTCOMShttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth outcome measure

To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions.

  HPRGRPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth program reporting

To perform one or more operations on information used for conducting activities to meet program accounting requirements.

  HQUALIMPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth quality improvement

To perform one or more operations on information used for conducting administrative activities to improve health care quality.

  HSYSADMINhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealth system administration

To perform one or more operations on information to administer the electronic systems used for the delivery of health care.

  LABELINGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonlabeling

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.

  METAMGThttp://terminology.hl7.org/CodeSystem/v3-ActReasonmetadata 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.

  MEMADMINhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmember administration

To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program.

  MILCDMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmilitary command

To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law.

  PATADMINhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient administration

To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient.

  PATSFTYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient safety

To perform one or more operations on information in processes related to ensuring the safety of health care.

  PERFMSRhttp://terminology.hl7.org/CodeSystem/v3-ActReasonperformance measure

To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions.

  RECORDMGThttp://terminology.hl7.org/CodeSystem/v3-ActReasonrecords management

To perform one or more operations on information used within the health records management process.

  SYSDEVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsystem development

To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application.

  HTESThttp://terminology.hl7.org/CodeSystem/v3-ActReasontest 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.

  TRAINhttp://terminology.hl7.org/CodeSystem/v3-ActReasontraining

To perform one or more operations on information used in training and education.

  HPAYMThttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealthcare payment

To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care.

  CLMATTCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonclaim 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.

  COVAUTHhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncoverage authorization

To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services.

  COVERAGEhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncoverage under policy or program

To perform one or more operations on information for conducting activities related to coverage under a program or policy.

  ELIGDTRMhttp://terminology.hl7.org/CodeSystem/v3-ActReasoneligibility 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.

  ELIGVERhttp://terminology.hl7.org/CodeSystem/v3-ActReasoneligibility 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.

  ENROLLMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonenrollment

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.

  MILDCRGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmilitary 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.

  REMITADVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonremittance advice

To perform one or more operations on information about the amount remitted for a health care claim.

  HRESCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonhealthcare 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.

  BIORCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonbiomedical 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.

  CLINTRCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical 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.

  CLINTRCHNPChttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical 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.

  CLINTRCHPChttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical 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.

  PRECLINTRCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpreclinical 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.

  DSRCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasondisease 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.

  POARCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpopulation 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.

  TRANSRCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasontranslational 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.

  PATRQThttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient requested

To perform one or more operations on information in response to a patient's request.

  FAMRQThttp://terminology.hl7.org/CodeSystem/v3-ActReasonfamily requested

To perform one or more operations on information in response to a request by a family member authorized by the patient.

  PWATRNYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpower 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.

  SUPNWKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsupport network

To perform one or more operations on information in response to a request by a person authorized by the patient.

  PUBHLTHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpublic health

To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions.

  DISASTERhttp://terminology.hl7.org/CodeSystem/v3-ActReasondisaster

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.

  THREAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonthreat

To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence.

  TREAThttp://terminology.hl7.org/CodeSystem/v3-ActReasontreatment

To perform one or more operations on information for provision of health care.

  CLINTRLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical trial

To perform health care as part of the clinical trial protocol.

  COChttp://terminology.hl7.org/CodeSystem/v3-ActReasoncoordination 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."

  ETREAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonEmergency Treatment

To perform one or more operations on information for provision of immediately needed health care for an emergent condition.

  BTGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonbreak 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.

  ERTREAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonemergency 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.

  POPHLTHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpopulation 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.

  _ActHealthInformationPrivacyReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActHealthInformationPrivacyReason

**Description:**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.

  _ActInformationPrivacyReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActInformationPrivacyReason

**Description:**The rationale or purpose for an act relating to the management of personal information, such as disclosing personal tax information for the purpose of complying with a court order.

  MARKThttp://terminology.hl7.org/CodeSystem/v3-ActReasonmarketing

Description:

  OPERAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonoperations

**Description:**Administrative and contractual processes required to support an activity, product, or service

  LEGALhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsubpoena

**Definition:**To provide information as a result of a subpoena.

  ACCREDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonaccreditation

**Description:**Operational activities conducted for the purposes of meeting of criteria defined by an accrediting entity for an activity, product, or service

  COMPLhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncompliance

**Description:**Operational activities required to meet a mandate related to an activity, product, or service

  ENADMINhttp://terminology.hl7.org/CodeSystem/v3-ActReasonentity administration

**Description:**Operational activities conducted to administer information relating to entities involves with an activity, product, or service

  OUTCOMShttp://terminology.hl7.org/CodeSystem/v3-ActReasonoutcome measure

**Description:**Operational activities conducted for the purposes of assessing the results of an activity, product, or service

  PRGRPThttp://terminology.hl7.org/CodeSystem/v3-ActReasonprogram reporting

**Description:**Operational activities conducted to meet program accounting requirements related to an activity, product, or service

  QUALIMPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonquality improvement

**Description:**Operational activities conducted for the purposes of improving the quality of an activity, product, or service

  SYSADMNhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsystem administration

**Description:**Operational activities conducted to administer the electronic systems used for an activity, product, or service

  PAYMThttp://terminology.hl7.org/CodeSystem/v3-ActReasonpayment

**Description:**Administrative, financial, and contractual processes related to payment for an activity, product, or service

  RESCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonresearch

**Description:**Investigative activities conducted for the purposes of obtaining knowledge

  SRVChttp://terminology.hl7.org/CodeSystem/v3-ActReasonservice

**Description:**Provision of a service, product, or capability to an individual or organization

  _ActInvalidReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActInvalidReason

Description: Types of reasons why a substance is invalid for use.

  ADVSTORAGEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonadverse storage condition

Description: Storage conditions caused the substance to be ineffective.

  COLDCHNBRKhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncold chain break

Description: Cold chain was not maintained for the substance.

  EXPLOThttp://terminology.hl7.org/CodeSystem/v3-ActReasonexpired lot

Description: The lot from which the substance was drawn was expired.

  OUTSIDESCHEDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonadministered outside recommended schedule or practice

The substance was administered outside of the recommended schedule or practice.

  PRODRECALLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonproduct recall

Description: The substance was recalled by the manufacturer.

  _ActInvoiceCancelReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActInvoiceCancelReason

Domain specifies the codes used to describe reasons why a Provider is cancelling an Invoice or Invoice Grouping.

  INCCOVPTYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonincorrect covered party as patient

The covered party (patient) specified with the Invoice is not correct.

  INCINVOICEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonincorrect billing

The billing information, specified in the Invoice Elements, is not correct. This could include incorrect costing for items included in the Invoice.

  INCPOLICYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonincorrect policy

The policy specified with the Invoice is not correct. For example, it may belong to another Adjudicator or Covered Party.

  INCPROVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonincorrect provider

The provider specified with the Invoice is not correct.

  _ActNoImmunizationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActNoImmunizationReason

A coded description of the reason for why a patient did not receive a scheduled immunization.

(important for public health strategy

  IMMUNEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonimmunity

**Definition:**Testing has shown that the patient already has immunity to the agent targeted by the immunization.

  MEDPREChttp://terminology.hl7.org/CodeSystem/v3-ActReasonmedical precaution

**Definition:**The patient currently has a medical condition for which the vaccine is contraindicated or for which precaution is warranted.

  OSTOCKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonproduct out of stock

**Definition:**There was no supply of the product on hand to perform the service.

  PATOBJhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient objection

**Definition:**The patient or their guardian objects to receiving the vaccine.

  PHILISOPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonphilosophical objection

**Definition:**The patient or their guardian objects to receiving the vaccine because of philosophical beliefs.

  RELIGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonreligious objection

**Definition:**The patient or their guardian objects to receiving the vaccine on religious grounds.

  VACEFFhttp://terminology.hl7.org/CodeSystem/v3-ActReasonvaccine efficacy concerns

**Definition:**The intended vaccine has expired or is otherwise believed to no longer be effective.

**Example:**Due to temperature exposure.

  VACSAFhttp://terminology.hl7.org/CodeSystem/v3-ActReasonvaccine safety concerns

**Definition:**The patient or their guardian objects to receiving the vaccine because of concerns over its safety.

  _ActSupplyFulfillmentRefusalReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActSupplyFulfillmentRefusalReason

Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision. E.g. "Suspect fraud", "Possible abuse", "Contraindicated".

(used when capturing 'refusal to fill' annotations)

  FRR01http://terminology.hl7.org/CodeSystem/v3-ActReasonorder stopped

**Definition:**The order has been stopped by the prescriber but this fact has not necessarily captured electronically.

**Example:**A verbal stop, a fax, etc.

  FRR02http://terminology.hl7.org/CodeSystem/v3-ActReasonstale-dated order

**Definition:**Order has not been fulfilled within a reasonable amount of time, and may not be current.

  FRR03http://terminology.hl7.org/CodeSystem/v3-ActReasonincomplete data

**Definition:**Data needed to safely act on the order which was expected to become available independent of the order is not yet available

**Example:**Lab results, diagnostic imaging, etc.

  FRR04http://terminology.hl7.org/CodeSystem/v3-ActReasonproduct unavailable

**Definition:**Product not available or manufactured. Cannot supply.

  FRR05http://terminology.hl7.org/CodeSystem/v3-ActReasonethical/religious

**Definition:**The dispenser has ethical, religious or moral objections to fulfilling the order/dispensing the product.

  FRR06http://terminology.hl7.org/CodeSystem/v3-ActReasonunable to provide care

**Definition:**Fulfiller not able to provide appropriate care associated with fulfilling the order.

**Example:**Therapy requires ongoing monitoring by fulfiller and fulfiller will be ending practice, leaving town, unable to schedule necessary time, etc.

  _ClinicalResearchEventReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonClinicalResearchEventReason

**Definition:**Specifies the reason that an event occurred in a clinical research study.

  REThttp://terminology.hl7.org/CodeSystem/v3-ActReasonretest

**Definition:**The event occurred so that a test or observation performed at a prior event could be performed again due to conditions set forth in the protocol.

  SCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonscheduled

**Definition:**The event occurred due to it being scheduled in the research protocol.

  TRMhttp://terminology.hl7.org/CodeSystem/v3-ActReasontermination

**Definition:**The event occurred in order to terminate the subject's participation in the study.

  UNShttp://terminology.hl7.org/CodeSystem/v3-ActReasonunscheduled

**Definition:**The event that occurred was initiated by a study participant (e.g. the subject or the investigator), and did not occur for protocol reasons.

  _ClinicalResearchObservationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonClinicalResearchObservationReason

**Definition:**SSpecifies the reason that a test was performed or observation collected in a clinical research study.

**Note:**This set of codes are not strictly reasons, but are used in the currently Normative standard. Future revisions of the specification will model these as ActRelationships and thes codes may subsequently be retired. Thus, these codes should not be used for new specifications.

  NPThttp://terminology.hl7.org/CodeSystem/v3-ActReasonnon-protocol

**Definition:**The observation or test was neither defined or scheduled in the study protocol.

  PPThttp://terminology.hl7.org/CodeSystem/v3-ActReasonper protocol

**Definition:**The observation or test occurred due to it being defined in the research protocol, and during an activity or event that was scheduled in the protocol.

  UPThttp://terminology.hl7.org/CodeSystem/v3-ActReasonper definition

**:**The observation or test occurred as defined in the research protocol, but at a point in time not specified in the study protocol.

  _CombinedPharmacyOrderSuspendReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonCombinedPharmacyOrderSuspendReasonCode

**Description:**Indicates why the prescription should be suspended.

  ALTCHOICEhttp://terminology.hl7.org/CodeSystem/v3-ActReasontry another treatment first

**Description:**This therapy has been ordered as a backup to a preferred therapy. This order will be released when and if the preferred therapy is unsuccessful.

  CLARIFhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprescription requires clarification

**Description:**Clarification is required before the order can be acted upon.

  DRUGHIGHhttp://terminology.hl7.org/CodeSystem/v3-ActReasondrug level too high

**Description:**The current level of the medication in the patient's system is too high. The medication is suspended to allow the level to subside to a safer level.

  HOSPADMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonadmission to hospital

**Description:**The patient has been admitted to a care facility and their community medications are suspended until hospital discharge.

  LABINThttp://terminology.hl7.org/CodeSystem/v3-ActReasonlab interference issues

**Description:**The therapy would interfere with a planned lab test and the therapy is being withdrawn until the test is completed.

  NON-AVAILhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient not-available

**Description:**Patient not available for a period of time due to a scheduled therapy, leave of absence or other reason.

  PREGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonparent is pregnant/breast feeding

**Description:**The patient is pregnant or breast feeding. The therapy will be resumed when the pregnancy is complete and the patient is no longer breastfeeding.

  SALGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonallergy

**Description:**The patient is believed to be allergic to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm.

  SDDIhttp://terminology.hl7.org/CodeSystem/v3-ActReasondrug interacts with another drug

**Description:**The drug interacts with a short-term treatment that is more urgently required. This order will be resumed when the short-term treatment is complete.

  SDUPTHERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonduplicate therapy

**Description:**Another short-term co-occurring therapy fulfills the same purpose as this therapy. This therapy will be resumed when the co-occuring therapy is complete.

  SINTOLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsuspected intolerance

**Description:**The patient is believed to have an intolerance to a substance that is part of the therapy and the therapy is being temporarily withdrawn to confirm.

  SURGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient scheduled for surgery

**Description:**The drug is contraindicated for patients receiving surgery and the patient is scheduled to be admitted for surgery in the near future. The drug will be resumed when the patient has sufficiently recovered from the surgery.

  WASHOUThttp://terminology.hl7.org/CodeSystem/v3-ActReasonwaiting for old drug to wash out

**Description:**The patient was previously receiving a medication contraindicated with the current medication. The current medication will remain on hold until the prior medication has been cleansed from their system.

  _ControlActNullificationReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonControlActNullificationReasonCode

**Description:**Identifies reasons for nullifying (retracting) a particular control act.

  ALTDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonaltered decision

**Description:**The decision on which the recorded information was based was changed before the decision had an effect.

**Example:**Aborted prescription before patient left office, released prescription before suspend took effect.

  EIEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonentered in error

**Description:**The information was recorded incorrectly or was recorded in the wrong record.

  NORECMTCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno record match

Description: There is no match for the record in the database.

  _ControlActNullificationRefusalReasonTypehttp://terminology.hl7.org/CodeSystem/v3-ActReasonControlActNullificationRefusalReasonType

Description: Reasons to refuse a transaction to be undone.

  INRQSTATEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonin requested state

The record is already in the requested state.

  NOMATCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno match

Description: There is no match.

  NOPRODMTCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno product match

Description: There is no match for the product in the master file repository.

  NOSERMTCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno service match

Description: There is no match for the service in the master file repository.

  NOVERMTCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno version match

Description: There is no match for the record and version.

  NOPERMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno permission

Description: There is no permission.

  NOUSERPERMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno user permission

**Definition:**The user does not have permission

  NOAGNTPERMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno agent permission

Description: The agent does not have permission.

  NOUSRPERMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno user permission

Description: The user does not have permission.

  WRNGVERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonwrong version

Description: The record and version requested to update is not the current version.

  _ControlActReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonControlActReason

Identifies why a specific query, request, or other trigger event occurred.

  _MedicationOrderAbortReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonmedication order abort reason

**Description:**Indicates the reason the medication order should be aborted.

  DISCONThttp://terminology.hl7.org/CodeSystem/v3-ActReasonproduct discontinued

**Description:**The medication is no longer being manufactured or is otherwise no longer available.

  INEFFECThttp://terminology.hl7.org/CodeSystem/v3-ActReasonineffective

**Description:**The therapy has been found to not have the desired therapeutic benefit on the patient.

  MONIThttp://terminology.hl7.org/CodeSystem/v3-ActReasonresponse to monitoring

**Description:**Monitoring the patient while taking the medication, the decision has been made that the therapy is no longer appropriate.

  NOREQhttp://terminology.hl7.org/CodeSystem/v3-ActReasonno longer required for treatment

**Description:**The underlying condition has been resolved or has evolved such that a different treatment is no longer needed.

  NOTCOVERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnot covered

**Description:**The product does not have (or no longer has) coverage under the patientaTMs insurance policy.

  PREFUShttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient refuse

**Description:**The patient refused to take the product.

  RECALLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonproduct recalled

**Description:**The manufacturer or other agency has requested that stocks of a medication be removed from circulation.

  REPLACEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonchange in order

**Description:**Item in current order is no longer in use as requested and a new one has/will be created to replace it.

  DOSECHGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonchange in medication/dose

**Description:**The medication is being re-prescribed at a different dosage.

  REPLACEFIXhttp://terminology.hl7.org/CodeSystem/v3-ActReasonerror in order

**Description:**Current order was issued with incorrect data and a new order has/will be created to replace it.

  UNABLEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonunable to use

Description:<The patient is not (or is no longer) able to use the medication in a manner prescribed.

**Example:**CanaTMt swallow.

  _MedicationOrderReleaseReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonmedication order release reason

**Definition:**A collection of concepts that indicate why the prescription should be released from suspended state.

  HOLDDONEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsuspend reason no longer applies

**Definition:**The original reason for suspending the medication has ended.

  HOLDINAPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonsuspend reason inappropriate

Definition:

  _ModifyPrescriptionReasonTypehttp://terminology.hl7.org/CodeSystem/v3-ActReasonModifyPrescriptionReasonType

Types of reason why a prescription is being changed.

  ADMINERRORhttp://terminology.hl7.org/CodeSystem/v3-ActReasonadministrative error in order

Order was created with incorrect data and is changed to reflect the intended accuracy of the order.

  CLINMODhttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical modification

Order is changed based on a clinical reason.

  _PharmacySupplyEventAbortReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonPharmacySupplyEventAbortReason

**Definition:**Identifies why the dispense event was not completed.

  CONTRAhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncontraindication

**Definition:**Contraindication identified

  FOABORThttp://terminology.hl7.org/CodeSystem/v3-ActReasonorder aborted

**Definition:**Order to be fulfilled was aborted

  FOSUSPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonorder suspended

**Definition:**Order to be fulfilled was suspended

  NOPICKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnot picked up

**Definition:**Patient did not come to get medication

  PATDEChttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient changed mind

**Definition:**Patient changed their mind regarding obtaining medication

  QUANTCHGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonchange supply quantity

**Definition:**Patient requested a revised quantity of medication

  _PharmacySupplyEventStockReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonpharmacy supply event stock reason

**Definition:**A collection of concepts that indicates the reason for a "bulk supply" of medication.

  FLRSTCKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonfloor stock

**Definition:**The bulk supply is issued to replenish a ward for local dispensing. (Includes both mobile and fixed-location ward stocks.)

  LTChttp://terminology.hl7.org/CodeSystem/v3-ActReasonlong term care use

**Definition:**The bulk supply will be administered within a long term care facility.

  OFFICEhttp://terminology.hl7.org/CodeSystem/v3-ActReasonoffice use

**Definition:**The bulk supply is intended for general clinician office use.

  PHARMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpharmacy transfer

**Definition:**The bulk supply is being transferred to another dispensing facility to.

**Example:**Alleviate a temporary shortage.

  PROGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprogram use

**Definition:**The bulk supply is intended for dispensing according to a specific program.

**Example:**Mass immunization.

  _PharmacySupplyRequestRenewalRefusalReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonpharmacy supply request renewal refusal reason

**Definition:**A collection of concepts that identifies why a renewal prescription has been refused.

  ALREADYRXhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnew prescription exists

**Definition:**Patient has already been given a new (renewal) prescription.

  FAMPHYShttp://terminology.hl7.org/CodeSystem/v3-ActReasonfamily physician must authorize further fills

**Definition:**Request for further authorization must be done through patient's family physician.

  MODIFYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmodified prescription exists

**Definition:**Therapy has been changed and new prescription issued

  NEEDAPMThttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient must make appointment

**Definition:**Patient must see prescriber prior to further fills.

  NOTAVAILhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprescriber not available

**Definition:**Original prescriber is no longer available to prescribe and no other prescriber has taken responsibility for the patient.

  NOTPAThttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient no longer in this practice

**Definition:**Patient no longer or has never been under this prescribers care.

  ONHOLDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmedication on hold

**Definition:**This medication is on hold.

  PRNAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonproduct not available

**Description:**This product is not available or manufactured.

  STOPMEDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprescriber stopped medication for patient

Renewing or original prescriber informed patient to stop using the medication.

  TOOEARLYhttp://terminology.hl7.org/CodeSystem/v3-ActReasontoo early

**Definition:**The patient should have medication remaining.

  _SupplyOrderAbortReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonsupply order abort reason

**Definition:**A collection of concepts that indicates why the prescription should no longer be allowed to be dispensed (but can still administer what is already being dispensed).

  IMPROVhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncondition improved

**Definition:**The patient's medical condition has nearly abated.

  INTOLhttp://terminology.hl7.org/CodeSystem/v3-ActReasonintolerance

**Description:**The patient has an intolerance to the medication.

  NEWSTRhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnew strength

**Definition:**The current medication will be replaced by a new strength of the same medication.

  NEWTHERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnew therapy

**Definition:**A new therapy will be commenced when current supply exhausted.

  _ControlActReasonConditionNullifyhttp://terminology.hl7.org/CodeSystem/v3-ActReasonControlActReasonConditionNullify

Indicates why the ConditionaTMs status was changed to Nullified. Examples administrative error, diagnostic error.

  _GenericUpdateReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonGenericUpdateReasonCode

**Description:**Identifies why a change is being made to a record.

  CHGDATAhttp://terminology.hl7.org/CodeSystem/v3-ActReasoninformation change

**Description:**Information has changed since the record was created.

  FIXDATAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonerror correction

**Description:**Previously recorded information was erroneous and is being corrected.

  MDATAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonmerge data

Information is combined into the record.

  NEWDATAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonnew information

**Description:**New information has become available to supplement the record.

  UMDATAhttp://terminology.hl7.org/CodeSystem/v3-ActReasonunmerge data

Information is separated from the record.

  _PatientProfileQueryReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient profile query reason

**Definition:**A collection of concepts identifying why the patient's profile is being queried.

  ADMREVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonadministrative review

Definition: To evaluate for service authorization, payment, reporting, or performance/outcome measures.

  PATCARhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient care

**Definition:**To obtain records as part of patient care.

  PATREQhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient request query

**Definition:**Patient requests information from their profile.

  PRCREVhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpractice review

**Definition:**To evaluate the provider's current practice for professional-improvement reasons.

  REGULhttp://terminology.hl7.org/CodeSystem/v3-ActReasonregulatory review

**Description:**Review for the purpose of regulatory compliance.

  RSRCHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonresearch

**Definition:**To provide research data, as authorized by the patient.

  VALIDATIONhttp://terminology.hl7.org/CodeSystem/v3-ActReasonvalidation review

**Description:**To validate the patient's record.

**Example:**Merging or unmerging records.

  _PharmacySupplyRequestFulfillerRevisionRefusalReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonPharmacySupplyRequestFulfillerRevisionRefusalReasonCode

**Definition:**Indicates why the request to transfer a prescription from one dispensing facility to another has been refused.

  LOCKEDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonlocked

**Definition:**The prescription may not be reassigned from the original pharmacy.

  UNKWNTARGEThttp://terminology.hl7.org/CodeSystem/v3-ActReasonunknown target

**Definition:**The target facility does not recognize the dispensing facility.

  _RefusalReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonRefusalReasonCode

Description: Identifies why a request to add (or activate) a record is being refused. Examples include the receiving system not able to match the identifier and find that record in the receiving system, having no permission, or a detected issue exists which precludes the requested action.

  _SchedulingActReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonSchedulingActReason

Reasons for cancelling or rescheduling an Appointment

  BLKhttp://terminology.hl7.org/CodeSystem/v3-ActReasonUnexpected Block (of Schedule)

The time slots previously allocated are now blocked and no longer available for booking Appointments

  DEChttp://terminology.hl7.org/CodeSystem/v3-ActReasonPatient Deceased

The Patient is deceased

  FINhttp://terminology.hl7.org/CodeSystem/v3-ActReasonNo Financial Backing

Patient unable to pay and not covered by insurance

  MEDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonMedical Status Altered

The medical condition of the Patient has changed

  MTGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonIn an outside meeting

The Physician is in a meeting. For example, he/she may request administrative time to talk to family after appointment

  PHYhttp://terminology.hl7.org/CodeSystem/v3-ActReasonPhysician request

The Physician requested the action

  _StatusRevisionRefusalReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonStatusRevisionRefusalReasonCode

Indicates why the act revision (status update) is being refused.

  FILLEDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonfully filled

Ordered quantity has already been completely fulfilled.

  _SubstanceAdministrationPermissionRefusalReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonSubstanceAdministrationPermissionRefusalReasonCode

**Definition:**Indicates why the requested authorization to prescribe or dispense a medication has been refused.

  PATINELIGhttp://terminology.hl7.org/CodeSystem/v3-ActReasonpatient not eligible

**Definition:**Patient not eligible for drug

  PROTUNMEThttp://terminology.hl7.org/CodeSystem/v3-ActReasonprotocol not met

**Definition:**Patient does not meet required protocol

  PROVUNAUTHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonprovider not authorized

**Definition:**Provider is not authorized to prescribe or dispense

  _SubstanceAdminSubstitutionNotAllowedReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonSubstanceAdminSubstitutionNotAllowedReason

Reasons why substitution of a substance administration request is not permitted.

  ALGINThttp://terminology.hl7.org/CodeSystem/v3-ActReasonallergy intolerance

Definition: Patient has had a prior allergic intolerance response to alternate product or one of its components.

  COMPCONhttp://terminology.hl7.org/CodeSystem/v3-ActReasoncompliance concern

Definition: Patient has compliance issues with medication such as differing appearance, flavor, size, shape or consistency.

  THERCHARhttp://terminology.hl7.org/CodeSystem/v3-ActReasontherapeutic characteristics

The prescribed product has specific clinical release or other therapeutic characteristics not shared by other substitutable medications.

  TRIALhttp://terminology.hl7.org/CodeSystem/v3-ActReasonclinical trial drug

Definition: The specific manufactured drug is part of a clinical trial.

  _SubstanceAdminSubstitutionReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonSubstanceAdminSubstitutionReason
  CThttp://terminology.hl7.org/CodeSystem/v3-ActReasoncontinuing therapy

Indicates that the decision to substitute or to not substitute was driven by a desire to maintain consistency with a pre-existing therapy. I.e. The performer provided the same item/service as had been previously provided rather than providing exactly what was ordered, or rather than substituting with a lower-cost equivalent.

  FPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonformulary policy

Indicates that the decision to substitute or to not substitute was driven by a policy expressed within the formulary.

  OShttp://terminology.hl7.org/CodeSystem/v3-ActReasonout of stock

In the case of 'substitution', indicates that the substitution occurred because the ordered item was not in stock. In the case of 'no substitution', indicates that a cheaper equivalent was not substituted because it was not in stock.

  RRhttp://terminology.hl7.org/CodeSystem/v3-ActReasonregulatory requirement

Indicates that the decision to substitute or to not substitute was driven by a jurisdictional regulatory requirement mandating or prohibiting substitution.

  _TransferActReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonTransferActReason

The explanation for why a patient is moved from one location to another within the organization

  ERhttp://terminology.hl7.org/CodeSystem/v3-ActReasonError

Moved to an error in placing the patient in the original location.

  RQhttp://terminology.hl7.org/CodeSystem/v3-ActReasonRequest

Moved at the request of the patient.

  _ActAdjudicationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActAdjudicationReason

Explanatory codes that describe reasons why an Adjudicator has financially adjusted an invoice (claim).

A companion domain (ActAdjudicationInformationCode) includes information reasons which do not have a financial impact on an invoice (claim).

Example adjudication reason code is AA-CLAIM-0011 - Only Basic Procedure/Test Eligible.

Codes from this domain further rationalizes ActAdjudicationCodes (e.g. AA - Adjudicated with Adjustment), which are used to describe the process of adjudicating an invoice. For AS - Adjudicated as Submitted, there should be no specification of ActAdjudicationReason codes, as there are no financial adjustments against the invoice.

  _ActBillableServiceReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActBillableServiceReason

Definition: This domain is used to document reasons for providing a billable service; the billable services may include both clinical services and social services.

  _ActBillableClinicalServiceReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActBillableClinicalServiceReason

Reason for Clinical Service being performed.

This domain excludes reasons specified by diagnosed conditions.

Examples of values from this domain include duplicate therapy and fraudulent prescription.

  _MedicallyNecessaryDuplicateProcedureReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonMedicallyNecessaryDuplicateProcedureReason

Definition: This domain is used to document why the procedure is a duplicate of one ordered/charged previously for the same patient within the same date of service and has been determined to be medically necessary.

Example: A doctor needs a different view in a chest X-Ray.

  _ActCoverageLevelRasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonActCoverageLevelRasonCode

**Description:**Represents the reason for the level of coverage provided under the policy or program in terms of the types of entities that may play covered parties based on their personal relationships or employment status.

  _ActImmunizationReasonhttp://terminology.hl7.org/CodeSystem/v3-ActReasonActImmunizationReason

**Description:**A coded description of the reason for why a patient was administered an immunization.

**Examples:**Post Exposure - Reason, Universal Immunization Program, Outbreak Control, Universal School Program

  _ConrolActNullificationReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonConrolActNullificationReasonCode

**Description:**Identifies reasons for nullifying (retracting) a particular control act.

Examples:"Entered in error", "altered decision", etc.

  _NonPerformanceReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonNonPerformanceReasonCode

The reason the action wasn't performed, e.g. why the medication was not taken. If an action wasn"t performed, it is often clinically important to know why the action wasn"t taken.

*Examples:*Patient refused, clinically inappropriate, absolute contraindication etc.

  _ReasonForNotEvaluatingDevicehttp://terminology.hl7.org/CodeSystem/v3-ActReasonReasonForNotEvaluatingDevice

Code assigned to indicate the rationale for not performing an evaluation investigation on a device for which a defect has been reported.

Examples include: device received in a condition that made analysis impossible, device evaluation anticipated but not yet begun, device not made by company.

  _ReferralReasonCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonReferralReasonCode

The reason a referral was made.

*Examples:*Specialized Medical Assistance, Other Care Requirements.

  BONUShttp://terminology.hl7.org/CodeSystem/v3-ActReason
  CHDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonChildren only

**Description:**The level of coverage under the policy or program is available only to children

  DEPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonDependents only

**Description:**The level of coverage under the policy or program is available only to a subscriber's dependents.

  ECHhttp://terminology.hl7.org/CodeSystem/v3-ActReasonEmployee and children

**Description:**The level of coverage under the policy or program is available to an employee and his or her children.

  EDUhttp://terminology.hl7.org/CodeSystem/v3-ActReason
  EMPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonEmployee only

**Description:**The level of coverage under the policy or program is available only to an employee.

  ESPhttp://terminology.hl7.org/CodeSystem/v3-ActReasonEmployee and spouse

**Description:**The level of coverage under the policy or program is available to an employee and his or her spouse.

  FAMhttp://terminology.hl7.org/CodeSystem/v3-ActReasonFamily

**Description:**The level of coverage under the policy or program is available to a subscriber's family.

  INDhttp://terminology.hl7.org/CodeSystem/v3-ActReasonIndividual

**Description:**The level of coverage under the policy or program is available to an individual.

  INVOICEhttp://terminology.hl7.org/CodeSystem/v3-ActReason
  PROAhttp://terminology.hl7.org/CodeSystem/v3-ActReason
  RECOVhttp://terminology.hl7.org/CodeSystem/v3-ActReason
  RETROhttp://terminology.hl7.org/CodeSystem/v3-ActReason
  SPChttp://terminology.hl7.org/CodeSystem/v3-ActReasonSpouse and children

**Description:**The level of coverage under the policy or program is available to a subscriber's spouse and children

  SPOhttp://terminology.hl7.org/CodeSystem/v3-ActReasonSpouse only

**Description:**The level of coverage under the policy or program is available only to a subscribers spouse

  TRANhttp://terminology.hl7.org/CodeSystem/v3-ActReason

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

History

DateActionCustodianAuthorComment
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2021-01-20deprecateVocabulary WGTed KleindeprecationEffectiveVersion=813-20090214 This value set was removed prior to the December 2019 V3 coremif release.
2020-08-17reviseVocabulary WGTed KleinNot imported as not in coremif; add for FHIR support