Release 5 Preview #2
TerminologyThis page is part of the FHIR Specification (v4.4.0: R5 Preview #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R4 R3 R2
| Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
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".
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="v3-ActReason"/> <meta> <lastUpdated value="2019-07-31T00:00:00.000+10:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Release Date: 2019-07-31</p> <table class="grid"> <tr> <td> <b> Level</b> </td> <td> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActAccommodationReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActAccommodationReason"> </a> </td> <td> Identifies the reason the patient is assigned to this accommodation type <br/> </td> </tr> <tr> <td> 2</td> <td> ACCREQNA <a name="v3-ActReason-ACCREQNA"> </a> </td> <td> Accommodation Requested Not Available</td> <td> Accommodation requested is not available. <br/> </td> </tr> <tr> <td> 2</td> <td> FLRCNV <a name="v3-ActReason-FLRCNV"> </a> </td> <td> Floor Convenience</td> <td> Accommodation is assigned for floor convenience. <br/> </td> </tr> <tr> <td> 2</td> <td> MEDNEC <a name="v3-ActReason-MEDNEC"> </a> </td> <td> Medical Necessity</td> <td> Required for medical reasons(s). <br/> </td> </tr> <tr> <td> 2</td> <td> PAT <a name="v3-ActReason-PAT"> </a> </td> <td> Patient request</td> <td> The Patient requested the action <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActCoverageReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActCoverageReason"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_EligibilityActReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_EligibilityActReasonCode"> </a> </td> <td> Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. <br/> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActIneligibilityReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActIneligibilityReason"> </a> </td> <td> Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy. <br/> Examples are client deceased & adopted client has been given a new policy identifier. <br/> </td> </tr> <tr> <td> 4</td> <td> COVSUS <a name="v3-ActReason-COVSUS"> </a> </td> <td> coverage suspended</td> <td> 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. <br/> Example: Coverage may be suspended during a strike situation, when employer benefits for employees are not covered (i.e. not in effect). <br/> </td> </tr> <tr> <td> 4</td> <td> DECSD <a name="v3-ActReason-DECSD"> </a> </td> <td> deceased</td> <td> Client deceased. <br/> </td> </tr> <tr> <td> 4</td> <td> REGERR <a name="v3-ActReason-REGERR"> </a> </td> <td> registered in error</td> <td> Client was registered in error. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_CoverageEligibilityReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_CoverageEligibilityReason"> </a> </td> <td> Definition: Identifies the reason or rational for why a person is eligibile for benefits under an insurance policy or progam. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> AGE <a name="v3-ActReason-AGE"> </a> </td> <td> age eligibility</td> <td> A person becomes eligible for a program based on age. <br/> Example: In the U.S., a person who is 65 years of age or older is eligible for Medicare. <br/> </td> </tr> <tr> <td> 4</td> <td> CRIME <a name="v3-ActReason-CRIME"> </a> </td> <td> crime victim</td> <td> A person becomes eligible for insurance or a program because of crime related health condition or injury. <br/> Example: A person is a claimant under the U.S. Crime Victims Compensation program. <br/> </td> </tr> <tr> <td> 4</td> <td> DIS <a name="v3-ActReason-DIS"> </a> </td> <td> disability</td> <td> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> EMPLOY <a name="v3-ActReason-EMPLOY"> </a> </td> <td> employment benefit</td> <td> A person becomes eligible for insurance provided as an employment benefit based on employment status. <br/> </td> </tr> <tr> <td> 4</td> <td> FINAN <a name="v3-ActReason-FINAN"> </a> </td> <td> financial eligibility</td> <td> A person becomes eligible for a program based on financial criteria. <br/> Example: A person whose family income is below a financial threshold for eligibility for Medicaid or SCHIP. <br/> </td> </tr> <tr> <td> 4</td> <td> HEALTH <a name="v3-ActReason-HEALTH"> </a> </td> <td> health status</td> <td> A person becomes eligible for a program because of a qualifying health condition or injury. <br/> 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 <br/> </td> </tr> <tr> <td> 4</td> <td> MULTI <a name="v3-ActReason-MULTI"> </a> </td> <td> multiple criteria eligibility</td> <td> A person becomes eligible for a program based on more than one criterion. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> PNC <a name="v3-ActReason-PNC"> </a> </td> <td> property and casualty condition</td> <td> 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. <br/> Example: A person is a claimant under a homeowners insurance policy because of an injury sustained on the policyholderaTMs premises. <br/> </td> </tr> <tr> <td> 4</td> <td> STATUTORY <a name="v3-ActReason-STATUTORY"> </a> </td> <td> statutory eligibility</td> <td> A person becomes eligible for a program based on statutory criteria. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> VEHIC <a name="v3-ActReason-VEHIC"> </a> </td> <td> motor vehicle accident victim</td> <td> A person becomes a claimant under a motor vehicle accident insurance because of a motor vehicle accident related health condition or injury. <br/> </td> </tr> <tr> <td> 4</td> <td> WORK <a name="v3-ActReason-WORK"> </a> </td> <td> work related</td> <td> A person becomes eligible for insurance or a program because of a work related health condition or injury. <br/> Example: A person is a claimant under the U.S. Black Lung Program. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInformationManagementReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActInformationManagementReason"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActHealthInformationManagementReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActHealthInformationManagementReason"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActConsentInformationAccessOverrideReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActConsentInformationAccessOverrideReason"> </a> </td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> OVRER <a name="v3-ActReason-OVRER"> </a> </td> <td> emergency treatment override</td> <td> 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. <br/> Usage Notes: The patient is unable to provide consent, but the provider determines they have an urgent healthcare related reason to access the record. <br/> </td> </tr> <tr> <td> 4</td> <td> OVRINCOMP <a name="v3-ActReason-OVRINCOMP"> </a> </td> <td> incompetency override</td> <td> To perform one or more operations on information to which the patient has not consented because deemed incompetent to provide consent. <br/> 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". <br/> </td> </tr> <tr> <td> 4</td> <td> OVRPJ <a name="v3-ActReason-OVRPJ"> </a> </td> <td> professional judgment override</td> <td> To perform one or more operations on information to which the patient declined to consent for providing health care. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> OVRPS <a name="v3-ActReason-OVRPS"> </a> </td> <td> public safety override</td> <td> To perform one or more operations on information to which the patient has not consented for public safety reasons. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> OVRTPS <a name="v3-ActReason-OVRTPS"> </a> </td> <td> third party safety override</td> <td> To perform one or more operations on information to which the patient has not consented for third party safety. <br/> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> PurposeOfUse <a name="v3-ActReason-PurposeOfUse"> </a> </td> <td> purpose of use</td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> HMARKT <a name="v3-ActReason-HMARKT"> </a> </td> <td> healthcare marketing</td> <td> To perform one or more operations on information for marketing services and products related to health care. <br/> </td> </tr> <tr> <td> 4</td> <td> HOPERAT <a name="v3-ActReason-HOPERAT"> </a> </td> <td> healthcare operations</td> <td> To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care. <br/> </td> </tr> <tr> <td> 5</td> <td> CAREMGT <a name="v3-ActReason-CAREMGT"> </a> </td> <td> care management</td> <td> 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. <br/> 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. <br/> 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." <br/> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> DONAT <a name="v3-ActReason-DONAT"> </a> </td> <td> donation</td> <td> To perform one or more operations on information used for cadaveric organ, eye or tissue donation. <br/> </td> </tr> <tr> <td> 5</td> <td> FRAUD <a name="v3-ActReason-FRAUD"> </a> </td> <td> fraud</td> <td> To perform one or more operations on information used for fraud detection and prevention processes. <br/> </td> </tr> <tr> <td> 5</td> <td> GOV <a name="v3-ActReason-GOV"> </a> </td> <td> government</td> <td> To perform one or more operations on information used within government processes. <br/> </td> </tr> <tr> <td> 5</td> <td> HACCRED <a name="v3-ActReason-HACCRED"> </a> </td> <td> health accreditation</td> <td> To perform one or more operations on information for conducting activities related to meeting accreditation criteria. <br/> </td> </tr> <tr> <td> 5</td> <td> HCOMPL <a name="v3-ActReason-HCOMPL"> </a> </td> <td> health compliance</td> <td> To perform one or more operations on information used for conducting activities required to meet a mandate. <br/> </td> </tr> <tr> <td> 5</td> <td> HDECD <a name="v3-ActReason-HDECD"> </a> </td> <td> decedent</td> <td> To perform one or more operations on information used for handling deceased patient matters. <br/> </td> </tr> <tr> <td> 5</td> <td> HDIRECT <a name="v3-ActReason-HDIRECT"> </a> </td> <td> directory</td> <td> To perform one or more operation operations on information used to manage a patient directory. <br/> Examples: <br/> facility enterprise payer health information exchange patient directory </td> </tr> <tr> <td> 5</td> <td> HDM <a name="v3-ActReason-HDM"> </a> </td> <td> healthcare delivery management</td> <td> 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. <br/> 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. <br/> 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." <br/> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> HLEGAL <a name="v3-ActReason-HLEGAL"> </a> </td> <td> legal</td> <td> To perform one or more operations on information for conducting activities required by legal proceeding. <br/> </td> </tr> <tr> <td> 5</td> <td> HOUTCOMS <a name="v3-ActReason-HOUTCOMS"> </a> </td> <td> health outcome measure</td> <td> To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions. <br/> </td> </tr> <tr> <td> 5</td> <td> HPRGRP <a name="v3-ActReason-HPRGRP"> </a> </td> <td> health program reporting</td> <td> To perform one or more operations on information used for conducting activities to meet program accounting requirements. <br/> </td> </tr> <tr> <td> 5</td> <td> HQUALIMP <a name="v3-ActReason-HQUALIMP"> </a> </td> <td> health quality improvement</td> <td> To perform one or more operations on information used for conducting administrative activities to improve health care quality. <br/> </td> </tr> <tr> <td> 5</td> <td> HSYSADMIN <a name="v3-ActReason-HSYSADMIN"> </a> </td> <td> health system administration</td> <td> To perform one or more operations on information to administer the electronic systems used for the delivery of health care. <br/> </td> </tr> <tr> <td> 6</td> <td> LABELING <a name="v3-ActReason-LABELING"> </a> </td> <td> labeling</td> <td> 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. <br/> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> METAMGT <a name="v3-ActReason-METAMGT"> </a> </td> <td> metadata management</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> MEMADMIN <a name="v3-ActReason-MEMADMIN"> </a> </td> <td> member administration</td> <td> To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program. <br/> </td> </tr> <tr> <td> 5</td> <td> MILCDM <a name="v3-ActReason-MILCDM"> </a> </td> <td> military command</td> <td> To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law. <br/> </td> </tr> <tr> <td> 5</td> <td> PATADMIN <a name="v3-ActReason-PATADMIN"> </a> </td> <td> patient administration</td> <td> To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient. <br/> </td> </tr> <tr> <td> 5</td> <td> PATSFTY <a name="v3-ActReason-PATSFTY"> </a> </td> <td> patient safety</td> <td> To perform one or more operations on information in processes related to ensuring the safety of health care. <br/> </td> </tr> <tr> <td> 5</td> <td> PERFMSR <a name="v3-ActReason-PERFMSR"> </a> </td> <td> performance measure</td> <td> To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions. <br/> </td> </tr> <tr> <td> 5</td> <td> RECORDMGT <a name="v3-ActReason-RECORDMGT"> </a> </td> <td> records management</td> <td> To perform one or more operations on information used within the health records management process. <br/> </td> </tr> <tr> <td> 5</td> <td> SYSDEV <a name="v3-ActReason-SYSDEV"> </a> </td> <td> system development</td> <td> To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application. <br/> </td> </tr> <tr> <td> 6</td> <td> HTEST <a name="v3-ActReason-HTEST"> </a> </td> <td> test health data</td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> TRAIN <a name="v3-ActReason-TRAIN"> </a> </td> <td> training</td> <td> To perform one or more operations on information used in training and education. <br/> </td> </tr> <tr> <td> 4</td> <td> HPAYMT <a name="v3-ActReason-HPAYMT"> </a> </td> <td> healthcare payment</td> <td> To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care. <br/> </td> </tr> <tr> <td> 5</td> <td> CLMATTCH <a name="v3-ActReason-CLMATTCH"> </a> </td> <td> claim attachment</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> COVAUTH <a name="v3-ActReason-COVAUTH"> </a> </td> <td> coverage authorization</td> <td> To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services. <br/> </td> </tr> <tr> <td> 5</td> <td> COVERAGE <a name="v3-ActReason-COVERAGE"> </a> </td> <td> coverage under policy or program</td> <td> To perform one or more operations on information for conducting activities related to coverage under a program or policy. <br/> </td> </tr> <tr> <td> 6</td> <td> ELIGDTRM <a name="v3-ActReason-ELIGDTRM"> </a> </td> <td> eligibility determination</td> <td> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> ELIGVER <a name="v3-ActReason-ELIGVER"> </a> </td> <td> eligibility verification</td> <td> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> ENROLLM <a name="v3-ActReason-ENROLLM"> </a> </td> <td> enrollment</td> <td> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> MILDCRG <a name="v3-ActReason-MILDCRG"> </a> </td> <td> military discharge</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> REMITADV <a name="v3-ActReason-REMITADV"> </a> </td> <td> remittance advice</td> <td> To perform one or more operations on information about the amount remitted for a health care claim. <br/> </td> </tr> <tr> <td> 4</td> <td> HRESCH <a name="v3-ActReason-HRESCH"> </a> </td> <td> healthcare research</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> BIORCH <a name="v3-ActReason-BIORCH"> </a> </td> <td> biomedical research</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> CLINTRCH <a name="v3-ActReason-CLINTRCH"> </a> </td> <td> clinical trial research</td> <td> To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge. <br/> </td> </tr> <tr> <td> 6</td> <td> CLINTRCHNPC <a name="v3-ActReason-CLINTRCHNPC"> </a> </td> <td> clinical trial research without patient care</td> <td> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> CLINTRCHPC <a name="v3-ActReason-CLINTRCHPC"> </a> </td> <td> clinical trial research with patient care</td> <td> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> PRECLINTRCH <a name="v3-ActReason-PRECLINTRCH"> </a> </td> <td> preclinical trial research</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> DSRCH <a name="v3-ActReason-DSRCH"> </a> </td> <td> disease specific healthcare research</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> POARCH <a name="v3-ActReason-POARCH"> </a> </td> <td> population origins or ancestry healthcare research</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> TRANSRCH <a name="v3-ActReason-TRANSRCH"> </a> </td> <td> translational healthcare research</td> <td> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> PATRQT <a name="v3-ActReason-PATRQT"> </a> </td> <td> patient requested</td> <td> To perform one or more operations on information in response to a patient's request. <br/> </td> </tr> <tr> <td> 5</td> <td> FAMRQT <a name="v3-ActReason-FAMRQT"> </a> </td> <td> family requested</td> <td> To perform one or more operations on information in response to a request by a family member authorized by the patient. <br/> </td> </tr> <tr> <td> 5</td> <td> PWATRNY <a name="v3-ActReason-PWATRNY"> </a> </td> <td> power of attorney</td> <td> To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative. <br/> </td> </tr> <tr> <td> 5</td> <td> SUPNWK <a name="v3-ActReason-SUPNWK"> </a> </td> <td> support network</td> <td> To perform one or more operations on information in response to a request by a person authorized by the patient. <br/> </td> </tr> <tr> <td> 4</td> <td> PUBHLTH <a name="v3-ActReason-PUBHLTH"> </a> </td> <td> public health</td> <td> To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions. <br/> </td> </tr> <tr> <td> 5</td> <td> DISASTER <a name="v3-ActReason-DISASTER"> </a> </td> <td> disaster</td> <td> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> THREAT <a name="v3-ActReason-THREAT"> </a> </td> <td> threat</td> <td> To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. <br/> </td> </tr> <tr> <td> 4</td> <td> TREAT <a name="v3-ActReason-TREAT"> </a> </td> <td> treatment</td> <td> To perform one or more operations on information for provision of health care. <br/> </td> </tr> <tr> <td> 5</td> <td> CLINTRL <a name="v3-ActReason-CLINTRL"> </a> </td> <td> clinical trial</td> <td> To perform health care as part of the clinical trial protocol. <br/> </td> </tr> <tr> <td> 5</td> <td> COC <a name="v3-ActReason-COC"> </a> </td> <td> coordination of care</td> <td> 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. <br/> 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. <br/> 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. <br/> 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. <br/> 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." <br/> </td> </tr> <tr> <td> 5</td> <td> ETREAT <a name="v3-ActReason-ETREAT"> </a> </td> <td> Emergency Treatment</td> <td> To perform one or more operations on information for provision of immediately needed health care for an emergent condition. <br/> </td> </tr> <tr> <td> 6</td> <td> BTG <a name="v3-ActReason-BTG"> </a> </td> <td> break the glass</td> <td> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 6</td> <td> ERTREAT <a name="v3-ActReason-ERTREAT"> </a> </td> <td> emergency room treatment</td> <td> 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. <br/> 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." <br/> 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. <br/> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> POPHLTH <a name="v3-ActReason-POPHLTH"> </a> </td> <td> population health</td> <td> To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActInformationPrivacyReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActInformationPrivacyReason"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> MARKT <a name="v3-ActReason-MARKT"> </a> </td> <td> marketing</td> <td> Description: <br/> </td> </tr> <tr> <td> 3</td> <td> OPERAT <a name="v3-ActReason-OPERAT"> </a> </td> <td> operations</td> <td> Description:Administrative and contractual processes required to support an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> LEGAL <a name="v3-ActReason-LEGAL"> </a> </td> <td> subpoena</td> <td> Definition:To provide information as a result of a subpoena. <br/> </td> </tr> <tr> <td> 4</td> <td> ACCRED <a name="v3-ActReason-ACCRED"> </a> </td> <td> accreditation</td> <td> Description:Operational activities conducted for the purposes of meeting of criteria defined by an accrediting entity for an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> COMPL <a name="v3-ActReason-COMPL"> </a> </td> <td> compliance</td> <td> Description:Operational activities required to meet a mandate related to an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> ENADMIN <a name="v3-ActReason-ENADMIN"> </a> </td> <td> entity administration</td> <td> Description:Operational activities conducted to administer information relating to entities involves with an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> OUTCOMS <a name="v3-ActReason-OUTCOMS"> </a> </td> <td> outcome measure</td> <td> Description:Operational activities conducted for the purposes of assessing the results of an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> PRGRPT <a name="v3-ActReason-PRGRPT"> </a> </td> <td> program reporting</td> <td> Description:Operational activities conducted to meet program accounting requirements related to an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> QUALIMP <a name="v3-ActReason-QUALIMP"> </a> </td> <td> quality improvement</td> <td> Description:Operational activities conducted for the purposes of improving the quality of an activity, product, or service <br/> </td> </tr> <tr> <td> 4</td> <td> SYSADMN <a name="v3-ActReason-SYSADMN"> </a> </td> <td> system administration</td> <td> Description:Operational activities conducted to administer the electronic systems used for an activity, product, or service <br/> </td> </tr> <tr> <td> 3</td> <td> PAYMT <a name="v3-ActReason-PAYMT"> </a> </td> <td> payment</td> <td> Description:Administrative, financial, and contractual processes related to payment for an activity, product, or service <br/> </td> </tr> <tr> <td> 3</td> <td> RESCH <a name="v3-ActReason-RESCH"> </a> </td> <td> research</td> <td> Description:Investigative activities conducted for the purposes of obtaining knowledge <br/> </td> </tr> <tr> <td> 3</td> <td> SRVC <a name="v3-ActReason-SRVC"> </a> </td> <td> service</td> <td> Description:Provision of a service, product, or capability to an individual or organization <br/> </td> </tr> <tr> <td> 1</td> <td> _ActInvalidReason <a name="v3-ActReason-_ActInvalidReason"> </a> </td> <td> ActInvalidReason</td> <td> Description: Types of reasons why a substance is invalid for use. <br/> </td> </tr> <tr> <td> 2</td> <td> ADVSTORAGE <a name="v3-ActReason-ADVSTORAGE"> </a> </td> <td> adverse storage condition</td> <td> Description: Storage conditions caused the substance to be ineffective. <br/> </td> </tr> <tr> <td> 3</td> <td> COLDCHNBRK <a name="v3-ActReason-COLDCHNBRK"> </a> </td> <td> cold chain break</td> <td> Description: Cold chain was not maintained for the substance. <br/> </td> </tr> <tr> <td> 2</td> <td> EXPLOT <a name="v3-ActReason-EXPLOT"> </a> </td> <td> expired lot</td> <td> Description: The lot from which the substance was drawn was expired. <br/> </td> </tr> <tr> <td> 2</td> <td> OUTSIDESCHED <a name="v3-ActReason-OUTSIDESCHED"> </a> </td> <td> administered outside recommended schedule or practice</td> <td> The substance was administered outside of the recommended schedule or practice. <br/> </td> </tr> <tr> <td> 2</td> <td> PRODRECALL <a name="v3-ActReason-PRODRECALL"> </a> </td> <td> product recall</td> <td> Description: The substance was recalled by the manufacturer. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInvoiceCancelReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActInvoiceCancelReason"> </a> </td> <td> Domain specifies the codes used to describe reasons why a Provider is cancelling an Invoice or Invoice Grouping. <br/> </td> </tr> <tr> <td> 2</td> <td> INCCOVPTY <a name="v3-ActReason-INCCOVPTY"> </a> </td> <td> incorrect covered party as patient</td> <td> The covered party (patient) specified with the Invoice is not correct. <br/> </td> </tr> <tr> <td> 2</td> <td> INCINVOICE <a name="v3-ActReason-INCINVOICE"> </a> </td> <td> incorrect billing</td> <td> The billing information, specified in the Invoice Elements, is not correct. This could include incorrect costing for items included in the Invoice. <br/> </td> </tr> <tr> <td> 2</td> <td> INCPOLICY <a name="v3-ActReason-INCPOLICY"> </a> </td> <td> incorrect policy</td> <td> The policy specified with the Invoice is not correct. For example, it may belong to another Adjudicator or Covered Party. <br/> </td> </tr> <tr> <td> 2</td> <td> INCPROV <a name="v3-ActReason-INCPROV"> </a> </td> <td> incorrect provider</td> <td> The provider specified with the Invoice is not correct. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActNoImmunizationReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActNoImmunizationReason"> </a> </td> <td> A coded description of the reason for why a patient did not receive a scheduled immunization. <br/> (important for public health strategy <br/> </td> </tr> <tr> <td> 2</td> <td> IMMUNE <a name="v3-ActReason-IMMUNE"> </a> </td> <td> immunity</td> <td> Definition:Testing has shown that the patient already has immunity to the agent targeted by the immunization. <br/> </td> </tr> <tr> <td> 2</td> <td> MEDPREC <a name="v3-ActReason-MEDPREC"> </a> </td> <td> medical precaution</td> <td> Definition:The patient currently has a medical condition for which the vaccine is contraindicated or for which precaution is warranted. <br/> </td> </tr> <tr> <td> 2</td> <td> OSTOCK <a name="v3-ActReason-OSTOCK"> </a> </td> <td> product out of stock</td> <td> Definition:There was no supply of the product on hand to perform the service. <br/> </td> </tr> <tr> <td> 2</td> <td> PATOBJ <a name="v3-ActReason-PATOBJ"> </a> </td> <td> patient objection</td> <td> Definition:The patient or their guardian objects to receiving the vaccine. <br/> </td> </tr> <tr> <td> 2</td> <td> PHILISOP <a name="v3-ActReason-PHILISOP"> </a> </td> <td> philosophical objection</td> <td> Definition:The patient or their guardian objects to receiving the vaccine because of philosophical beliefs. <br/> </td> </tr> <tr> <td> 2</td> <td> RELIG <a name="v3-ActReason-RELIG"> </a> </td> <td> religious objection</td> <td> Definition:The patient or their guardian objects to receiving the vaccine on religious grounds. <br/> </td> </tr> <tr> <td> 2</td> <td> VACEFF <a name="v3-ActReason-VACEFF"> </a> </td> <td> vaccine efficacy concerns</td> <td> Definition:The intended vaccine has expired or is otherwise believed to no longer be effective. <br/> Example:Due to temperature exposure. <br/> </td> </tr> <tr> <td> 2</td> <td> VACSAF <a name="v3-ActReason-VACSAF"> </a> </td> <td> vaccine safety concerns</td> <td> Definition:The patient or their guardian objects to receiving the vaccine because of concerns over its safety. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActSupplyFulfillmentRefusalReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActSupplyFulfillmentRefusalReason"> </a> </td> <td> 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". <br/> (used when capturing 'refusal to fill' annotations) <br/> </td> </tr> <tr> <td> 2</td> <td> FRR01 <a name="v3-ActReason-FRR01"> </a> </td> <td> order stopped</td> <td> Definition:The order has been stopped by the prescriber but this fact has not necessarily captured electronically. <br/> Example:A verbal stop, a fax, etc. <br/> </td> </tr> <tr> <td> 2</td> <td> FRR02 <a name="v3-ActReason-FRR02"> </a> </td> <td> stale-dated order</td> <td> Definition:Order has not been fulfilled within a reasonable amount of time, and may not be current. <br/> </td> </tr> <tr> <td> 2</td> <td> FRR03 <a name="v3-ActReason-FRR03"> </a> </td> <td> incomplete data</td> <td> Definition:Data needed to safely act on the order which was expected to become available independent of the order is not yet available <br/> Example:Lab results, diagnostic imaging, etc. <br/> </td> </tr> <tr> <td> 2</td> <td> FRR04 <a name="v3-ActReason-FRR04"> </a> </td> <td> product unavailable</td> <td> Definition:Product not available or manufactured. Cannot supply. <br/> </td> </tr> <tr> <td> 2</td> <td> FRR05 <a name="v3-ActReason-FRR05"> </a> </td> <td> ethical/religious</td> <td> Definition:The dispenser has ethical, religious or moral objections to fulfilling the order/dispensing the product. <br/> </td> </tr> <tr> <td> 2</td> <td> FRR06 <a name="v3-ActReason-FRR06"> </a> </td> <td> unable to provide care</td> <td> Definition:Fulfiller not able to provide appropriate care associated with fulfilling the order. <br/> Example:Therapy requires ongoing monitoring by fulfiller and fulfiller will be ending practice, leaving town, unable to schedule necessary time, etc. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ClinicalResearchEventReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ClinicalResearchEventReason"> </a> </td> <td> Definition:Specifies the reason that an event occurred in a clinical research study. <br/> </td> </tr> <tr> <td> 2</td> <td> RET <a name="v3-ActReason-RET"> </a> </td> <td> retest</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SCH <a name="v3-ActReason-SCH"> </a> </td> <td> scheduled</td> <td> Definition:The event occurred due to it being scheduled in the research protocol. <br/> </td> </tr> <tr> <td> 2</td> <td> TRM <a name="v3-ActReason-TRM"> </a> </td> <td> termination</td> <td> Definition:The event occurred in order to terminate the subject's participation in the study. <br/> </td> </tr> <tr> <td> 2</td> <td> UNS <a name="v3-ActReason-UNS"> </a> </td> <td> unscheduled</td> <td> 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. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ClinicalResearchObservationReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ClinicalResearchObservationReason"> </a> </td> <td> Definition:SSpecifies the reason that a test was performed or observation collected in a clinical research study. <br/> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> NPT <a name="v3-ActReason-NPT"> </a> </td> <td> non-protocol</td> <td> Definition:The observation or test was neither defined or scheduled in the study protocol. <br/> </td> </tr> <tr> <td> 2</td> <td> PPT <a name="v3-ActReason-PPT"> </a> </td> <td> per protocol</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> UPT <a name="v3-ActReason-UPT"> </a> </td> <td> per definition</td> <td> :The observation or test occurred as defined in the research protocol, but at a point in time not specified in the study protocol. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_CombinedPharmacyOrderSuspendReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_CombinedPharmacyOrderSuspendReasonCode"> </a> </td> <td> Description:Indicates why the prescription should be suspended. <br/> </td> </tr> <tr> <td> 2</td> <td> ALTCHOICE <a name="v3-ActReason-ALTCHOICE"> </a> </td> <td> try another treatment first</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> CLARIF <a name="v3-ActReason-CLARIF"> </a> </td> <td> prescription requires clarification</td> <td> Description:Clarification is required before the order can be acted upon. <br/> </td> </tr> <tr> <td> 2</td> <td> DRUGHIGH <a name="v3-ActReason-DRUGHIGH"> </a> </td> <td> drug level too high</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> HOSPADM <a name="v3-ActReason-HOSPADM"> </a> </td> <td> admission to hospital</td> <td> Description:The patient has been admitted to a care facility and their community medications are suspended until hospital discharge. <br/> </td> </tr> <tr> <td> 2</td> <td> LABINT <a name="v3-ActReason-LABINT"> </a> </td> <td> lab interference issues</td> <td> Description:The therapy would interfere with a planned lab test and the therapy is being withdrawn until the test is completed. <br/> </td> </tr> <tr> <td> 2</td> <td> NON-AVAIL <a name="v3-ActReason-NON-AVAIL"> </a> </td> <td> patient not-available</td> <td> Description:Patient not available for a period of time due to a scheduled therapy, leave of absence or other reason. <br/> </td> </tr> <tr> <td> 2</td> <td> PREG <a name="v3-ActReason-PREG"> </a> </td> <td> parent is pregnant/breast feeding</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SALG <a name="v3-ActReason-SALG"> </a> </td> <td> allergy</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SDDI <a name="v3-ActReason-SDDI"> </a> </td> <td> drug interacts with another drug</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SDUPTHER <a name="v3-ActReason-SDUPTHER"> </a> </td> <td> duplicate therapy</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SINTOL <a name="v3-ActReason-SINTOL"> </a> </td> <td> suspected intolerance</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> SURG <a name="v3-ActReason-SURG"> </a> </td> <td> patient scheduled for surgery</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> WASHOUT <a name="v3-ActReason-WASHOUT"> </a> </td> <td> waiting for old drug to wash out</td> <td> 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. <br/> </td> </tr> <tr> <td> 1</td> <td> _ControlActNullificationReasonCode <a name="v3-ActReason-_ControlActNullificationReasonCode"> </a> </td> <td> ControlActNullificationReasonCode</td> <td> Description:Identifies reasons for nullifying (retracting) a particular control act. <br/> </td> </tr> <tr> <td> 2</td> <td> ALTD <a name="v3-ActReason-ALTD"> </a> </td> <td> altered decision</td> <td> Description:The decision on which the recorded information was based was changed before the decision had an effect. <br/> Example:Aborted prescription before patient left office, released prescription before suspend took effect. <br/> </td> </tr> <tr> <td> 2</td> <td> EIE <a name="v3-ActReason-EIE"> </a> </td> <td> entered in error</td> <td> Description:The information was recorded incorrectly or was recorded in the wrong record. <br/> </td> </tr> <tr> <td> 2</td> <td> NORECMTCH <a name="v3-ActReason-NORECMTCH"> </a> </td> <td> no record match</td> <td> Description: There is no match for the record in the database. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ControlActNullificationRefusalReasonType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ControlActNullificationRefusalReasonType"> </a> </td> <td> Description: Reasons to refuse a transaction to be undone. <br/> </td> </tr> <tr> <td> 2</td> <td> INRQSTATE <a name="v3-ActReason-INRQSTATE"> </a> </td> <td> in requested state</td> <td> The record is already in the requested state. <br/> </td> </tr> <tr> <td> 2</td> <td> NOMATCH <a name="v3-ActReason-NOMATCH"> </a> </td> <td> no match</td> <td> Description: There is no match. <br/> </td> </tr> <tr> <td> 3</td> <td> <a href="#NORECMTCH">NORECMTCH</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td> NOPRODMTCH <a name="v3-ActReason-NOPRODMTCH"> </a> </td> <td> no product match</td> <td> Description: There is no match for the product in the master file repository. <br/> </td> </tr> <tr> <td> 3</td> <td> NOSERMTCH <a name="v3-ActReason-NOSERMTCH"> </a> </td> <td> no service match</td> <td> Description: There is no match for the service in the master file repository. <br/> </td> </tr> <tr> <td> 3</td> <td> NOVERMTCH <a name="v3-ActReason-NOVERMTCH"> </a> </td> <td> no version match</td> <td> Description: There is no match for the record and version. <br/> </td> </tr> <tr> <td> 2</td> <td> NOPERM <a name="v3-ActReason-NOPERM"> </a> </td> <td> no permission</td> <td> Description: There is no permission. <br/> </td> </tr> <tr> <td> 3</td> <td> NOUSERPERM <a name="v3-ActReason-NOUSERPERM"> </a> </td> <td> no user permission</td> <td> Definition:The user does not have permission <br/> </td> </tr> <tr> <td> 3</td> <td> NOAGNTPERM <a name="v3-ActReason-NOAGNTPERM"> </a> </td> <td> no agent permission</td> <td> Description: The agent does not have permission. <br/> </td> </tr> <tr> <td> 3</td> <td> NOUSRPERM <a name="v3-ActReason-NOUSRPERM"> </a> </td> <td> no user permission</td> <td> Description: The user does not have permission. <br/> </td> </tr> <tr> <td> 2</td> <td> WRNGVER <a name="v3-ActReason-WRNGVER"> </a> </td> <td> wrong version</td> <td> Description: The record and version requested to update is not the current version. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ControlActReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ControlActReason"> </a> </td> <td> Identifies why a specific query, request, or other trigger event occurred. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_MedicationOrderAbortReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_MedicationOrderAbortReasonCode"> </a> </td> <td> Description:Indicates the reason the medication order should be aborted. <br/> </td> </tr> <tr> <td> 3</td> <td> DISCONT <a name="v3-ActReason-DISCONT"> </a> </td> <td> product discontinued</td> <td> Description:The medication is no longer being manufactured or is otherwise no longer available. <br/> </td> </tr> <tr> <td> 3</td> <td> INEFFECT <a name="v3-ActReason-INEFFECT"> </a> </td> <td> ineffective</td> <td> Description:The therapy has been found to not have the desired therapeutic benefit on the patient. <br/> </td> </tr> <tr> <td> 3</td> <td> MONIT <a name="v3-ActReason-MONIT"> </a> </td> <td> response to monitoring</td> <td> Description:Monitoring the patient while taking the medication, the decision has been made that the therapy is no longer appropriate. <br/> </td> </tr> <tr> <td> 3</td> <td> NOREQ <a name="v3-ActReason-NOREQ"> </a> </td> <td> no longer required for treatment</td> <td> Description:The underlying condition has been resolved or has evolved such that a different treatment is no longer needed. <br/> </td> </tr> <tr> <td> 3</td> <td> NOTCOVER <a name="v3-ActReason-NOTCOVER"> </a> </td> <td> not covered</td> <td> Description:The product does not have (or no longer has) coverage under the patientaTMs insurance policy. <br/> </td> </tr> <tr> <td> 3</td> <td> PREFUS <a name="v3-ActReason-PREFUS"> </a> </td> <td> patient refuse</td> <td> Description:The patient refused to take the product. <br/> </td> </tr> <tr> <td> 3</td> <td> RECALL <a name="v3-ActReason-RECALL"> </a> </td> <td> product recalled</td> <td> Description:The manufacturer or other agency has requested that stocks of a medication be removed from circulation. <br/> </td> </tr> <tr> <td> 3</td> <td> REPLACE <a name="v3-ActReason-REPLACE"> </a> </td> <td> change in order</td> <td> Description:Item in current order is no longer in use as requested and a new one has/will be created to replace it. <br/> </td> </tr> <tr> <td> 4</td> <td> DOSECHG <a name="v3-ActReason-DOSECHG"> </a> </td> <td> change in medication/dose</td> <td> Description:The medication is being re-prescribed at a different dosage. <br/> </td> </tr> <tr> <td> 3</td> <td> REPLACEFIX <a name="v3-ActReason-REPLACEFIX"> </a> </td> <td> error in order</td> <td> Description:Current order was issued with incorrect data and a new order has/will be created to replace it. <br/> </td> </tr> <tr> <td> 3</td> <td> UNABLE <a name="v3-ActReason-UNABLE"> </a> </td> <td> unable to use</td> <td> Description:<The patient is not (or is no longer) able to use the medication in a manner prescribed. <br/> Example:CanaTMt swallow. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_MedicationOrderReleaseReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_MedicationOrderReleaseReasonCode"> </a> </td> <td> Definition:A collection of concepts that indicate why the prescription should be released from suspended state. <br/> </td> </tr> <tr> <td> 3</td> <td> HOLDDONE <a name="v3-ActReason-HOLDDONE"> </a> </td> <td> suspend reason no longer applies</td> <td> Definition:The original reason for suspending the medication has ended. <br/> </td> </tr> <tr> <td> 3</td> <td> HOLDINAP <a name="v3-ActReason-HOLDINAP"> </a> </td> <td> suspend reason inappropriate</td> <td> Definition: <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ModifyPrescriptionReasonType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ModifyPrescriptionReasonType"> </a> </td> <td> Types of reason why a prescription is being changed. <br/> </td> </tr> <tr> <td> 3</td> <td> ADMINERROR <a name="v3-ActReason-ADMINERROR"> </a> </td> <td> administrative error in order</td> <td> Order was created with incorrect data and is changed to reflect the intended accuracy of the order. <br/> </td> </tr> <tr> <td> 3</td> <td> CLINMOD <a name="v3-ActReason-CLINMOD"> </a> </td> <td> clinical modification</td> <td> Order is changed based on a clinical reason. <br/> </td> </tr> <tr> <td> 2</td> <td> _PharmacySupplyEventAbortReason <a name="v3-ActReason-_PharmacySupplyEventAbortReason"> </a> </td> <td> PharmacySupplyEventAbortReason</td> <td> Definition:Identifies why the dispense event was not completed. <br/> </td> </tr> <tr> <td> 3</td> <td> CONTRA <a name="v3-ActReason-CONTRA"> </a> </td> <td> contraindication</td> <td> Definition:Contraindication identified <br/> </td> </tr> <tr> <td> 3</td> <td> FOABORT <a name="v3-ActReason-FOABORT"> </a> </td> <td> order aborted</td> <td> Definition:Order to be fulfilled was aborted <br/> </td> </tr> <tr> <td> 3</td> <td> FOSUSP <a name="v3-ActReason-FOSUSP"> </a> </td> <td> order suspended</td> <td> Definition:Order to be fulfilled was suspended <br/> </td> </tr> <tr> <td> 3</td> <td> NOPICK <a name="v3-ActReason-NOPICK"> </a> </td> <td> not picked up</td> <td> Definition:Patient did not come to get medication <br/> </td> </tr> <tr> <td> 3</td> <td> PATDEC <a name="v3-ActReason-PATDEC"> </a> </td> <td> patient changed mind</td> <td> Definition:Patient changed their mind regarding obtaining medication <br/> </td> </tr> <tr> <td> 3</td> <td> QUANTCHG <a name="v3-ActReason-QUANTCHG"> </a> </td> <td> change supply quantity</td> <td> Definition:Patient requested a revised quantity of medication <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_PharmacySupplyEventStockReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_PharmacySupplyEventStockReasonCode"> </a> </td> <td> Definition:A collection of concepts that indicates the reason for a "bulk supply" of medication. <br/> </td> </tr> <tr> <td> 3</td> <td> FLRSTCK <a name="v3-ActReason-FLRSTCK"> </a> </td> <td> floor stock</td> <td> Definition:The bulk supply is issued to replenish a ward for local dispensing. (Includes both mobile and fixed-location ward stocks.) <br/> </td> </tr> <tr> <td> 3</td> <td> LTC <a name="v3-ActReason-LTC"> </a> </td> <td> long term care use</td> <td> Definition:The bulk supply will be administered within a long term care facility. <br/> </td> </tr> <tr> <td> 3</td> <td> OFFICE <a name="v3-ActReason-OFFICE"> </a> </td> <td> office use</td> <td> Definition:The bulk supply is intended for general clinician office use. <br/> </td> </tr> <tr> <td> 3</td> <td> PHARM <a name="v3-ActReason-PHARM"> </a> </td> <td> pharmacy transfer</td> <td> Definition:The bulk supply is being transferred to another dispensing facility to. <br/> Example:Alleviate a temporary shortage. <br/> </td> </tr> <tr> <td> 3</td> <td> PROG <a name="v3-ActReason-PROG"> </a> </td> <td> program use</td> <td> Definition:The bulk supply is intended for dispensing according to a specific program. <br/> Example:Mass immunization. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_PharmacySupplyRequestRenewalRefusalReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_PharmacySupplyRequestRenewalRefusalReasonCode"> </a> </td> <td> Definition:A collection of concepts that identifies why a renewal prescription has been refused. <br/> </td> </tr> <tr> <td> 3</td> <td> <a href="#DISCONT">DISCONT</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td> ALREADYRX <a name="v3-ActReason-ALREADYRX"> </a> </td> <td> new prescription exists</td> <td> Definition:Patient has already been given a new (renewal) prescription. <br/> </td> </tr> <tr> <td> 3</td> <td> FAMPHYS <a name="v3-ActReason-FAMPHYS"> </a> </td> <td> family physician must authorize further fills</td> <td> Definition:Request for further authorization must be done through patient's family physician. <br/> </td> </tr> <tr> <td> 3</td> <td> MODIFY <a name="v3-ActReason-MODIFY"> </a> </td> <td> modified prescription exists</td> <td> Definition:Therapy has been changed and new prescription issued <br/> </td> </tr> <tr> <td> 3</td> <td> NEEDAPMT <a name="v3-ActReason-NEEDAPMT"> </a> </td> <td> patient must make appointment</td> <td> Definition:Patient must see prescriber prior to further fills. <br/> </td> </tr> <tr> <td> 3</td> <td> NOTAVAIL <a name="v3-ActReason-NOTAVAIL"> </a> </td> <td> prescriber not available</td> <td> Definition:Original prescriber is no longer available to prescribe and no other prescriber has taken responsibility for the patient. <br/> </td> </tr> <tr> <td> 3</td> <td> NOTPAT <a name="v3-ActReason-NOTPAT"> </a> </td> <td> patient no longer in this practice</td> <td> Definition:Patient no longer or has never been under this prescribers care. <br/> </td> </tr> <tr> <td> 3</td> <td> ONHOLD <a name="v3-ActReason-ONHOLD"> </a> </td> <td> medication on hold</td> <td> Definition:This medication is on hold. <br/> </td> </tr> <tr> <td> 3</td> <td> PRNA <a name="v3-ActReason-PRNA"> </a> </td> <td> product not available</td> <td> Description:This product is not available or manufactured. <br/> </td> </tr> <tr> <td> 3</td> <td> STOPMED <a name="v3-ActReason-STOPMED"> </a> </td> <td> prescriber stopped medication for patient</td> <td> Renewing or original prescriber informed patient to stop using the medication. <br/> </td> </tr> <tr> <td> 3</td> <td> TOOEARLY <a name="v3-ActReason-TOOEARLY"> </a> </td> <td> too early</td> <td> Definition:The patient should have medication remaining. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_SupplyOrderAbortReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_SupplyOrderAbortReasonCode"> </a> </td> <td> 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). <br/> </td> </tr> <tr> <td> 3</td> <td> IMPROV <a name="v3-ActReason-IMPROV"> </a> </td> <td> condition improved</td> <td> Definition:The patient's medical condition has nearly abated. <br/> </td> </tr> <tr> <td> 3</td> <td> INTOL <a name="v3-ActReason-INTOL"> </a> </td> <td> intolerance</td> <td> Description:The patient has an intolerance to the medication. <br/> </td> </tr> <tr> <td> 3</td> <td> NEWSTR <a name="v3-ActReason-NEWSTR"> </a> </td> <td> new strength</td> <td> Definition:The current medication will be replaced by a new strength of the same medication. <br/> </td> </tr> <tr> <td> 3</td> <td> NEWTHER <a name="v3-ActReason-NEWTHER"> </a> </td> <td> new therapy</td> <td> Definition:A new therapy will be commenced when current supply exhausted. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_GenericUpdateReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_GenericUpdateReasonCode"> </a> </td> <td> Description:Identifies why a change is being made to a record. <br/> </td> </tr> <tr> <td> 2</td> <td> CHGDATA <a name="v3-ActReason-CHGDATA"> </a> </td> <td> information change</td> <td> Description:Information has changed since the record was created. <br/> </td> </tr> <tr> <td> 2</td> <td> FIXDATA <a name="v3-ActReason-FIXDATA"> </a> </td> <td> error correction</td> <td> Description:Previously recorded information was erroneous and is being corrected. <br/> </td> </tr> <tr> <td> 2</td> <td> MDATA <a name="v3-ActReason-MDATA"> </a> </td> <td> merge data</td> <td> Information is combined into the record. <br/> </td> </tr> <tr> <td> 2</td> <td> NEWDATA <a name="v3-ActReason-NEWDATA"> </a> </td> <td> new information</td> <td> Description:New information has become available to supplement the record. <br/> </td> </tr> <tr> <td> 2</td> <td> UMDATA <a name="v3-ActReason-UMDATA"> </a> </td> <td> unmerge data</td> <td> Information is separated from the record. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_PatientProfileQueryReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_PatientProfileQueryReasonCode"> </a> </td> <td> Definition:A collection of concepts identifying why the patient's profile is being queried. <br/> </td> </tr> <tr> <td> 2</td> <td> ADMREV <a name="v3-ActReason-ADMREV"> </a> </td> <td> administrative review</td> <td> Definition: To evaluate for service authorization, payment, reporting, or performance/outcome measures. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#LEGAL">LEGAL</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> PATCAR <a name="v3-ActReason-PATCAR"> </a> </td> <td> patient care</td> <td> Definition:To obtain records as part of patient care. <br/> </td> </tr> <tr> <td> 2</td> <td> PATREQ <a name="v3-ActReason-PATREQ"> </a> </td> <td> patient request query</td> <td> Definition:Patient requests information from their profile. <br/> </td> </tr> <tr> <td> 2</td> <td> PRCREV <a name="v3-ActReason-PRCREV"> </a> </td> <td> practice review</td> <td> Definition:To evaluate the provider's current practice for professional-improvement reasons. <br/> </td> </tr> <tr> <td> 2</td> <td> REGUL <a name="v3-ActReason-REGUL"> </a> </td> <td> regulatory review</td> <td> Description:Review for the purpose of regulatory compliance. <br/> </td> </tr> <tr> <td> 2</td> <td> RSRCH <a name="v3-ActReason-RSRCH"> </a> </td> <td> research</td> <td> Definition:To provide research data, as authorized by the patient. <br/> </td> </tr> <tr> <td> 2</td> <td> VALIDATION <a name="v3-ActReason-VALIDATION"> </a> </td> <td> validation review</td> <td> Description:To validate the patient's record. <br/> Example:Merging or unmerging records. <br/> </td> </tr> <tr> <td> 1</td> <td> _PharmacySupplyRequestFulfillerRevisionRefusalReasonCode <a name="v3-ActReason-_PharmacySupplyRequestFulfillerRevisionRefusalReasonCode"> </a> </td> <td> PharmacySupplyRequestFulfillerRevisionRefusalReasonCode</td> <td> Definition:Indicates why the request to transfer a prescription from one dispensing facility to another has been refused. <br/> </td> </tr> <tr> <td> 2</td> <td> LOCKED <a name="v3-ActReason-LOCKED"> </a> </td> <td> locked</td> <td> Definition:The prescription may not be reassigned from the original pharmacy. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#NOUSERPERM">NOUSERPERM</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> UNKWNTARGET <a name="v3-ActReason-UNKWNTARGET"> </a> </td> <td> unknown target</td> <td> Definition:The target facility does not recognize the dispensing facility. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_RefusalReasonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_RefusalReasonCode"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#NOMATCH">NOMATCH</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> <a href="#NOPERM">NOPERM</a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_SchedulingActReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_SchedulingActReason"> </a> </td> <td> Reasons for cancelling or rescheduling an Appointment <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#PAT">PAT</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> BLK <a name="v3-ActReason-BLK"> </a> </td> <td> Unexpected Block (of Schedule)</td> <td> The time slots previously allocated are now blocked and no longer available for booking Appointments <br/> </td> </tr> <tr> <td> 2</td> <td> DEC <a name="v3-ActReason-DEC"> </a> </td> <td> Patient Deceased</td> <td> The Patient is deceased <br/> </td> </tr> <tr> <td> 2</td> <td> FIN <a name="v3-ActReason-FIN"> </a> </td> <td> No Financial Backing</td> <td> Patient unable to pay and not covered by insurance <br/> </td> </tr> <tr> <td> 2</td> <td> MED <a name="v3-ActReason-MED"> </a> </td> <td> Medical Status Altered</td> <td> The medical condition of the Patient has changed <br/> </td> </tr> <tr> <td> 2</td> <td> MTG <a name="v3-ActReason-MTG"> </a> </td> <td> In an outside meeting</td> <td> The Physician is in a meeting. For example, he/she may request administrative time to talk to family after appointment <br/> </td> </tr> <tr> <td> 2</td> <td> PHY <a name="v3-ActReason-PHY"> </a> </td> <td> Physician request</td> <td> The Physician requested the action <br/> </td> </tr> <tr> <td> 1</td> <td> _StatusRevisionRefusalReasonCode <a name="v3-ActReason-_StatusRevisionRefusalReasonCode"> </a> </td> <td> StatusRevisionRefusalReasonCode</td> <td> Indicates why the act revision (status update) is being refused. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#NORECMTCH">NORECMTCH</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> <a href="#INRQSTATE">INRQSTATE</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> <a href="#NOUSERPERM">NOUSERPERM</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> FILLED <a name="v3-ActReason-FILLED"> </a> </td> <td> fully filled</td> <td> Ordered quantity has already been completely fulfilled. <br/> </td> </tr> <tr> <td> 1</td> <td> _SubstanceAdministrationPermissionRefusalReasonCode <a name="v3-ActReason-_SubstanceAdministrationPermissionRefusalReasonCode"> </a> </td> <td> SubstanceAdministrationPermissionRefusalReasonCode</td> <td> Definition:Indicates why the requested authorization to prescribe or dispense a medication has been refused. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#NOUSERPERM">NOUSERPERM</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> PATINELIG <a name="v3-ActReason-PATINELIG"> </a> </td> <td> patient not eligible</td> <td> Definition:Patient not eligible for drug <br/> </td> </tr> <tr> <td> 2</td> <td> PROTUNMET <a name="v3-ActReason-PROTUNMET"> </a> </td> <td> protocol not met</td> <td> Definition:Patient does not meet required protocol <br/> </td> </tr> <tr> <td> 2</td> <td> PROVUNAUTH <a name="v3-ActReason-PROVUNAUTH"> </a> </td> <td> provider not authorized</td> <td> Definition:Provider is not authorized to prescribe or dispense <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_SubstanceAdminSubstitutionNotAllowedReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_SubstanceAdminSubstitutionNotAllowedReason"> </a> </td> <td> Reasons why substitution of a substance administration request is not permitted. <br/> </td> </tr> <tr> <td> 2</td> <td> <a href="#PAT">PAT</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td> ALGINT <a name="v3-ActReason-ALGINT"> </a> </td> <td> allergy intolerance</td> <td> Definition: Patient has had a prior allergic intolerance response to alternate product or one of its components. <br/> </td> </tr> <tr> <td> 2</td> <td> COMPCON <a name="v3-ActReason-COMPCON"> </a> </td> <td> compliance concern</td> <td> Definition: Patient has compliance issues with medication such as differing appearance, flavor, size, shape or consistency. <br/> </td> </tr> <tr> <td> 2</td> <td> THERCHAR <a name="v3-ActReason-THERCHAR"> </a> </td> <td> therapeutic characteristics</td> <td> The prescribed product has specific clinical release or other therapeutic characteristics not shared by other substitutable medications. <br/> </td> </tr> <tr> <td> 2</td> <td> TRIAL <a name="v3-ActReason-TRIAL"> </a> </td> <td> clinical trial drug</td> <td> Definition: The specific manufactured drug is part of a clinical trial. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_SubstanceAdminSubstitutionReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_SubstanceAdminSubstitutionReason"> </a> </td> <td/> </tr> <tr> <td> 2</td> <td> CT <a name="v3-ActReason-CT"> </a> </td> <td> continuing therapy</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> FP <a name="v3-ActReason-FP"> </a> </td> <td> formulary policy</td> <td> Indicates that the decision to substitute or to not substitute was driven by a policy expressed within the formulary. <br/> </td> </tr> <tr> <td> 2</td> <td> OS <a name="v3-ActReason-OS"> </a> </td> <td> out of stock</td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> RR <a name="v3-ActReason-RR"> </a> </td> <td> regulatory requirement</td> <td> Indicates that the decision to substitute or to not substitute was driven by a jurisdictional regulatory requirement mandating or prohibiting substitution. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_TransferActReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_TransferActReason"> </a> </td> <td> The explanation for why a patient is moved from one location to another within the organization <br/> </td> </tr> <tr> <td> 2</td> <td> ER <a name="v3-ActReason-ER"> </a> </td> <td> Error</td> <td> Moved to an error in placing the patient in the original location. <br/> </td> </tr> <tr> <td> 2</td> <td> RQ <a name="v3-ActReason-RQ"> </a> </td> <td> Request</td> <td> Moved at the request of the patient. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActBillableServiceReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActBillableServiceReason"> </a> </td> <td> Definition: This domain is used to document reasons for providing a billable service; the billable services may include both clinical services and social services. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActBillableClinicalServiceReason)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActReason-_ActBillableClinicalServiceReason"> </a> </td> <td> Reason for Clinical Service being performed. <br/> This domain excludes reasons specified by diagnosed conditions. <br/> Examples of values from this domain include duplicate therapy and fraudulent prescription. <br/> </td> </tr> <tr> <td> 1</td> <td> BONUS <a name="v3-ActReason-BONUS"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> CHD <a name="v3-ActReason-CHD"> </a> </td> <td> Children only</td> <td> Description:The level of coverage under the policy or program is available only to children <br/> </td> </tr> <tr> <td> 1</td> <td> DEP <a name="v3-ActReason-DEP"> </a> </td> <td> Dependents only</td> <td> Description:The level of coverage under the policy or program is available only to a subscriber's dependents. <br/> </td> </tr> <tr> <td> 1</td> <td> ECH <a name="v3-ActReason-ECH"> </a> </td> <td> Employee and children</td> <td> Description:The level of coverage under the policy or program is available to an employee and his or her children. <br/> </td> </tr> <tr> <td> 1</td> <td> EDU <a name="v3-ActReason-EDU"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> EMP <a name="v3-ActReason-EMP"> </a> </td> <td> Employee only</td> <td> Description:The level of coverage under the policy or program is available only to an employee. <br/> </td> </tr> <tr> <td> 1</td> <td> ESP <a name="v3-ActReason-ESP"> </a> </td> <td> Employee and spouse</td> <td> Description:The level of coverage under the policy or program is available to an employee and his or her spouse. <br/> </td> </tr> <tr> <td> 1</td> <td> FAM <a name="v3-ActReason-FAM"> </a> </td> <td> Family</td> <td> Description:The level of coverage under the policy or program is available to a subscriber's family. <br/> </td> </tr> <tr> <td> 1</td> <td> IND <a name="v3-ActReason-IND"> </a> </td> <td> Individual</td> <td> Description:The level of coverage under the policy or program is available to an individual. <br/> </td> </tr> <tr> <td> 1</td> <td> INVOICE <a name="v3-ActReason-INVOICE"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> PROA <a name="v3-ActReason-PROA"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> RECOV <a name="v3-ActReason-RECOV"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> RETRO <a name="v3-ActReason-RETRO"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> SPC <a name="v3-ActReason-SPC"> </a> </td> <td> Spouse and children</td> <td> Description:The level of coverage under the policy or program is available to a subscriber's spouse and children <br/> </td> </tr> <tr> <td> 1</td> <td> SPO <a name="v3-ActReason-SPO"> </a> </td> <td> Spouse only</td> <td> Description:The level of coverage under the policy or program is available only to a subscribers spouse <br/> </td> </tr> <tr> <td> 1</td> <td> TRAN <a name="v3-ActReason-TRAN"> </a> </td> <td/> <td/> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="draft"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="vocab"/> </extension> <url value="http://terminology.hl7.org/ValueSet/v3-ActReason"/> <version value="2019-07-31"/> <name value="v3.ActReason"/> <title value="v3 Code System ActReason"/> <status value="active"/> <experimental value="false"/> <date value="2019-07-31"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> </contact> <description value=" 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"."/> <immutable value="true"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActReason"/> </include> </compose> </ValueSet>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
FHIR ®© HL7.org 2011+. FHIR CI Build hl7.fhir.core#4.4.0 generated on Sun, May 3, 2020 08:48+1000.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change