Release 5 Preview #1
TerminologyThis page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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 code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted.
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="v3-ActCode"/> <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> (_ActAccountCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAccountCode"> </a> </td> <td> An account represents a grouping of financial transactions that are tracked and reported together with a single balance. Examples of account codes (types) are Patient billing accounts (collection of charges), Cost centers; Cash. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACCTRECEIVABLE <a name="v3-ActCode-ACCTRECEIVABLE"> </a> </td> <td> account receivable</td> <td> An account for collecting charges, reversals, adjustments and payments, including deductibles, copayments, coinsurance (financial transactions) credited or debited to the account receivable account for a patient's encounter. <br/> </td> </tr> <tr> <td> 2</td> <td>   CASH <a name="v3-ActCode-CASH"> </a> </td> <td> Cash</td> <td/> </tr> <tr> <td> 2</td> <td>   CC <a name="v3-ActCode-CC"> </a> </td> <td> credit card</td> <td> Description: Types of advance payment to be made on a plastic card usually issued by a financial institution used of purchasing services and/or products. <br/> </td> </tr> <tr> <td> 3</td> <td>     AE <a name="v3-ActCode-AE"> </a> </td> <td> American Express</td> <td/> </tr> <tr> <td> 3</td> <td>     DN <a name="v3-ActCode-DN"> </a> </td> <td> Diner's Club</td> <td/> </tr> <tr> <td> 3</td> <td>     DV <a name="v3-ActCode-DV"> </a> </td> <td> Discover Card</td> <td/> </tr> <tr> <td> 3</td> <td>     MC <a name="v3-ActCode-MC"> </a> </td> <td> Master Card</td> <td/> </tr> <tr> <td> 3</td> <td>     V <a name="v3-ActCode-V"> </a> </td> <td> Visa</td> <td/> </tr> <tr> <td> 2</td> <td>   PBILLACCT <a name="v3-ActCode-PBILLACCT"> </a> </td> <td> patient billing account</td> <td> An account representing charges and credits (financial transactions) for a patient's encounter. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActAdjudicationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdjudicationCode"> </a> </td> <td> Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActAdjudicationGroupCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdjudicationGroupCode"> </a> </td> <td> Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals). <br/> </td> </tr> <tr> <td> 3</td> <td>     CONT <a name="v3-ActCode-CONT"> </a> </td> <td> contract</td> <td> Transaction counts and value totals by Contract Identifier. <br/> </td> </tr> <tr> <td> 3</td> <td>     DAY <a name="v3-ActCode-DAY"> </a> </td> <td> day</td> <td> Transaction counts and value totals for each calendar day within the date range specified. <br/> </td> </tr> <tr> <td> 3</td> <td>     LOC <a name="v3-ActCode-LOC"> </a> </td> <td> location</td> <td> Transaction counts and value totals by service location (e.g clinic). <br/> </td> </tr> <tr> <td> 3</td> <td>     MONTH <a name="v3-ActCode-MONTH"> </a> </td> <td> month</td> <td> Transaction counts and value totals for each calendar month within the date range specified. <br/> </td> </tr> <tr> <td> 3</td> <td>     PERIOD <a name="v3-ActCode-PERIOD"> </a> </td> <td> period</td> <td> Transaction counts and value totals for the date range specified. <br/> </td> </tr> <tr> <td> 3</td> <td>     PROV <a name="v3-ActCode-PROV"> </a> </td> <td> provider</td> <td> Transaction counts and value totals by Provider Identifier. <br/> </td> </tr> <tr> <td> 3</td> <td>     WEEK <a name="v3-ActCode-WEEK"> </a> </td> <td> week</td> <td> Transaction counts and value totals for each calendar week within the date range specified. <br/> </td> </tr> <tr> <td> 3</td> <td>     YEAR <a name="v3-ActCode-YEAR"> </a> </td> <td> year</td> <td> Transaction counts and value totals for each calendar year within the date range specified. <br/> </td> </tr> <tr> <td> 2</td> <td>   AA <a name="v3-ActCode-AA"> </a> </td> <td> adjudicated with adjustments</td> <td> The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges). <br/> Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy. <br/> Invoice element can be reversed (nullified). <br/> Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). <br/> </td> </tr> <tr> <td> 3</td> <td>     ANF <a name="v3-ActCode-ANF"> </a> </td> <td> adjudicated with adjustments and no financial impact</td> <td> The invoice element has been accepted for payment but one or more adjustment(s) have been made to one or more invoice element line items (component charges) without changing the amount. <br/> Invoice element can be reversed (nullified). <br/> Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). <br/> </td> </tr> <tr> <td> 2</td> <td>   AR <a name="v3-ActCode-AR"> </a> </td> <td> adjudicated as refused</td> <td> The invoice element has passed through the adjudication process but payment is refused due to one or more reasons. <br/> Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late'). <br/> If one invoice element line item in the invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected. <br/> A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer. <br/> Invoice element cannot be reversed (nullified) as there is nothing to reverse. <br/> Recommend that the invoice element is not saved for DUR (Drug Utilization Reporting). <br/> </td> </tr> <tr> <td> 2</td> <td>   AS <a name="v3-ActCode-AS"> </a> </td> <td> adjudicated as submitted</td> <td> The invoice element was/will be paid exactly as submitted, without financial adjustment(s). <br/> If the dollar amount stays the same, but the billing codes have been amended or financial adjustments have been applied through the adjudication process, the invoice element is treated as "Adjudicated with Adjustment". <br/> If information items are included in the adjudication results that do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim'). <br/> Invoice element can be reversed (nullified). <br/> Recommend that the invoice element is saved for DUR (Drug Utilization Reporting). <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActAdjudicationResultActionCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdjudicationResultActionCode"> </a> </td> <td> Actions to be carried out by the recipient of the Adjudication Result information. <br/> </td> </tr> <tr> <td> 2</td> <td>   DISPLAY <a name="v3-ActCode-DISPLAY"> </a> </td> <td> Display</td> <td> The adjudication result associated is to be displayed to the receiver of the adjudication result. <br/> </td> </tr> <tr> <td> 2</td> <td>   FORM <a name="v3-ActCode-FORM"> </a> </td> <td> Print on Form</td> <td> The adjudication result associated is to be printed on the specified form, which is then provided to the covered party. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActBillableModifierCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActBillableModifierCode"> </a> </td> <td> Definition:An identifying modifier code for healthcare interventions or procedures. <br/> </td> </tr> <tr> <td> 2</td> <td>   CPTM <a name="v3-ActCode-CPTM"> </a> </td> <td> CPT modifier codes</td> <td> Description:CPT modifier codes are found in Appendix A of CPT 2000 Standard Edition. <br/> </td> </tr> <tr> <td> 2</td> <td>   HCPCSA <a name="v3-ActCode-HCPCSA"> </a> </td> <td> HCPCS Level II and Carrier-assigned</td> <td> Description:HCPCS Level II (HCFA-assigned) and Carrier-assigned (Level III) modifiers are reported in Appendix A of CPT 2000 Standard Edition and in the Medicare Bulletin. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActBillingArrangementCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActBillingArrangementCode"> </a> </td> <td> The type of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period. <br/> </td> </tr> <tr> <td> 2</td> <td>   BLK <a name="v3-ActCode-BLK"> </a> </td> <td> block funding</td> <td> A billing arrangement where a Provider charges a lump sum to provide a prescribed group (volume) of services to a single patient which occur over a period of time. Services included in the block may vary. <br/> This billing arrangement is also known as Program of Care for some specific Payors and Program Fees for other Payors. <br/> </td> </tr> <tr> <td> 2</td> <td>   CAP <a name="v3-ActCode-CAP"> </a> </td> <td> capitation funding</td> <td> A billing arrangement where the payment made to a Provider is determined by analyzing one or more demographic attributes about the persons/patients who are enrolled with the Provider (in their practice). <br/> </td> </tr> <tr> <td> 2</td> <td>   CONTF <a name="v3-ActCode-CONTF"> </a> </td> <td> contract funding</td> <td> A billing arrangement where a Provider charges a lump sum to provide a particular volume of one or more interventions/procedures or groups of interventions/procedures. <br/> </td> </tr> <tr> <td> 2</td> <td>   FINBILL <a name="v3-ActCode-FINBILL"> </a> </td> <td> financial</td> <td> A billing arrangement where a Provider charges for non-clinical items. This includes interest in arrears, mileage, etc. Clinical content is not included in Invoices submitted with this type of billing arrangement. <br/> </td> </tr> <tr> <td> 2</td> <td>   ROST <a name="v3-ActCode-ROST"> </a> </td> <td> roster funding</td> <td> A billing arrangement where funding is based on a list of individuals registered as patients of the Provider. <br/> </td> </tr> <tr> <td> 2</td> <td>   SESS <a name="v3-ActCode-SESS"> </a> </td> <td> sessional funding</td> <td> A billing arrangement where a Provider charges a sum to provide a group (volume) of interventions/procedures to one or more patients within a defined period of time, typically on the same date. Interventions/procedures included in the session may vary. <br/> </td> </tr> <tr> <td> 2</td> <td>   FFS <a name="v3-ActCode-FFS"> </a> </td> <td> fee for service</td> <td> A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product. <br/> Fee for Service is used when an individual intervention/procedure/event is used for billing purposes. In other words, fees are associated with the intervention/procedure/ event. For example, a specific CCI (Canadian Classification of Interventions) code has an associated fee and is used for billing purposes. <br/> </td> </tr> <tr> <td> 3</td> <td>     FFPS <a name="v3-ActCode-FFPS"> </a> </td> <td> first fill, part fill, partial strength</td> <td> A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets) <br/> </td> </tr> <tr> <td> 3</td> <td>     FFCS <a name="v3-ActCode-FFCS"> </a> </td> <td> first fill complete, partial strength</td> <td> A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 3</td> <td>     TFS <a name="v3-ActCode-TFS"> </a> </td> <td> trial fill partial strength</td> <td> A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActBoundedROICode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActBoundedROICode"> </a> </td> <td> Type of bounded ROI. <br/> </td> </tr> <tr> <td> 2</td> <td>   ROIFS <a name="v3-ActCode-ROIFS"> </a> </td> <td> fully specified ROI</td> <td> A fully specified bounded Region of Interest (ROI) delineates a ROI in which only those dimensions participate that are specified by boundary criteria, whereas all other dimensions are excluded. For example a ROI to mark an episode of "ST elevation" in a subset of the EKG leads V2, V3, and V4 would include 4 boundaries, one each for time, V2, V3, and V4. <br/> </td> </tr> <tr> <td> 2</td> <td>   ROIPS <a name="v3-ActCode-ROIPS"> </a> </td> <td> partially specified ROI</td> <td> A partially specified bounded Region of Interest (ROI) specifies a ROI in which at least all values in the dimensions specified by the boundary criteria participate. For example, if an episode of ventricular fibrillations (VFib) is observed, it usually doesn't make sense to exclude any EKG leads from the observation and the partially specified ROI would contain only one boundary for time indicating the time interval where VFib was observed. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActCareProvisionCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCareProvisionCode"> </a> </td> <td> Description:The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActCredentialedCareCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCredentialedCareCode"> </a> </td> <td> Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements. <br/> Example:Hospital license; physician license; clinic accreditation. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActCredentialedCareProvisionPersonCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCredentialedCareProvisionPersonCode"> </a> </td> <td> Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals. <br/> </td> </tr> <tr> <td> 4</td> <td>       CACC <a name="v3-ActCode-CACC"> </a> </td> <td> certified anatomic pathology and clinical pathology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CAIC <a name="v3-ActCode-CAIC"> </a> </td> <td> certified allergy and immunology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CAMC <a name="v3-ActCode-CAMC"> </a> </td> <td> certified aerospace medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CANC <a name="v3-ActCode-CANC"> </a> </td> <td> certified anesthesiology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CAPC <a name="v3-ActCode-CAPC"> </a> </td> <td> certified anatomic pathology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CBGC <a name="v3-ActCode-CBGC"> </a> </td> <td> certified clinical biochemical genetics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCCC <a name="v3-ActCode-CCCC"> </a> </td> <td> certified clinical cytogenetics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCGC <a name="v3-ActCode-CCGC"> </a> </td> <td> certified clinical genetics (M.D.) care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCPC <a name="v3-ActCode-CCPC"> </a> </td> <td> certified clinical pathology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCSC <a name="v3-ActCode-CCSC"> </a> </td> <td> certified colon and rectal surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CDEC <a name="v3-ActCode-CDEC"> </a> </td> <td> certified dermatology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CDRC <a name="v3-ActCode-CDRC"> </a> </td> <td> certified diagnostic radiology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CEMC <a name="v3-ActCode-CEMC"> </a> </td> <td> certified emergency medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CFPC <a name="v3-ActCode-CFPC"> </a> </td> <td> certified family practice care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CIMC <a name="v3-ActCode-CIMC"> </a> </td> <td> certified internal medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CMGC <a name="v3-ActCode-CMGC"> </a> </td> <td> certified clinical molecular genetics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CNEC <a name="v3-ActCode-CNEC"> </a> </td> <td> certified neurology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board <br/> </td> </tr> <tr> <td> 4</td> <td>       CNMC <a name="v3-ActCode-CNMC"> </a> </td> <td> certified nuclear medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CNQC <a name="v3-ActCode-CNQC"> </a> </td> <td> certified neurology with special qualifications in child neurology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CNSC <a name="v3-ActCode-CNSC"> </a> </td> <td> certified neurological surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       COGC <a name="v3-ActCode-COGC"> </a> </td> <td> certified obstetrics and gynecology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       COMC <a name="v3-ActCode-COMC"> </a> </td> <td> certified occupational medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       COPC <a name="v3-ActCode-COPC"> </a> </td> <td> certified ophthalmology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       COSC <a name="v3-ActCode-COSC"> </a> </td> <td> certified orthopaedic surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       COTC <a name="v3-ActCode-COTC"> </a> </td> <td> certified otolaryngology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPEC <a name="v3-ActCode-CPEC"> </a> </td> <td> certified pediatrics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPGC <a name="v3-ActCode-CPGC"> </a> </td> <td> certified Ph.D. medical genetics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPHC <a name="v3-ActCode-CPHC"> </a> </td> <td> certified public health and general preventive medicine care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPRC <a name="v3-ActCode-CPRC"> </a> </td> <td> certified physical medicine and rehabilitation care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPSC <a name="v3-ActCode-CPSC"> </a> </td> <td> certified plastic surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPYC <a name="v3-ActCode-CPYC"> </a> </td> <td> certified psychiatry care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CROC <a name="v3-ActCode-CROC"> </a> </td> <td> certified radiation oncology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CRPC <a name="v3-ActCode-CRPC"> </a> </td> <td> certified radiological physics care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSUC <a name="v3-ActCode-CSUC"> </a> </td> <td> certified surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CTSC <a name="v3-ActCode-CTSC"> </a> </td> <td> certified thoracic surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CURC <a name="v3-ActCode-CURC"> </a> </td> <td> certified urology care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       CVSC <a name="v3-ActCode-CVSC"> </a> </td> <td> certified vascular surgery care</td> <td> Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board. <br/> </td> </tr> <tr> <td> 4</td> <td>       LGPC <a name="v3-ActCode-LGPC"> </a> </td> <td> licensed general physician care</td> <td> Description:Scope of responsibility taken-on for physician care of a patient as defined by a governmental licensing agency. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActCredentialedCareProvisionProgramCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCredentialedCareProvisionProgramCode"> </a> </td> <td> Description:The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing programs within organizations. <br/> </td> </tr> <tr> <td> 4</td> <td>       AALC <a name="v3-ActCode-AALC"> </a> </td> <td> accredited assisted living care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       AAMC <a name="v3-ActCode-AAMC"> </a> </td> <td> accredited ambulatory care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       ABHC <a name="v3-ActCode-ABHC"> </a> </td> <td> accredited behavioral health care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       ACAC <a name="v3-ActCode-ACAC"> </a> </td> <td> accredited critical access hospital care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       ACHC <a name="v3-ActCode-ACHC"> </a> </td> <td> accredited hospital care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       AHOC <a name="v3-ActCode-AHOC"> </a> </td> <td> accredited home care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       ALTC <a name="v3-ActCode-ALTC"> </a> </td> <td> accredited long term care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       AOSC <a name="v3-ActCode-AOSC"> </a> </td> <td> accredited office-based surgery care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CACS <a name="v3-ActCode-CACS"> </a> </td> <td> certified acute coronary syndrome care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CAMI <a name="v3-ActCode-CAMI"> </a> </td> <td> certified acute myocardial infarction care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CAST <a name="v3-ActCode-CAST"> </a> </td> <td> certified asthma care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CBAR <a name="v3-ActCode-CBAR"> </a> </td> <td> certified bariatric surgery care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCAD <a name="v3-ActCode-CCAD"> </a> </td> <td> certified coronary artery disease care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CCAR <a name="v3-ActCode-CCAR"> </a> </td> <td> certified cardiac care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CDEP <a name="v3-ActCode-CDEP"> </a> </td> <td> certified depression care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CDGD <a name="v3-ActCode-CDGD"> </a> </td> <td> certified digestive/gastrointestinal disorders care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CDIA <a name="v3-ActCode-CDIA"> </a> </td> <td> certified diabetes care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CEPI <a name="v3-ActCode-CEPI"> </a> </td> <td> certified epilepsy care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CFEL <a name="v3-ActCode-CFEL"> </a> </td> <td> certified frail elderly care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CHFC <a name="v3-ActCode-CHFC"> </a> </td> <td> certified heart failure care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CHRO <a name="v3-ActCode-CHRO"> </a> </td> <td> certified high risk obstetrics care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CHYP <a name="v3-ActCode-CHYP"> </a> </td> <td> certified hyperlipidemia care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CMIH <a name="v3-ActCode-CMIH"> </a> </td> <td> certified migraine headache care</td> <td> Description:. <br/> </td> </tr> <tr> <td> 4</td> <td>       CMSC <a name="v3-ActCode-CMSC"> </a> </td> <td> certified multiple sclerosis care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       COJR <a name="v3-ActCode-COJR"> </a> </td> <td> certified orthopedic joint replacement care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CONC <a name="v3-ActCode-CONC"> </a> </td> <td> certified oncology care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       COPD <a name="v3-ActCode-COPD"> </a> </td> <td> certified chronic obstructive pulmonary disease care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CORT <a name="v3-ActCode-CORT"> </a> </td> <td> certified organ transplant care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPAD <a name="v3-ActCode-CPAD"> </a> </td> <td> certified parkinsons disease care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPND <a name="v3-ActCode-CPND"> </a> </td> <td> certified pneumonia disease care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPST <a name="v3-ActCode-CPST"> </a> </td> <td> certified primary stroke center care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSDM <a name="v3-ActCode-CSDM"> </a> </td> <td> certified stroke disease management care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSIC <a name="v3-ActCode-CSIC"> </a> </td> <td> certified sickle cell care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSLD <a name="v3-ActCode-CSLD"> </a> </td> <td> certified sleep disorders care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSPT <a name="v3-ActCode-CSPT"> </a> </td> <td> certified spine treatment care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CTBU <a name="v3-ActCode-CTBU"> </a> </td> <td> certified trauma/burn center care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CVDC <a name="v3-ActCode-CVDC"> </a> </td> <td> certified vascular diseases care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CWMA <a name="v3-ActCode-CWMA"> </a> </td> <td> certified wound management care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 4</td> <td>       CWOH <a name="v3-ActCode-CWOH"> </a> </td> <td> certified women's health care</td> <td> Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActEncounterCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActEncounterCode"> </a> </td> <td> Domain provides codes that qualify the ActEncounterClass (ENC) <br/> </td> </tr> <tr> <td> 3</td> <td>     AMB <a name="v3-ActCode-AMB"> </a> </td> <td> ambulatory</td> <td> A comprehensive term for health care provided in a healthcare facility (e.g. a practitioneraTMs office, clinic setting, or hospital) on a nonresident basis. The term ambulatory usually implies that the patient has come to the location and is not assigned to a bed. Sometimes referred to as an outpatient encounter. <br/> </td> </tr> <tr> <td> 3</td> <td>     EMER <a name="v3-ActCode-EMER"> </a> </td> <td> emergency</td> <td> A patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate evaluation and treatment, provided until the patient can be discharged or responsibility for the patient's care is transferred elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.) <br/> </td> </tr> <tr> <td> 3</td> <td>     FLD <a name="v3-ActCode-FLD"> </a> </td> <td> field</td> <td> A patient encounter that takes place both outside a dedicated service delivery location and outside a patient's residence. Example locations might include an accident site and at a supermarket. <br/> </td> </tr> <tr> <td> 3</td> <td>     HH <a name="v3-ActCode-HH"> </a> </td> <td> home health</td> <td> Healthcare encounter that takes place in the residence of the patient or a designee <br/> </td> </tr> <tr> <td> 3</td> <td>     IMP <a name="v3-ActCode-IMP"> </a> </td> <td> inpatient encounter</td> <td> A patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients generally stay at least overnight and provided with room, board, and continuous nursing service. <br/> </td> </tr> <tr> <td> 4</td> <td>       ACUTE <a name="v3-ActCode-ACUTE"> </a> </td> <td> inpatient acute</td> <td> An acute inpatient encounter. <br/> </td> </tr> <tr> <td> 4</td> <td>       NONAC <a name="v3-ActCode-NONAC"> </a> </td> <td> inpatient non-acute</td> <td> Any category of inpatient encounter except 'acute' <br/> </td> </tr> <tr> <td> 3</td> <td>     OBSENC <a name="v3-ActCode-OBSENC"> </a> </td> <td> observation encounter</td> <td> An encounter where the patient usually will start in different encounter, such as one in the emergency department (EMER) but then transition to this type of encounter because they require a significant period of treatment and monitoring to determine whether or not their condition warrants an inpatient admission or discharge. In the majority of cases the decision about admission or discharge will occur within a time period determined by local, regional or national regulation, often between 24 and 48 hours. <br/> </td> </tr> <tr> <td> 3</td> <td>     PRENC <a name="v3-ActCode-PRENC"> </a> </td> <td> pre-admission</td> <td> A patient encounter where patient is scheduled or planned to receive service delivery in the future, and the patient is given a pre-admission account number. When the patient comes back for subsequent service, the pre-admission encounter is selected and is encapsulated into the service registration, and a new account number is generated. <br/> Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc. <br/> </td> </tr> <tr> <td> 3</td> <td>     SS <a name="v3-ActCode-SS"> </a> </td> <td> short stay</td> <td> An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours. <br/> </td> </tr> <tr> <td> 3</td> <td>     VR <a name="v3-ActCode-VR"> </a> </td> <td> virtual</td> <td> A patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone conference, email exchange, robotic surgery, and televideo conference. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActMedicalServiceCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActMedicalServiceCode"> </a> </td> <td> General category of medical service provided to the patient during their encounter. <br/> </td> </tr> <tr> <td> 3</td> <td>     ALC <a name="v3-ActCode-ALC"> </a> </td> <td> Alternative Level of Care</td> <td> Provision of Alternate Level of Care to a patient in an acute bed. Patient is waiting for placement in a long-term care facility and is unable to return home. <br/> </td> </tr> <tr> <td> 3</td> <td>     CARD <a name="v3-ActCode-CARD"> </a> </td> <td> Cardiology</td> <td> Provision of diagnosis and treatment of diseases and disorders affecting the heart <br/> </td> </tr> <tr> <td> 3</td> <td>     CHR <a name="v3-ActCode-CHR"> </a> </td> <td> Chronic</td> <td> Provision of recurring care for chronic illness. <br/> </td> </tr> <tr> <td> 3</td> <td>     DNTL <a name="v3-ActCode-DNTL"> </a> </td> <td> Dental</td> <td> Provision of treatment for oral health and/or dental surgery. <br/> </td> </tr> <tr> <td> 3</td> <td>     DRGRHB <a name="v3-ActCode-DRGRHB"> </a> </td> <td> Drug Rehab</td> <td> Provision of treatment for drug abuse. <br/> </td> </tr> <tr> <td> 3</td> <td>     GENRL <a name="v3-ActCode-GENRL"> </a> </td> <td> General</td> <td> General care performed by a general practitioner or family doctor as a responsible provider for a patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     MED <a name="v3-ActCode-MED"> </a> </td> <td> Medical</td> <td> Provision of diagnostic and/or therapeutic treatment. <br/> </td> </tr> <tr> <td> 3</td> <td>     OBS <a name="v3-ActCode-OBS"> </a> </td> <td> Obstetrics</td> <td> Provision of care of women during pregnancy, childbirth and immediate postpartum period. Also known as Maternity. <br/> </td> </tr> <tr> <td> 3</td> <td>     ONC <a name="v3-ActCode-ONC"> </a> </td> <td> Oncology</td> <td> Provision of treatment and/or diagnosis related to tumors and/or cancer. <br/> </td> </tr> <tr> <td> 3</td> <td>     PALL <a name="v3-ActCode-PALL"> </a> </td> <td> Palliative</td> <td> Provision of care for patients who are living or dying from an advanced illness. <br/> </td> </tr> <tr> <td> 3</td> <td>     PED <a name="v3-ActCode-PED"> </a> </td> <td> Pediatrics</td> <td> Provision of diagnosis and treatment of diseases and disorders affecting children. <br/> </td> </tr> <tr> <td> 3</td> <td>     PHAR <a name="v3-ActCode-PHAR"> </a> </td> <td> Pharmaceutical</td> <td> Pharmaceutical care performed by a pharmacist. <br/> </td> </tr> <tr> <td> 3</td> <td>     PHYRHB <a name="v3-ActCode-PHYRHB"> </a> </td> <td> Physical Rehab</td> <td> Provision of treatment for physical injury. <br/> </td> </tr> <tr> <td> 3</td> <td>     PSYCH <a name="v3-ActCode-PSYCH"> </a> </td> <td> Psychiatric</td> <td> Provision of treatment of psychiatric disorder relating to mental illness. <br/> </td> </tr> <tr> <td> 3</td> <td>     SURG <a name="v3-ActCode-SURG"> </a> </td> <td> Surgical</td> <td> Provision of surgical treatment. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActClaimAttachmentCategoryCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActClaimAttachmentCategoryCode"> </a> </td> <td> Description: Coded types of attachments included to support a healthcare claim. <br/> </td> </tr> <tr> <td> 2</td> <td>   AUTOATTCH <a name="v3-ActCode-AUTOATTCH"> </a> </td> <td> auto attachment</td> <td> Description: Automobile Information Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   DOCUMENT <a name="v3-ActCode-DOCUMENT"> </a> </td> <td> document</td> <td> Description: Document Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   HEALTHREC <a name="v3-ActCode-HEALTHREC"> </a> </td> <td> health record</td> <td> Description: Health Record Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   IMG <a name="v3-ActCode-IMG"> </a> </td> <td> image attachment</td> <td> Description: Image Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   LABRESULTS <a name="v3-ActCode-LABRESULTS"> </a> </td> <td> lab results</td> <td> Description: Lab Results Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   MODEL <a name="v3-ActCode-MODEL"> </a> </td> <td> model</td> <td> Description: Digital Model Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   WIATTCH <a name="v3-ActCode-WIATTCH"> </a> </td> <td> work injury report attachment</td> <td> Description: Work Injury related additional Information Attachment <br/> </td> </tr> <tr> <td> 2</td> <td>   XRAY <a name="v3-ActCode-XRAY"> </a> </td> <td> x-ray</td> <td> Description: Digital X-Ray Attachment <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActConsentType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActConsentType"> </a> </td> <td> Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research. <br/> </td> </tr> <tr> <td> 2</td> <td>   ICOL <a name="v3-ActCode-ICOL"> </a> </td> <td> information collection</td> <td> Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated. <br/> </td> </tr> <tr> <td> 2</td> <td>   IDSCL <a name="v3-ActCode-IDSCL"> </a> </td> <td> information disclosure</td> <td> Definition: Consent to have collected healthcare information disclosed. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFA <a name="v3-ActCode-INFA"> </a> </td> <td> information access</td> <td> Definition: Consent to access healthcare information. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFAO <a name="v3-ActCode-INFAO"> </a> </td> <td> access only</td> <td> Definition: Consent to access or "read" only, which entails that the information is not to be copied, screen printed, saved, emailed, stored, re-disclosed or altered in any way. This level ensures that data which is masked or to which access is restricted will not be. <br/> Example: Opened and then emailed or screen printed for use outside of the consent directive purpose. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFASO <a name="v3-ActCode-INFASO"> </a> </td> <td> access and save only</td> <td> Definition: Consent to access and save only, which entails that access to the saved copy will remain locked. <br/> </td> </tr> <tr> <td> 2</td> <td>   IRDSCL <a name="v3-ActCode-IRDSCL"> </a> </td> <td> information redisclosure</td> <td> Definition: Information re-disclosed without the patient's consent. <br/> </td> </tr> <tr> <td> 2</td> <td>   RESEARCH <a name="v3-ActCode-RESEARCH"> </a> </td> <td> research information access</td> <td> Definition: Consent to have healthcare information in an electronic health record accessed for research purposes. <br/> </td> </tr> <tr> <td> 3</td> <td>     RSDID <a name="v3-ActCode-RSDID"> </a> </td> <td> de-identified information access</td> <td> Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes, but without consent to re-identify the information under any circumstance. <br/> </td> </tr> <tr> <td> 3</td> <td>     RSREID <a name="v3-ActCode-RSREID"> </a> </td> <td> re-identifiable information access</td> <td> Definition: Consent to have de-identified healthcare information in an electronic health record that is accessed for research purposes re-identified under specific circumstances outlined in the consent. <br/> Example:: Where there is a need to inform the subject of potential health issues. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActContainerRegistrationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActContainerRegistrationCode"> </a> </td> <td> Constrains the ActCode to the domain of Container Registration <br/> </td> </tr> <tr> <td> 2</td> <td>   ID <a name="v3-ActCode-ID"> </a> </td> <td> Identified</td> <td> Used by one system to inform another that it has received a container. <br/> </td> </tr> <tr> <td> 2</td> <td>   IP <a name="v3-ActCode-IP"> </a> </td> <td> In Position</td> <td> Used by one system to inform another that the container is in position for specimen transfer (e.g., container removal from track, pipetting, etc.). <br/> </td> </tr> <tr> <td> 2</td> <td>   L <a name="v3-ActCode-L"> </a> </td> <td> Left Equipment</td> <td> Used by one system to inform another that the container has been released from that system. <br/> </td> </tr> <tr> <td> 2</td> <td>   M <a name="v3-ActCode-M"> </a> </td> <td> Missing</td> <td> Used by one system to inform another that the container did not arrive at its next expected location. <br/> </td> </tr> <tr> <td> 2</td> <td>   O <a name="v3-ActCode-O"> </a> </td> <td> In Process</td> <td> Used by one system to inform another that the specific container is being processed by the equipment. It is useful as a response to a query about Container Status, when the specific step of the process is not relevant. <br/> </td> </tr> <tr> <td> 2</td> <td>   R <a name="v3-ActCode-R"> </a> </td> <td> Process Completed</td> <td> Status is used by one system to inform another that the processing has been completed, but the container has not been released from that system. <br/> </td> </tr> <tr> <td> 2</td> <td>   X <a name="v3-ActCode-X"> </a> </td> <td> Container Unavailable</td> <td> Used by one system to inform another that the container is no longer available within the scope of the system (e.g., tube broken or discarded). <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActControlVariable)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActControlVariable"> </a> </td> <td> An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure. <br/> Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control variables sometimes can be observed (by noting the control settings or an actually measured feedback loop) they are not primary observations, in the sense that a control variable without a primary act is of no use (e.g., it makes no sense to record a blood pressure position without recording a blood pressure, whereas it does make sense to record a systolic blood pressure without a diastolic blood pressure). <br/> </td> </tr> <tr> <td> 2</td> <td>   AUTO <a name="v3-ActCode-AUTO"> </a> </td> <td> auto-repeat permission</td> <td> Specifies whether or not automatic repeat testing is to be initiated on specimens. <br/> </td> </tr> <tr> <td> 2</td> <td>   ENDC <a name="v3-ActCode-ENDC"> </a> </td> <td> endogenous content</td> <td> A baseline value for the measured test that is inherently contained in the diluent. In the calculation of the actual result for the measured test, this baseline value is normally considered. <br/> </td> </tr> <tr> <td> 2</td> <td>   REFLEX <a name="v3-ActCode-REFLEX"> </a> </td> <td> reflex permission</td> <td> Specifies whether or not further testing may be automatically or manually initiated on specimens. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActCoverageConfirmationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageConfirmationCode"> </a> </td> <td> Response to an insurance coverage eligibility query or authorization request. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActCoverageAuthorizationConfirmationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageAuthorizationConfirmationCode"> </a> </td> <td> Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside. <br/> </td> </tr> <tr> <td> 3</td> <td>     AUTH <a name="v3-ActCode-AUTH"> </a> </td> <td> Authorized</td> <td> Authorization approved and funds have been set aside to pay for specified healthcare service(s) and/or product(s) within defined criteria for the authorization. <br/> </td> </tr> <tr> <td> 3</td> <td>     NAUTH <a name="v3-ActCode-NAUTH"> </a> </td> <td> Not Authorized</td> <td> Authorization for specified healthcare service(s) and/or product(s) denied. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActCoverageEligibilityConfirmationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageEligibilityConfirmationCode"> </a> </td> <td> Indication of eligibility coverage for healthcare service(s) and/or product(s). <br/> </td> </tr> <tr> <td> 3</td> <td>     ELG <a name="v3-ActCode-ELG"> </a> </td> <td> Eligible</td> <td> Insurance coverage is in effect for healthcare service(s) and/or product(s). <br/> </td> </tr> <tr> <td> 3</td> <td>     NELG <a name="v3-ActCode-NELG"> </a> </td> <td> Not Eligible</td> <td> Insurance coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActCoverageLimitCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageLimitCode"> </a> </td> <td> Criteria that are applicable to the authorized coverage. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActCoverageQuantityLimitCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageQuantityLimitCode"> </a> </td> <td> Maximum amount paid or maximum number of services/products covered; or maximum amount or number covered during a specified time period under the policy or program. <br/> </td> </tr> <tr> <td> 3</td> <td>     COVPRD <a name="v3-ActCode-COVPRD"> </a> </td> <td> coverage period</td> <td> Codes representing the time period during which coverage is available; or financial participation requirements are in effect. <br/> </td> </tr> <tr> <td> 3</td> <td>     LFEMX <a name="v3-ActCode-LFEMX"> </a> </td> <td> life time maximum</td> <td> Definition: Maximum amount paid by payer or covered party; or maximum number of services or products covered under the policy or program during a covered party's lifetime. <br/> </td> </tr> <tr> <td> 3</td> <td>     NETAMT <a name="v3-ActCode-NETAMT"> </a> </td> <td> Net Amount</td> <td> Maximum net amount that will be covered for the product or service specified. <br/> </td> </tr> <tr> <td> 3</td> <td>     PRDMX <a name="v3-ActCode-PRDMX"> </a> </td> <td> period maximum</td> <td> Definition: Maximum amount paid by payer or covered party; or maximum number of services/products covered under the policy or program by time period specified by the effective time on the act. <br/> </td> </tr> <tr> <td> 3</td> <td>     UNITPRICE <a name="v3-ActCode-UNITPRICE"> </a> </td> <td> Unit Price</td> <td> Maximum unit price that will be covered for the authorized product or service. <br/> </td> </tr> <tr> <td> 3</td> <td>     UNITQTY <a name="v3-ActCode-UNITQTY"> </a> </td> <td> Unit Quantity</td> <td> Maximum number of items that will be covered of the product or service specified. <br/> </td> </tr> <tr> <td> 2</td> <td>   COVMX <a name="v3-ActCode-COVMX"> </a> </td> <td> coverage maximum</td> <td> Definition: Codes representing the maximum coverate or financial participation requirements. <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#LFEMX">LFEMX</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     <a href="#PRDMX">PRDMX</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActCoveredPartyLimitCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoveredPartyLimitCode"> </a> </td> <td> Codes representing the types of covered parties that may receive covered benefits under a policy or program. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActCoverageTypeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActCoverageTypeCode"> </a> </td> <td> Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInsurancePolicyCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInsurancePolicyCode"> </a> </td> <td> Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs. <br/> </td> </tr> <tr> <td> 3</td> <td>     EHCPOL <a name="v3-ActCode-EHCPOL"> </a> </td> <td> extended healthcare</td> <td> Private insurance policy that provides coverage in addition to other policies (e.g. in addition to a Public Healthcare insurance policy). <br/> </td> </tr> <tr> <td> 3</td> <td>     HSAPOL <a name="v3-ActCode-HSAPOL"> </a> </td> <td> health spending account</td> <td> Insurance policy that provides for an allotment of funds replenished on a periodic (e.g. annual) basis. The use of the funds under this policy is at the discretion of the covered party. <br/> </td> </tr> <tr> <td> 3</td> <td>     AUTOPOL <a name="v3-ActCode-AUTOPOL"> </a> </td> <td> automobile</td> <td> Insurance policy for injuries sustained in an automobile accident. Will also typically covered non-named parties to the policy, such as pedestrians and passengers. <br/> </td> </tr> <tr> <td> 4</td> <td>       COL <a name="v3-ActCode-COL"> </a> </td> <td> collision coverage policy</td> <td> Definition: An automobile insurance policy under which the insurance company will cover the cost of damages to an automobile owned by the named insured that are caused by accident or intentionally by another party. <br/> </td> </tr> <tr> <td> 4</td> <td>       UNINSMOT <a name="v3-ActCode-UNINSMOT"> </a> </td> <td> uninsured motorist policy</td> <td> Definition: An automobile insurance policy under which the insurance company will indemnify a loss for which another motorist is liable if that motorist is unable to pay because he or she is uninsured. Coverage under the policy applies to bodily injury damages only. Injuries to the covered party caused by a hit-and-run driver are also covered. <br/> </td> </tr> <tr> <td> 3</td> <td>     PUBLICPOL <a name="v3-ActCode-PUBLICPOL"> </a> </td> <td> public healthcare</td> <td> Insurance policy funded by a public health system such as a provincial or national health plan. Examples include BC MSP (British Columbia Medical Services Plan) OHIP (Ontario Health Insurance Plan), NHS (National Health Service). <br/> </td> </tr> <tr> <td> 4</td> <td>       DENTPRG <a name="v3-ActCode-DENTPRG"> </a> </td> <td> dental program</td> <td> Definition: A public or government health program that administers and funds coverage for dental care to assist program eligible who meet financial and health status criteria. <br/> </td> </tr> <tr> <td> 4</td> <td>       DISEASEPRG <a name="v3-ActCode-DISEASEPRG"> </a> </td> <td> public health program</td> <td> Definition: A public or government health program that administers and funds coverage for health and social services to assist program eligible who meet financial and health status criteria related to a particular disease. <br/> Example: Reproductive health, sexually transmitted disease, and end renal disease programs. <br/> </td> </tr> <tr> <td> 5</td> <td>         CANPRG <a name="v3-ActCode-CANPRG"> </a> </td> <td> women's cancer detection program</td> <td> Definition: A program that provides low-income, uninsured, and underserved women access to timely, high-quality screening and diagnostic services, to detect breast and cervical cancer at the earliest stages. <br/> Example: To improve women's access to screening for breast and cervical cancers, Congress passed the Breast and Cervical Cancer Mortality Prevention Act of 1990, which guided CDC in creating the National Breast and Cervical Cancer Early Detection Program (NBCCEDP), which provides access to critical breast and cervical cancer screening services for underserved women in the United States. An estimated 7 to 10% of U.S. women of screening age are eligible to receive NBCCEDP services. Federal guidelines establish an eligibility baseline to direct services to uninsured and underinsured women at or below 250% of federal poverty level; ages 18 to 64 for cervical screening; ages 40 to 64 for breast screening. <br/> </td> </tr> <tr> <td> 5</td> <td>         ENDRENAL <a name="v3-ActCode-ENDRENAL"> </a> </td> <td> end renal program</td> <td> Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services. <br/> Example: In the U.S., the Medicare End-stage Renal Disease program (ESRD), the National Kidney Foundation (NKF) American Kidney Fund (AKF) The Organ Transplant Fund. <br/> </td> </tr> <tr> <td> 5</td> <td>         HIVAIDS <a name="v3-ActCode-HIVAIDS"> </a> </td> <td> HIV-AIDS program</td> <td> Definition: Government administered and funded HIV-AIDS program for beneficiaries meeting financial and health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. <br/> Example: In the U.S., the Ryan White program, which is administered by the Health Resources and Services Administration. <br/> </td> </tr> <tr> <td> 4</td> <td>       MANDPOL <a name="v3-ActCode-MANDPOL"> </a> </td> <td> mandatory health program</td> <td/> </tr> <tr> <td> 4</td> <td>       MENTPRG <a name="v3-ActCode-MENTPRG"> </a> </td> <td> mental health program</td> <td> Definition: Government administered and funded mental health program for beneficiaries meeting financial and mental health status criteria. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. <br/> Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). <br/> </td> </tr> <tr> <td> 4</td> <td>       SAFNET <a name="v3-ActCode-SAFNET"> </a> </td> <td> safety net clinic program</td> <td> Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics. <br/> Example: In the U.S., safety net providers such as federally qualified health centers (FQHC) receive funding under PHSA Section 330 grants administered by the Health Resources and Services Administration. <br/> </td> </tr> <tr> <td> 4</td> <td>       SUBPRG <a name="v3-ActCode-SUBPRG"> </a> </td> <td> substance use program</td> <td> Definition: Government administered and funded substance use program for beneficiaries meeting financial, substance use behavior, and health status criteria. Beneficiaries may be required to enroll as a result of legal proceedings. Administration, funding levels, eligibility criteria, covered benefits, provider types, and financial participation are typically set by a regulatory process. Payer responsibilities for administering the program may be delegated to contractors. <br/> Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA). <br/> </td> </tr> <tr> <td> 4</td> <td>       SUBSIDIZ <a name="v3-ActCode-SUBSIDIZ"> </a> </td> <td> subsidized health program</td> <td> Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. <br/> </td> </tr> <tr> <td> 5</td> <td>         SUBSIDMC <a name="v3-ActCode-SUBSIDMC"> </a> </td> <td> subsidized managed care program</td> <td> Definition: A government health program that provides coverage through managed care contracts for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. <br/> Discussion: The structure and business processes for underwriting and administering a subsidized managed care program is further specified by the Underwriter and Payer Role.class and Role.code. <br/> </td> </tr> <tr> <td> 5</td> <td>         SUBSUPP <a name="v3-ActCode-SUBSUPP"> </a> </td> <td> subsidized supplemental health program</td> <td> Definition: A government health program that provides coverage for health services to persons meeting eligibility criteria for a supplemental health policy or program such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. <br/> Example: Supplemental health coverage program may cover the cost of a health program or policy financial participations, such as the copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy. In the U.S., Medicaid programs may pay the premium for a covered party who is also covered under the Medicare program or a private health policy. <br/> Discussion: The structure and business processes for underwriting and administering a subsidized supplemental retiree health program is further specified by the Underwriter and Payer Role.class and Role.code. <br/> </td> </tr> <tr> <td> 3</td> <td>     WCBPOL <a name="v3-ActCode-WCBPOL"> </a> </td> <td> worker's compensation</td> <td> Insurance policy for injuries sustained in the work place or in the course of employment. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInsuranceTypeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInsuranceTypeCode"> </a> </td> <td> Definition: Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly. A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss. An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer. A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured. <br/> Discussion: In contrast to programs, an insurance policy has one or more policy holders, who own the policy. The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer. A subscriber of a self-insured health insurance policy is a policy holder. A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer. See CoveredRoleType. <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#AUTOPOL">AUTOPOL</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActHealthInsuranceTypeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActHealthInsuranceTypeCode"> </a> </td> <td> Definition: Set of codes indicating the type of health insurance policy that covers health services provided to covered parties. A health insurance policy is a written contract for insurance between the insurance company and the policyholder, and contains pertinent facts about the policy owner (the policy holder), the health insurance coverage, the insured subscribers and dependents, and the insurer. Health insurance is typically administered in accordance with a plan, which specifies (1) the type of health services and health conditions that will be covered under what circumstances (e.g., exclusion of a pre-existing condition, service must be deemed medically necessary; service must not be experimental; service must provided in accordance with a protocol; drug must be on a formulary; service must be prior authorized; or be a referral from a primary care provider); (2) the type and affiliation of providers (e.g., only allopathic physicians, only in network, only providers employed by an HMO); (3) financial participations required of covered parties (e.g., co-pays, coinsurance, deductibles, out-of-pocket); and (4) the manner in which services will be paid (e.g., under indemnity or fee-for-service health plans, the covered party typically pays out-of-pocket and then file a claim for reimbursement, while health plans that have contractual relationships with providers, i.e., network providers, typically do not allow the providers to bill the covered party for the cost of the service until after filing a claim with the payer and receiving reimbursement). <br/> </td> </tr> <tr> <td> 4</td> <td>       DENTAL <a name="v3-ActCode-DENTAL"> </a> </td> <td> dental care policy</td> <td> Definition: A health insurance policy that that covers benefits for dental services. <br/> </td> </tr> <tr> <td> 4</td> <td>       DISEASE <a name="v3-ActCode-DISEASE"> </a> </td> <td> disease specific policy</td> <td> Definition: A health insurance policy that covers benefits for healthcare services provided for named conditions under the policy, e.g., cancer, diabetes, or HIV-AIDS. <br/> </td> </tr> <tr> <td> 4</td> <td>       DRUGPOL <a name="v3-ActCode-DRUGPOL"> </a> </td> <td> drug policy</td> <td> Definition: A health insurance policy that covers benefits for prescription drugs, pharmaceuticals, and supplies. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#EHCPOL">EHCPOL</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       HIP <a name="v3-ActCode-HIP"> </a> </td> <td> health insurance plan policy</td> <td> Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from medical expenses arising from health conditions, sickness, or accidental injury as well as preventive care. Health insurance policies explicitly exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. <br/> Discussion: Health insurance policies are offered by health insurance plans that typically reimburse providers for covered services on a fee-for-service basis, that is, a fee that is the allowable amount that a provider may charge. This is in contrast to managed care plans, which typically prepay providers a per-member/per-month amount or capitation as reimbursement for all covered services rendered. Health insurance plans include indemnity and healthcare services plans. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#HSAPOL">HSAPOL</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       LTC <a name="v3-ActCode-LTC"> </a> </td> <td> long term care policy</td> <td> Definition: An insurance policy that covers benefits for long-term care services people need when they no longer can care for themselves. This may be due to an accident, disability, prolonged illness or the simple process of aging. Long-term care services assist with activities of daily living including: <br/> Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing <br/> Care in the community, such as in an adult day care facility <br/> Supervised care provided in an assisted living facility <br/> Skilled care provided in a nursing home <br/> </td> </tr> <tr> <td> 4</td> <td>       MCPOL <a name="v3-ActCode-MCPOL"> </a> </td> <td> managed care policy</td> <td> Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. <br/> Managed care policies specifically exclude coverage for losses insured under a disability policy, workers' compensation program, liability insurance (including automobile insurance); or for medical expenses, coverage for on-site medical clinics or for limited dental or vision benefits when these are provided under a separate policy. <br/> Discussion: Managed care policies are offered by managed care plans that contract with selected providers or health care organizations to provide comprehensive health care at a discount to covered parties and coordinate the financing and delivery of health care. Managed care uses medical protocols and procedures agreed on by the medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a capitated amount on a per member per month basis that may reflect difference in the health status and level of services anticipated to be needed by the member. <br/> </td> </tr> <tr> <td> 5</td> <td>         POS <a name="v3-ActCode-POS"> </a> </td> <td> point of service policy</td> <td> Definition: A policy for a health plan that has features of both an HMO and a FFS plan. Like an HMO, a POS plan encourages the use its HMO network to maintain discounted fees with participating providers, but recognizes that sometimes covered parties want to choose their own provider. The POS plan allows a covered party to use providers who are not part of the HMO network (non-participating providers). However, there is a greater cost associated with choosing these non-network providers. A covered party will usually pay deductibles and coinsurances that are substantially higher than the payments when he or she uses a plan provider. Use of non-participating providers often requires the covered party to pay the provider directly and then to file a claim for reimbursement, like in an FFS plan. <br/> </td> </tr> <tr> <td> 5</td> <td>         HMO <a name="v3-ActCode-HMO"> </a> </td> <td> health maintenance organization policy</td> <td> Definition: A policy for a health plan that provides coverage for health care only through contracted or employed physicians and hospitals located in particular geographic or service areas. HMOs emphasize prevention and early detection of illness. Eligibility to enroll in an HMO is determined by where a covered party lives or works. <br/> </td> </tr> <tr> <td> 5</td> <td>         PPO <a name="v3-ActCode-PPO"> </a> </td> <td> preferred provider organization policy</td> <td> Definition: A network-based, managed care plan that allows a covered party to choose any health care provider. However, if care is received from a "preferred" (participating in-network) provider, there are generally higher benefit coverage and lower deductibles. <br/> </td> </tr> <tr> <td> 4</td> <td>       MENTPOL <a name="v3-ActCode-MENTPOL"> </a> </td> <td> mental health policy</td> <td> Definition: A health insurance policy that covers benefits for mental health services and prescriptions. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#POS">POS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       SUBPOL <a name="v3-ActCode-SUBPOL"> </a> </td> <td> substance use policy</td> <td> Definition: A health insurance policy that covers benefits for substance use services. <br/> </td> </tr> <tr> <td> 4</td> <td>       VISPOL <a name="v3-ActCode-VISPOL"> </a> </td> <td> vision care policy</td> <td> Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services. <br/> A health insurance policy that covers benefits for vision care services, prescriptions, and products. <br/> </td> </tr> <tr> <td> 3</td> <td>     DIS <a name="v3-ActCode-DIS"> </a> </td> <td> disability insurance policy</td> <td> Definition: An insurance policy that provides a regular payment to compensate for income lost due to the covered party's inability to work because of illness or injury. <br/> </td> </tr> <tr> <td> 3</td> <td>     EWB <a name="v3-ActCode-EWB"> </a> </td> <td> employee welfare benefit plan policy</td> <td> Definition: An insurance policy under a benefit plan run by an employer or employee organization for the purpose of providing benefits other than pension-related to employees and their families. Typically provides health-related benefits, benefits for disability, disease or unemployment, or day care and scholarship benefits, among others. An employer sponsored health policy includes coverage of health care expenses arising from sickness or accidental injury, coverage for on-site medical clinics or for dental or vision benefits, which are typically provided under a separate policy. Coverage excludes health care expenses covered by accident or disability, workers' compensation, liability or automobile insurance. <br/> </td> </tr> <tr> <td> 3</td> <td>     FLEXP <a name="v3-ActCode-FLEXP"> </a> </td> <td> flexible benefit plan policy</td> <td> Definition: An insurance policy that covers qualified benefits under a Flexible Benefit plan such as group medical insurance, long and short term disability income insurance, group term life insurance for employees only up to $50,000 face amount, specified disease coverage such as a cancer policy, dental and/or vision insurance, hospital indemnity insurance, accidental death and dismemberment insurance, a medical expense reimbursement plan and a dependent care reimbursement plan. <br/> Discussion: See UnderwriterRoleTypeCode flexible benefit plan which is defined as a benefit plan that allows employees to choose from several life, health, disability, dental, and other insurance plans according to their individual needs. Also known as cafeteria plans. Authorized under Section 125 of the Revenue Act of 1978. <br/> </td> </tr> <tr> <td> 3</td> <td>     LIFE <a name="v3-ActCode-LIFE"> </a> </td> <td> life insurance policy</td> <td> Definition: A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals. Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party. For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion. <br/> Discussion:A life insurance policy may be used by the covered party as a source of health care coverage in the case of a viatical settlement, which is the sale of a life insurance policy by the policy owner, before the policy matures. Such a sale, at a price discounted from the face amount of the policy but usually in excess of the premiums paid or current cash surrender value, provides the seller an immediate cash settlement. Generally, viatical settlements involve insured individuals with a life expectancy of less than two years. In countries without state-subsidized healthcare and high healthcare costs (e.g. United States), this is a practical way to pay extremely high health insurance premiums that severely ill people face. Some people are also familiar with life settlements, which are similar transactions but involve insureds with longer life expectancies (two to fifteen years). <br/> </td> </tr> <tr> <td> 4</td> <td>       ANNU <a name="v3-ActCode-ANNU"> </a> </td> <td> annuity policy</td> <td> Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals. <br/> For example, a policy holder may pay $10,000, and in return receive $150 each month until he dies; or $1,000 for each of 14 years or death benefits if he dies before the full term of the annuity has elapsed. <br/> </td> </tr> <tr> <td> 4</td> <td>       TLIFE <a name="v3-ActCode-TLIFE"> </a> </td> <td> term life insurance policy</td> <td> Definition: Life insurance under which the benefit is payable only if the insured dies during a specified period. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing. <br/> </td> </tr> <tr> <td> 4</td> <td>       ULIFE <a name="v3-ActCode-ULIFE"> </a> </td> <td> universal life insurance policy</td> <td> Definition: Life insurance under which the benefit is payable upon the insuredaTMs death or diagnosis of a terminal illness. If an insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing <br/> </td> </tr> <tr> <td> 3</td> <td>     PNC <a name="v3-ActCode-PNC"> </a> </td> <td> property and casualty insurance policy</td> <td> Definition: A type of insurance that covers damage to or loss of the policyholderaTMs property by providing payments for damages to property damage or the injury or death of living subjects. The terms "casualty" and "liability" insurance are often used interchangeably. Both cover the policyholder's legal liability for damages caused to other persons and/or their property. <br/> </td> </tr> <tr> <td> 3</td> <td>     REI <a name="v3-ActCode-REI"> </a> </td> <td> reinsurance policy</td> <td> Definition: An agreement between two or more insurance companies by which the risk of loss is proportioned. Thus the risk of loss is spread and a disproportionately large loss under a single policy does not fall on one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the risk of loss of another insurance company. <br/> Discussion: Reinsurance is a means by which an insurance company can protect itself against the risk of losses with other insurance companies. Individuals and corporations obtain insurance policies to provide protection for various risks (hurricanes, earthquakes, lawsuits, collisions, sickness and death, etc.). Reinsurers, in turn, provide insurance to insurance companies. <br/> For example, an HMO may purchase a reinsurance policy to protect itself from losing too much money from one insured's particularly expensive health care costs. An insurance company issuing an automobile liability policy, with a limit of $100,000 per accident may reinsure its liability in excess of $10,000. A fire insurance company which issues a large policy generally reinsures a portion of the risk with one or several other companies. Also called risk control insurance or stop-loss insurance. <br/> </td> </tr> <tr> <td> 3</td> <td>     SURPL <a name="v3-ActCode-SURPL"> </a> </td> <td> surplus line insurance policy</td> <td> Definition: <br/> A risk or part of a risk for which there is no normal insurance market available. <br/> Insurance written by unauthorized insurance companies. Surplus lines insurance is insurance placed with unauthorized insurance companies through licensed surplus lines agents or brokers. <br/> </td> </tr> <tr> <td> 3</td> <td>     UMBRL <a name="v3-ActCode-UMBRL"> </a> </td> <td> umbrella liability insurance policy</td> <td> Definition: A form of insurance protection that provides additional liability coverage after the limits of your underlying policy are reached. An umbrella liability policy also protects you (the insured) in many situations not covered by the usual liability policies. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActProgramTypeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActProgramTypeCode"> </a> </td> <td> Definition: A set of codes used to indicate coverage under a program. A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight. Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation. Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds. <br/> Discussion: Programs do not have policy holders or subscribers. Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age. Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients. Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage. See CoveredPartyRoleType. <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#PUBLICPOL">PUBLICPOL</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     <a href="#WCBPOL">WCBPOL</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     CHAR <a name="v3-ActCode-CHAR"> </a> </td> <td> charity program</td> <td> Definition: A program that covers the cost of services provided directly to a beneficiary who typically has no other source of coverage without charge. <br/> </td> </tr> <tr> <td> 3</td> <td>     CRIME <a name="v3-ActCode-CRIME"> </a> </td> <td> crime victim program</td> <td> Definition: A program that covers the cost of services provided to crime victims for injuries or losses related to the occurrence of a crime. <br/> </td> </tr> <tr> <td> 3</td> <td>     EAP <a name="v3-ActCode-EAP"> </a> </td> <td> employee assistance program</td> <td> Definition: An employee assistance program is run by an employer or employee organization for the purpose of providing benefits and covering all or part of the cost for employees to receive counseling, referrals, and advice in dealing with stressful issues in their lives. These may include substance abuse, bereavement, marital problems, weight issues, or general wellness issues. The services are usually provided by a third-party, rather than the company itself, and the company receives only summary statistical data from the service provider. Employee's names and services received are kept confidential. <br/> </td> </tr> <tr> <td> 3</td> <td>     GOVEMP <a name="v3-ActCode-GOVEMP"> </a> </td> <td> government employee health program</td> <td> Definition: A set of codes used to indicate a government program that is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health and financial status. Government programs are established or permitted by legislation with provisions for ongoing government oversight. Regulation mandates the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency is charged with implementing the program in accordance to the regulation <br/> Example: Federal employee health benefit program in the U.S. <br/> </td> </tr> <tr> <td> 3</td> <td>     HIRISK <a name="v3-ActCode-HIRISK"> </a> </td> <td> high risk pool program</td> <td> Definition: A government program that provides health coverage to individuals who are considered medically uninsurable or high risk, and who have been denied health insurance due to a serious health condition. In certain cases, it also applies to those who have been quoted very high premiums a" again, due to a serious health condition. The pool charges premiums for coverage. Because the pool covers high-risk people, it incurs a higher level of claims than premiums can cover. The insurance industry pays into the pool to make up the difference and help it remain viable. <br/> </td> </tr> <tr> <td> 3</td> <td>     IND <a name="v3-ActCode-IND"> </a> </td> <td> indigenous peoples health program</td> <td> Definition: Services provided directly and through contracted and operated indigenous peoples health programs. <br/> Example: Indian Health Service in the U.S. <br/> </td> </tr> <tr> <td> 3</td> <td>     MILITARY <a name="v3-ActCode-MILITARY"> </a> </td> <td> military health program</td> <td> Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents. A covered party who is a subscriber can choose from among Fee-for-Service (FFS) plans, and their Preferred Provider Organizations (PPO), or Plans offering a Point of Service (POS) Product, or Health Maintenance Organizations. <br/> Example: In the U.S., TRICARE, CHAMPUS. <br/> </td> </tr> <tr> <td> 3</td> <td>     RETIRE <a name="v3-ActCode-RETIRE"> </a> </td> <td> retiree health program</td> <td> Definition: A government mandated program with specific eligibility requirements based on premium contributions made during employment, length of employment, age, and employment status, e.g., being retired, disabled, or a dependent of a covered party under this program. Benefits typically include ambulatory, inpatient, and long-term care, such as hospice care, home health care and respite care. <br/> </td> </tr> <tr> <td> 3</td> <td>     SOCIAL <a name="v3-ActCode-SOCIAL"> </a> </td> <td> social service program</td> <td> Definition: A social service program funded by a public or governmental entity. <br/> Example: Programs providing habilitation, food, lodging, medicine, transportation, equipment, devices, products, education, training, counseling, alteration of living or work space, and other resources to persons meeting eligibility criteria. <br/> </td> </tr> <tr> <td> 3</td> <td>     VET <a name="v3-ActCode-VET"> </a> </td> <td> veteran health program</td> <td> Definition: Services provided directly and through contracted and operated veteran health programs. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActDetectedIssueManagementCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActDetectedIssueManagementCode"> </a> </td> <td> Codes dealing with the management of Detected Issue observations <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActAdministrativeDetectedIssueManagementCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdministrativeDetectedIssueManagementCode"> </a> </td> <td> Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_AuthorizationIssueManagementCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_AuthorizationIssueManagementCode"> </a> </td> <td/> </tr> <tr> <td> 4</td> <td>       EMAUTH <a name="v3-ActCode-EMAUTH"> </a> </td> <td> emergency authorization override</td> <td> Used to temporarily override normal authorization rules to gain access to data in a case of emergency. Use of this override code will typically be monitored, and a procedure to verify its proper use may be triggered when used. <br/> </td> </tr> <tr> <td> 5</td> <td>         21 <a name="v3-ActCode-21"> </a> </td> <td> authorization confirmed</td> <td> Description: Indicates that the permissions have been externally verified and the request should be processed. <br/> </td> </tr> <tr> <td> 2</td> <td>   1 <a name="v3-ActCode-1"> </a> </td> <td> Therapy Appropriate</td> <td> Confirmed drug therapy appropriate <br/> </td> </tr> <tr> <td> 3</td> <td>     19 <a name="v3-ActCode-19"> </a> </td> <td> Consulted Supplier</td> <td> Consulted other supplier/pharmacy, therapy confirmed <br/> </td> </tr> <tr> <td> 3</td> <td>     2 <a name="v3-ActCode-2"> </a> </td> <td> Assessed Patient</td> <td> Assessed patient, therapy is appropriate <br/> </td> </tr> <tr> <td> 3</td> <td>     22 <a name="v3-ActCode-22"> </a> </td> <td> appropriate indication or diagnosis</td> <td> Description: The patient has the appropriate indication or diagnosis for the action to be taken. <br/> </td> </tr> <tr> <td> 3</td> <td>     23 <a name="v3-ActCode-23"> </a> </td> <td> prior therapy documented</td> <td> Description: It has been confirmed that the appropriate pre-requisite therapy has been tried. <br/> </td> </tr> <tr> <td> 3</td> <td>     3 <a name="v3-ActCode-3"> </a> </td> <td> Patient Explanation</td> <td> Patient gave adequate explanation <br/> </td> </tr> <tr> <td> 3</td> <td>     4 <a name="v3-ActCode-4"> </a> </td> <td> Consulted Other Source</td> <td> Consulted other supply source, therapy still appropriate <br/> </td> </tr> <tr> <td> 3</td> <td>     5 <a name="v3-ActCode-5"> </a> </td> <td> Consulted Prescriber</td> <td> Consulted prescriber, therapy confirmed <br/> </td> </tr> <tr> <td> 4</td> <td>       6 <a name="v3-ActCode-6"> </a> </td> <td> Prescriber Declined Change</td> <td> Consulted prescriber and recommended change, prescriber declined <br/> </td> </tr> <tr> <td> 3</td> <td>     7 <a name="v3-ActCode-7"> </a> </td> <td> Interacting Therapy No Longer Active/Planned</td> <td> Concurrent therapy triggering alert is no longer on-going or planned <br/> </td> </tr> <tr> <td> 2</td> <td>   14 <a name="v3-ActCode-14"> </a> </td> <td> Supply Appropriate</td> <td> Confirmed supply action appropriate <br/> </td> </tr> <tr> <td> 3</td> <td>     15 <a name="v3-ActCode-15"> </a> </td> <td> Replacement</td> <td> Patient's existing supply was lost/wasted <br/> </td> </tr> <tr> <td> 3</td> <td>     16 <a name="v3-ActCode-16"> </a> </td> <td> Vacation Supply</td> <td> Supply date is due to patient vacation <br/> </td> </tr> <tr> <td> 3</td> <td>     17 <a name="v3-ActCode-17"> </a> </td> <td> Weekend Supply</td> <td> Supply date is intended to carry patient over weekend <br/> </td> </tr> <tr> <td> 3</td> <td>     18 <a name="v3-ActCode-18"> </a> </td> <td> Leave of Absence</td> <td> Supply is intended for use during a leave of absence from an institution. <br/> </td> </tr> <tr> <td> 3</td> <td>     20 <a name="v3-ActCode-20"> </a> </td> <td> additional quantity on separate dispense</td> <td> Description: Supply is different than expected as an additional quantity has been supplied in a separate dispense. <br/> </td> </tr> <tr> <td> 2</td> <td>   8 <a name="v3-ActCode-8"> </a> </td> <td> Other Action Taken</td> <td> Order is performed as issued, but other action taken to mitigate potential adverse effects <br/> </td> </tr> <tr> <td> 3</td> <td>     10 <a name="v3-ActCode-10"> </a> </td> <td> Provided Patient Education</td> <td> Provided education or training to the patient on appropriate therapy use <br/> </td> </tr> <tr> <td> 3</td> <td>     11 <a name="v3-ActCode-11"> </a> </td> <td> Added Concurrent Therapy</td> <td> Instituted an additional therapy to mitigate potential negative effects <br/> </td> </tr> <tr> <td> 3</td> <td>     12 <a name="v3-ActCode-12"> </a> </td> <td> Temporarily Suspended Concurrent Therapy</td> <td> Suspended existing therapy that triggered interaction for the duration of this therapy <br/> </td> </tr> <tr> <td> 3</td> <td>     13 <a name="v3-ActCode-13"> </a> </td> <td> Stopped Concurrent Therapy</td> <td> Aborted existing therapy that triggered interaction. <br/> </td> </tr> <tr> <td> 3</td> <td>     9 <a name="v3-ActCode-9"> </a> </td> <td> Instituted Ongoing Monitoring Program</td> <td> Arranged to monitor patient for adverse effects <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActExposureCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActExposureCode"> </a> </td> <td> Concepts that identify the type or nature of exposure interaction. Examples include "household", "care giver", "intimate partner", "common space", "common substance", etc. to further describe the nature of interaction. <br/> </td> </tr> <tr> <td> 2</td> <td>   CHLDCARE <a name="v3-ActCode-CHLDCARE"> </a> </td> <td> Day care - Child care Interaction</td> <td> Description: Exposure participants' interaction occurred in a child care setting <br/> </td> </tr> <tr> <td> 2</td> <td>   CONVEYNC <a name="v3-ActCode-CONVEYNC"> </a> </td> <td> Common Conveyance Interaction</td> <td> Description: An interaction where the exposure participants traveled in/on the same vehicle (not necessarily concurrently, e.g. both are passengers of the same plane, but on different flights of that plane). <br/> </td> </tr> <tr> <td> 2</td> <td>   HLTHCARE <a name="v3-ActCode-HLTHCARE"> </a> </td> <td> Health Care Interaction - Not Patient Care</td> <td> Description: Exposure participants' interaction occurred during the course of health care delivery or in a health care delivery setting, but did not involve the direct provision of care (e.g. a janitor cleaning a patient's hospital room). <br/> </td> </tr> <tr> <td> 2</td> <td>   HOMECARE <a name="v3-ActCode-HOMECARE"> </a> </td> <td> Care Giver Interaction</td> <td> Description: Exposure interaction occurred in context of one providing care for the other, i.e. a babysitter providing care for a child, a home-care aide providing assistance to a paraplegic. <br/> </td> </tr> <tr> <td> 2</td> <td>   HOSPPTNT <a name="v3-ActCode-HOSPPTNT"> </a> </td> <td> Hospital Patient Interaction</td> <td> Description: Exposure participants' interaction occurred when both were patients being treated in the same (acute) health care delivery facility. <br/> </td> </tr> <tr> <td> 2</td> <td>   HOSPVSTR <a name="v3-ActCode-HOSPVSTR"> </a> </td> <td> Hospital Visitor Interaction</td> <td> Description: Exposure participants' interaction occurred when one visited the other who was a patient being treated in a health care delivery facility. <br/> </td> </tr> <tr> <td> 2</td> <td>   HOUSEHLD <a name="v3-ActCode-HOUSEHLD"> </a> </td> <td> Household Interaction</td> <td> Description: Exposure interaction occurred in context of domestic interaction, i.e. both participants reside in the same household. <br/> </td> </tr> <tr> <td> 2</td> <td>   INMATE <a name="v3-ActCode-INMATE"> </a> </td> <td> Inmate Interaction</td> <td> Description: Exposure participants' interaction occurred in the course of one or both participants being incarcerated at a correctional facility <br/> </td> </tr> <tr> <td> 2</td> <td>   INTIMATE <a name="v3-ActCode-INTIMATE"> </a> </td> <td> Intimate Interaction</td> <td> Description: Exposure interaction was intimate, i.e. participants are intimate companions (e.g. spouses, domestic partners). <br/> </td> </tr> <tr> <td> 2</td> <td>   LTRMCARE <a name="v3-ActCode-LTRMCARE"> </a> </td> <td> Long Term Care Facility Interaction</td> <td> Description: Exposure participants' interaction occurred in the course of one or both participants being resident at a long term care facility (second participant may be a visitor, worker, resident or a physical place or object within the facility). <br/> </td> </tr> <tr> <td> 2</td> <td>   PLACE <a name="v3-ActCode-PLACE"> </a> </td> <td> Common Space Interaction</td> <td> Description: An interaction where the exposure participants were both present in the same location/place/space. <br/> </td> </tr> <tr> <td> 2</td> <td>   PTNTCARE <a name="v3-ActCode-PTNTCARE"> </a> </td> <td> Health Care Interaction - Patient Care</td> <td> Description: Exposure participants' interaction occurred during the course of health care delivery by a provider (e.g. a physician treating a patient in her office). <br/> </td> </tr> <tr> <td> 2</td> <td>   SCHOOL2 <a name="v3-ActCode-SCHOOL2"> </a> </td> <td> School Interaction</td> <td> Description: Exposure participants' interaction occurred in an academic setting (e.g., participants are fellow students, or student and teacher). <br/> </td> </tr> <tr> <td> 2</td> <td>   SOCIAL2 <a name="v3-ActCode-SOCIAL2"> </a> </td> <td> Social/Extended Family Interaction</td> <td> Description: An interaction where the exposure participants are social associates or members of the same extended family <br/> </td> </tr> <tr> <td> 2</td> <td>   SUBSTNCE <a name="v3-ActCode-SUBSTNCE"> </a> </td> <td> Common Substance Interaction</td> <td> Description: An interaction where the exposure participants shared or co-used a common substance (e.g. drugs, needles, or common food item). <br/> </td> </tr> <tr> <td> 2</td> <td>   TRAVINT <a name="v3-ActCode-TRAVINT"> </a> </td> <td> Common Travel Interaction</td> <td> Description: An interaction where the exposure participants traveled together in/on the same vehicle/trip (e.g. concurrent co-passengers). <br/> </td> </tr> <tr> <td> 2</td> <td>   WORK2 <a name="v3-ActCode-WORK2"> </a> </td> <td> Work Interaction</td> <td> Description: Exposure interaction occurred in a work setting, i.e. participants are co-workers. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActFinancialTransactionCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActFinancialTransactionCode"> </a> </td> <td/> </tr> <tr> <td> 2</td> <td>   CHRG <a name="v3-ActCode-CHRG"> </a> </td> <td> Standard Charge</td> <td> A type of transaction that represents a charge for a service or product. Expressed in monetary terms. <br/> </td> </tr> <tr> <td> 2</td> <td>   REV <a name="v3-ActCode-REV"> </a> </td> <td> Standard Charge Reversal</td> <td> A type of transaction that represents a reversal of a previous charge for a service or product. Expressed in monetary terms. It has the opposite effect of a standard charge. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActIncidentCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActIncidentCode"> </a> </td> <td> Set of codes indicating the type of incident or accident. <br/> </td> </tr> <tr> <td> 2</td> <td>   MVA <a name="v3-ActCode-MVA"> </a> </td> <td> Motor vehicle accident</td> <td> Incident or accident as the result of a motor vehicle accident <br/> </td> </tr> <tr> <td> 2</td> <td>   SCHOOL <a name="v3-ActCode-SCHOOL"> </a> </td> <td> School Accident</td> <td> Incident or accident is the result of a school place accident. <br/> </td> </tr> <tr> <td> 2</td> <td>   SPT <a name="v3-ActCode-SPT"> </a> </td> <td> Sporting Accident</td> <td> Incident or accident is the result of a sporting accident. <br/> </td> </tr> <tr> <td> 2</td> <td>   WPA <a name="v3-ActCode-WPA"> </a> </td> <td> Workplace accident</td> <td> Incident or accident is the result of a work place accident <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInformationAccessCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationAccessCode"> </a> </td> <td> Description: The type of health information to which the subject of the information or the subject's delegate consents or dissents. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACADR <a name="v3-ActCode-ACADR"> </a> </td> <td> adverse drug reaction access</td> <td> Description: Provide consent to collect, use, disclose, or access adverse drug reaction information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACALL <a name="v3-ActCode-ACALL"> </a> </td> <td> all access</td> <td> Description: Provide consent to collect, use, disclose, or access all information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACALLG <a name="v3-ActCode-ACALLG"> </a> </td> <td> allergy access</td> <td> Description: Provide consent to collect, use, disclose, or access allergy information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACCONS <a name="v3-ActCode-ACCONS"> </a> </td> <td> informational consent access</td> <td> Description: Provide consent to collect, use, disclose, or access informational consent information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACDEMO <a name="v3-ActCode-ACDEMO"> </a> </td> <td> demographics access</td> <td> Description: Provide consent to collect, use, disclose, or access demographics information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACDI <a name="v3-ActCode-ACDI"> </a> </td> <td> diagnostic imaging access</td> <td> Description: Provide consent to collect, use, disclose, or access diagnostic imaging information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACIMMUN <a name="v3-ActCode-ACIMMUN"> </a> </td> <td> immunization access</td> <td> Description: Provide consent to collect, use, disclose, or access immunization information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACLAB <a name="v3-ActCode-ACLAB"> </a> </td> <td> lab test result access</td> <td> Description: Provide consent to collect, use, disclose, or access lab test result information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACMED <a name="v3-ActCode-ACMED"> </a> </td> <td> medication access</td> <td> Description: Provide consent to collect, use, disclose, or access medical condition information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACMEDC <a name="v3-ActCode-ACMEDC"> </a> </td> <td> medical condition access</td> <td> Definition: Provide consent to view or access medical condition information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACMEN <a name="v3-ActCode-ACMEN"> </a> </td> <td> mental health access</td> <td> Description:Provide consent to collect, use, disclose, or access mental health information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACOBS <a name="v3-ActCode-ACOBS"> </a> </td> <td> common observations access</td> <td> Description: Provide consent to collect, use, disclose, or access common observation information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACPOLPRG <a name="v3-ActCode-ACPOLPRG"> </a> </td> <td> policy or program information access</td> <td> Description: Provide consent to collect, use, disclose, or access coverage policy or program for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACPROV <a name="v3-ActCode-ACPROV"> </a> </td> <td> provider information access</td> <td> Description: Provide consent to collect, use, disclose, or access provider information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACPSERV <a name="v3-ActCode-ACPSERV"> </a> </td> <td> professional service access</td> <td> Description: Provide consent to collect, use, disclose, or access professional service information for a patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   ACSUBSTAB <a name="v3-ActCode-ACSUBSTAB"> </a> </td> <td> substance abuse access</td> <td> Description:Provide consent to collect, use, disclose, or access substance abuse information for a patient. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInformationAccessContextCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationAccessContextCode"> </a> </td> <td> Concepts conveying the context in which authorization given under jurisdictional law, by organizational policy, or by a patient consent directive permits the collection, access, use or disclosure of specified patient health information. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFAUT <a name="v3-ActCode-INFAUT"> </a> </td> <td> authorized information transfer</td> <td> Authorization to collect, access, use, or disclose specified patient health information in accordance with jurisdictional law, organizational policy, or a patient's consent directive, which may be implied, deemed, opt-in, opt-out, or explicit. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFCON <a name="v3-ActCode-INFCON"> </a> </td> <td> after explicit consent</td> <td> Authorization to collect, access, use, or disclose specified patient health information as explicitly consented to by the subject of the information or the subject's representative. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFCRT <a name="v3-ActCode-INFCRT"> </a> </td> <td> only on court order</td> <td> Authorization to collect, access, use, or disclose specified patient health information in accordance with judicial system protocol, such as in the case of a subpoena or court order. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFDNG <a name="v3-ActCode-INFDNG"> </a> </td> <td> only if danger to others</td> <td> Authorization to collect, access, use, or disclose specified patient health information where deemed necessary to avert potential danger to other persons in accordance with jurisdictional law, organizational policy, or standards of practice. For example, disclosure about a person threatening violence. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFEMER <a name="v3-ActCode-INFEMER"> </a> </td> <td> only in an emergency</td> <td> Authorization to collect, access, use, or disclose specified patient health information in accordance with emergency information transfer protocol dictated by jurisdictional law, organization policy, or standards of practice. For example, sharing of health information during disaster response. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFPWR <a name="v3-ActCode-INFPWR"> </a> </td> <td> only if public welfare risk</td> <td> Authorization to collect, access, use, or disclose specified patient health information necessary to avert potential public welfare risk in accordance with jurisdictional law, organizational policy, or standards of practice. For example, reporting that a person is a victim of abuse or demonstrating suicidal tendencies. <br/> </td> </tr> <tr> <td> 2</td> <td>   INFREG <a name="v3-ActCode-INFREG"> </a> </td> <td> regulatory information transfer</td> <td> Authorization to collect, access, use, or disclose specified patient health information for public health, welfare, and safety purposes in accordance with jurisdictional law, organizational policy, or standards of practice. For example, public health reporting of notifiable conditions. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInformationCategoryCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationCategoryCode"> </a> </td> <td> Definition:Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions. <br/> </td> </tr> <tr> <td> 2</td> <td>   ALLCAT <a name="v3-ActCode-ALLCAT"> </a> </td> <td> all categories</td> <td> Description: All patient information. <br/> </td> </tr> <tr> <td> 2</td> <td>   ALLGCAT <a name="v3-ActCode-ALLGCAT"> </a> </td> <td> allergy category</td> <td> Definition:All information pertaining to a patient's allergy and intolerance records. <br/> </td> </tr> <tr> <td> 2</td> <td>   ARCAT <a name="v3-ActCode-ARCAT"> </a> </td> <td> adverse drug reaction category</td> <td> Description: All information pertaining to a patient's adverse drug reactions. <br/> </td> </tr> <tr> <td> 2</td> <td>   COBSCAT <a name="v3-ActCode-COBSCAT"> </a> </td> <td> common observation category</td> <td> Definition:All information pertaining to a patient's common observation records (height, weight, blood pressure, temperature, etc.). <br/> </td> </tr> <tr> <td> 2</td> <td>   DEMOCAT <a name="v3-ActCode-DEMOCAT"> </a> </td> <td> demographics category</td> <td> Definition:All information pertaining to a patient's demographics (such as name, date of birth, gender, address, etc). <br/> </td> </tr> <tr> <td> 2</td> <td>   DICAT <a name="v3-ActCode-DICAT"> </a> </td> <td> diagnostic image category</td> <td> Definition:All information pertaining to a patient's diagnostic image records (orders & results). <br/> </td> </tr> <tr> <td> 2</td> <td>   IMMUCAT <a name="v3-ActCode-IMMUCAT"> </a> </td> <td> immunization category</td> <td> Definition:All information pertaining to a patient's vaccination records. <br/> </td> </tr> <tr> <td> 2</td> <td>   LABCAT <a name="v3-ActCode-LABCAT"> </a> </td> <td> lab test category</td> <td> Description: All information pertaining to a patient's lab test records (orders & results) <br/> </td> </tr> <tr> <td> 2</td> <td>   MEDCCAT <a name="v3-ActCode-MEDCCAT"> </a> </td> <td> medical condition category</td> <td> Definition:All information pertaining to a patient's medical condition records. <br/> </td> </tr> <tr> <td> 2</td> <td>   MENCAT <a name="v3-ActCode-MENCAT"> </a> </td> <td> mental health category</td> <td> Description: All information pertaining to a patient's mental health records. <br/> </td> </tr> <tr> <td> 2</td> <td>   PSVCCAT <a name="v3-ActCode-PSVCCAT"> </a> </td> <td> professional service category</td> <td> Definition:All information pertaining to a patient's professional service records (such as smoking cessation, counseling, medication review, mental health). <br/> </td> </tr> <tr> <td> 2</td> <td>   RXCAT <a name="v3-ActCode-RXCAT"> </a> </td> <td> medication category</td> <td> Definition:All information pertaining to a patient's medication records (orders, dispenses and other active medications). <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInvoiceElementCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceElementCode"> </a> </td> <td> Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInvoiceAdjudicationPaymentCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceAdjudicationPaymentCode"> </a> </td> <td> Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee and other cost elements such as bonus, retroactive adjustment and transaction fees. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceAdjudicationPaymentGroupCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceAdjudicationPaymentGroupCode"> </a> </td> <td> Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc. <br/> </td> </tr> <tr> <td> 4</td> <td>       ALEC <a name="v3-ActCode-ALEC"> </a> </td> <td> alternate electronic</td> <td> Payment initiated by the payor as the result of adjudicating a submitted invoice that arrived to the payor from an electronic source that did not provide a conformant set of HL7 messages (e.g. web claim submission). <br/> </td> </tr> <tr> <td> 4</td> <td>       BONUS <a name="v3-ActCode-BONUS"> </a> </td> <td> bonus</td> <td> Bonus payments based on performance, volume, etc. as agreed to by the payor. <br/> </td> </tr> <tr> <td> 4</td> <td>       CFWD <a name="v3-ActCode-CFWD"> </a> </td> <td> carry forward adjusment</td> <td> An amount still owing to the payor but the payment is 0$ and this cannot be settled until a future payment is made. <br/> </td> </tr> <tr> <td> 4</td> <td>       EDU <a name="v3-ActCode-EDU"> </a> </td> <td> education fees</td> <td> Fees deducted on behalf of a payee for tuition and continuing education. <br/> </td> </tr> <tr> <td> 4</td> <td>       EPYMT <a name="v3-ActCode-EPYMT"> </a> </td> <td> early payment fee</td> <td> Fees deducted on behalf of a payee for charges based on a shorter payment frequency (i.e. next day versus biweekly payments. <br/> </td> </tr> <tr> <td> 4</td> <td>       GARN <a name="v3-ActCode-GARN"> </a> </td> <td> garnishee</td> <td> Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. <br/> </td> </tr> <tr> <td> 4</td> <td>       INVOICE <a name="v3-ActCode-INVOICE"> </a> </td> <td> submitted invoice</td> <td> Payment is based on a payment intent for a previously submitted Invoice, based on formal adjudication results.. <br/> </td> </tr> <tr> <td> 4</td> <td>       PINV <a name="v3-ActCode-PINV"> </a> </td> <td> paper invoice</td> <td> Payment initiated by the payor as the result of adjudicating a paper (original, may have been faxed) invoice. <br/> </td> </tr> <tr> <td> 4</td> <td>       PPRD <a name="v3-ActCode-PPRD"> </a> </td> <td> prior period adjustment</td> <td> An amount that was owed to the payor as indicated, by a carry forward adjusment, in a previous payment advice <br/> </td> </tr> <tr> <td> 4</td> <td>       PROA <a name="v3-ActCode-PROA"> </a> </td> <td> professional association deduction</td> <td> Professional association fee that is collected by the payor from the practitioner/provider on behalf of the association <br/> </td> </tr> <tr> <td> 4</td> <td>       RECOV <a name="v3-ActCode-RECOV"> </a> </td> <td> recovery</td> <td> Retroactive adjustment such as fee rate adjustment due to contract negotiations. <br/> </td> </tr> <tr> <td> 4</td> <td>       RETRO <a name="v3-ActCode-RETRO"> </a> </td> <td> retro adjustment</td> <td> Bonus payments based on performance, volume, etc. as agreed to by the payor. <br/> </td> </tr> <tr> <td> 4</td> <td>       TRAN <a name="v3-ActCode-TRAN"> </a> </td> <td> transaction fee</td> <td> Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceAdjudicationPaymentSummaryCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceAdjudicationPaymentSummaryCode"> </a> </td> <td> Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee, etc. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#CONT">CONT</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#DAY">DAY</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#LOC">LOC</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#MONTH">MONTH</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#PERIOD">PERIOD</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#PROV">PROV</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#WEEK">WEEK</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#YEAR">YEAR</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       INVTYPE <a name="v3-ActCode-INVTYPE"> </a> </td> <td> invoice type</td> <td> Transaction counts and value totals by invoice type (e.g. RXDINV - Pharmacy Dispense) <br/> </td> </tr> <tr> <td> 4</td> <td>       PAYEE <a name="v3-ActCode-PAYEE"> </a> </td> <td> payee</td> <td> Transaction counts and value totals by each instance of an invoice payee. <br/> </td> </tr> <tr> <td> 4</td> <td>       PAYOR <a name="v3-ActCode-PAYOR"> </a> </td> <td> payor</td> <td> Transaction counts and value totals by each instance of an invoice payor. <br/> </td> </tr> <tr> <td> 4</td> <td>       SENDAPP <a name="v3-ActCode-SENDAPP"> </a> </td> <td> sending application</td> <td> Transaction counts and value totals by each instance of a messaging application on a single processor. It is a registered identifier known to the receivers. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInvoiceDetailCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailCode"> </a> </td> <td> Codes representing a service or product that is being invoiced (billed). The code can represent such concepts as "office visit", "drug X", "wheelchair" and other billable items such as taxes, service charges and discounts. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceDetailClinicalProductCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailClinicalProductCode"> </a> </td> <td> An identifying data string for healthcare products. <br/> </td> </tr> <tr> <td> 4</td> <td>       UNSPSC <a name="v3-ActCode-UNSPSC"> </a> </td> <td> United Nations Standard Products and Services Classification</td> <td> Description:United Nations Standard Products and Services Classification, managed by Uniform Code Council (UCC): www.unspsc.org <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceDetailDrugProductCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailDrugProductCode"> </a> </td> <td> An identifying data string for A substance used as a medication or in the preparation of medication. <br/> </td> </tr> <tr> <td> 4</td> <td>       GTIN <a name="v3-ActCode-GTIN"> </a> </td> <td> Global Trade Item Number</td> <td> Description:Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council). <br/> </td> </tr> <tr> <td> 4</td> <td>       UPC <a name="v3-ActCode-UPC"> </a> </td> <td> Universal Product Code</td> <td> Description:Universal Product Code is one of a wide variety of bar code languages widely used in the United States and Canada for items in stores. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceDetailGenericCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailGenericCode"> </a> </td> <td> The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActInvoiceDetailGenericAdjudicatorCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailGenericAdjudicatorCode"> </a> </td> <td> The billable item codes to identify adjudicator specified components to the total billing of a claim. <br/> </td> </tr> <tr> <td> 5</td> <td>         COIN <a name="v3-ActCode-COIN"> </a> </td> <td> coinsurance</td> <td> That portion of the eligible charges which a covered party must pay for each service and/or product. It is a percentage of the eligible amount for the service/product that is typically charged after the covered party has met the policy deductible. This amount represents the covered party's coinsurance that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. <br/> </td> </tr> <tr> <td> 5</td> <td>         COPAYMENT <a name="v3-ActCode-COPAYMENT"> </a> </td> <td> patient co-pay</td> <td> That portion of the eligible charges which a covered party must pay for each service and/or product. It is a defined amount per service/product of the eligible amount for the service/product. This amount represents the covered party's copayment that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. <br/> </td> </tr> <tr> <td> 5</td> <td>         DEDUCTIBLE <a name="v3-ActCode-DEDUCTIBLE"> </a> </td> <td> deductible</td> <td> That portion of the eligible charges which a covered party must pay in a particular period (e.g. annual) before the benefits are payable by the adjudicator. This amount represents the covered party's deductible that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results. <br/> </td> </tr> <tr> <td> 5</td> <td>         PAY <a name="v3-ActCode-PAY"> </a> </td> <td> payment</td> <td> The guarantor, who may be the patient, pays the entire charge for a service. Reasons for such action may include: there is no insurance coverage for the service (e.g. cosmetic surgery); the patient wishes to self-pay for the service; or the insurer denies payment for the service due to contractual provisions such as the need for prior authorization. <br/> </td> </tr> <tr> <td> 5</td> <td>         SPEND <a name="v3-ActCode-SPEND"> </a> </td> <td> spend down</td> <td> That total amount of the eligible charges which a covered party must periodically pay for services and/or products prior to the Medicaid program providing any coverage. This amount represents the covered party's spend down that is applied to a particular adjudication result. It is expressed as a negative dollar amount in adjudication results <br/> </td> </tr> <tr> <td> 5</td> <td>         COINS <a name="v3-ActCode-COINS"> </a> </td> <td> co-insurance</td> <td> The covered party pays a percentage of the cost of covered services. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActInvoiceDetailGenericModifierCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailGenericModifierCode"> </a> </td> <td> The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee. <br/> </td> </tr> <tr> <td> 5</td> <td>         AFTHRS <a name="v3-ActCode-AFTHRS"> </a> </td> <td> non-normal hours</td> <td> Premium paid on service fees in compensation for practicing outside of normal working hours. <br/> </td> </tr> <tr> <td> 5</td> <td>         ISOL <a name="v3-ActCode-ISOL"> </a> </td> <td> isolation allowance</td> <td> Premium paid on service fees in compensation for practicing in a remote location. <br/> </td> </tr> <tr> <td> 5</td> <td>         OOO <a name="v3-ActCode-OOO"> </a> </td> <td> out of office</td> <td> Premium paid on service fees in compensation for practicing at a location other than normal working location. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActInvoiceDetailGenericProviderCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailGenericProviderCode"> </a> </td> <td> The billable item codes to identify provider supplied charges or changes to the total billing of a claim. <br/> </td> </tr> <tr> <td> 5</td> <td>         CANCAPT <a name="v3-ActCode-CANCAPT"> </a> </td> <td> cancelled appointment</td> <td> A charge to compensate the provider when a patient cancels an appointment with insufficient time for the provider to make another appointment with another patient. <br/> </td> </tr> <tr> <td> 5</td> <td>         DSC <a name="v3-ActCode-DSC"> </a> </td> <td> discount</td> <td> A reduction in the amount charged as a percentage of the amount. For example a 5% discount for volume purchase. <br/> </td> </tr> <tr> <td> 5</td> <td>         ESA <a name="v3-ActCode-ESA"> </a> </td> <td> extraordinary service assessment</td> <td> A premium on a service fee is requested because, due to extenuating circumstances, the service took an extraordinary amount of time or supplies. <br/> </td> </tr> <tr> <td> 5</td> <td>         FFSTOP <a name="v3-ActCode-FFSTOP"> </a> </td> <td> fee for service top off</td> <td> Under agreement between the parties (payor and provider), a guaranteed level of income is established for the provider over a specific, pre-determined period of time. The normal course of business for the provider is submission of fee-for-service claims. Should the fee-for-service income during the specified period of time be less than the agreed to amount, a top-up amount is paid to the provider equal to the difference between the fee-for-service total and the guaranteed income amount for that period of time. The details of the agreement may specify (or not) a requirement for repayment to the payor in the event that the fee-for-service income exceeds the guaranteed amount. <br/> </td> </tr> <tr> <td> 5</td> <td>         FNLFEE <a name="v3-ActCode-FNLFEE"> </a> </td> <td> final fee</td> <td> Anticipated or actual final fee associated with treating a patient. <br/> </td> </tr> <tr> <td> 5</td> <td>         FRSTFEE <a name="v3-ActCode-FRSTFEE"> </a> </td> <td> first fee</td> <td> Anticipated or actual initial fee associated with treating a patient. <br/> </td> </tr> <tr> <td> 5</td> <td>         MARKUP <a name="v3-ActCode-MARKUP"> </a> </td> <td> markup or up-charge</td> <td> An increase in the amount charged as a percentage of the amount. For example, 12% markup on product cost. <br/> </td> </tr> <tr> <td> 5</td> <td>         MISSAPT <a name="v3-ActCode-MISSAPT"> </a> </td> <td> missed appointment</td> <td> A charge to compensate the provider when a patient does not show for an appointment. <br/> </td> </tr> <tr> <td> 5</td> <td>         PERFEE <a name="v3-ActCode-PERFEE"> </a> </td> <td> periodic fee</td> <td> Anticipated or actual periodic fee associated with treating a patient. For example, expected billing cycle such as monthly, quarterly. The actual period (e.g. monthly, quarterly) is specified in the unit quantity of the Invoice Element. <br/> </td> </tr> <tr> <td> 5</td> <td>         PERMBNS <a name="v3-ActCode-PERMBNS"> </a> </td> <td> performance bonus</td> <td> The amount for a performance bonus that is being requested from a payor for the performance of certain services (childhood immunizations, influenza immunizations, mammograms, pap smears) on a sliding scale. That is, for 90% of childhood immunizations to a maximum of $2200/yr. An invoice is created at the end of the service period (one year) and a code is submitted indicating the percentage achieved and the dollar amount claimed. <br/> </td> </tr> <tr> <td> 5</td> <td>         RESTOCK <a name="v3-ActCode-RESTOCK"> </a> </td> <td> restocking fee</td> <td> A charge is requested because the patient failed to pick up the item and it took an amount of time to return it to stock for future use. <br/> </td> </tr> <tr> <td> 5</td> <td>         TRAVEL <a name="v3-ActCode-TRAVEL"> </a> </td> <td> travel</td> <td> A charge to cover the cost of travel time and/or cost in conjuction with providing a service or product. It may be charged per kilometer or per hour based on the effective agreement. <br/> </td> </tr> <tr> <td> 5</td> <td>         URGENT <a name="v3-ActCode-URGENT"> </a> </td> <td> urgent</td> <td> Premium paid on service fees in compensation for providing an expedited response to an urgent situation. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActInvoiceDetailTaxCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailTaxCode"> </a> </td> <td> The billable item codes to identify modifications to a billable item charge by a tax factor applied to the amount. As for example 7% provincial sales tax. <br/> </td> </tr> <tr> <td> 5</td> <td>         FST <a name="v3-ActCode-FST"> </a> </td> <td> federal sales tax</td> <td> Federal tax on transactions such as the Goods and Services Tax (GST) <br/> </td> </tr> <tr> <td> 5</td> <td>         HST <a name="v3-ActCode-HST"> </a> </td> <td> harmonized sales Tax</td> <td> Joint Federal/Provincial Sales Tax <br/> </td> </tr> <tr> <td> 5</td> <td>         PST <a name="v3-ActCode-PST"> </a> </td> <td> provincial/state sales tax</td> <td> Tax levied by the provincial or state jurisdiction such as Provincial Sales Tax <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceDetailPreferredAccommodationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailPreferredAccommodationCode"> </a> </td> <td> An identifying data string for medical facility accommodations. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActEncounterAccommodationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActEncounterAccommodationCode"> </a> </td> <td> Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. <br/> </td> </tr> <tr> <td> 5</td> <td>         <span style="color: grey"> <i> (_HL7AccommodationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_HL7AccommodationCode"> </a> </td> <td> Description:Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type. <br/> </td> </tr> <tr> <td> 6</td> <td>           I <a name="v3-ActCode-I"> </a> </td> <td> Isolation</td> <td> Accommodations used in the care of diseases that are transmitted through casual contact or respiratory transmission. <br/> </td> </tr> <tr> <td> 6</td> <td>           P <a name="v3-ActCode-P"> </a> </td> <td> Private</td> <td> Accommodations in which there is only 1 bed. <br/> </td> </tr> <tr> <td> 6</td> <td>           S <a name="v3-ActCode-S"> </a> </td> <td> Suite</td> <td> Uniquely designed and elegantly decorated accommodations with many amenities available for an additional charge. <br/> </td> </tr> <tr> <td> 6</td> <td>           SP <a name="v3-ActCode-SP"> </a> </td> <td> Semi-private</td> <td> Accommodations in which there are 2 beds. <br/> </td> </tr> <tr> <td> 6</td> <td>           W <a name="v3-ActCode-W"> </a> </td> <td> Ward</td> <td> Accommodations in which there are 3 or more beds. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceDetailClinicalServiceCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceDetailClinicalServiceCode"> </a> </td> <td> An identifying data string for healthcare procedures. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInvoiceGroupCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceGroupCode"> </a> </td> <td> Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. <br/> Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceInterGroupCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceInterGroupCode"> </a> </td> <td> Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. <br/> Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. <br/> The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPNDDRGING <a name="v3-ActCode-CPNDDRGING"> </a> </td> <td> compound drug invoice group</td> <td> A grouping of invoice element groups and details including the ones specifying the compound ingredients being invoiced. It may also contain generic detail items such as markup. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPNDINDING <a name="v3-ActCode-CPNDINDING"> </a> </td> <td> compound ingredient invoice group</td> <td> A grouping of invoice element details including the one specifying an ingredient drug being invoiced. It may also contain generic detail items such as tax or markup. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPNDSUPING <a name="v3-ActCode-CPNDSUPING"> </a> </td> <td> compound supply invoice group</td> <td> A grouping of invoice element groups and details including the ones specifying the compound supplies being invoiced. It may also contain generic detail items such as markup. <br/> </td> </tr> <tr> <td> 4</td> <td>       DRUGING <a name="v3-ActCode-DRUGING"> </a> </td> <td> drug invoice group</td> <td> A grouping of invoice element details including the one specifying the drug being invoiced. It may also contain generic detail items such as markup. <br/> </td> </tr> <tr> <td> 4</td> <td>       FRAMEING <a name="v3-ActCode-FRAMEING"> </a> </td> <td> frame invoice group</td> <td> A grouping of invoice element details including the ones specifying the frame fee and the frame dispensing cost that are being invoiced. <br/> </td> </tr> <tr> <td> 4</td> <td>       LENSING <a name="v3-ActCode-LENSING"> </a> </td> <td> lens invoice group</td> <td> A grouping of invoice element details including the ones specifying the lens fee and the lens dispensing cost that are being invoiced. <br/> </td> </tr> <tr> <td> 4</td> <td>       PRDING <a name="v3-ActCode-PRDING"> </a> </td> <td> product invoice group</td> <td> A grouping of invoice element details including the one specifying the product (good or supply) being invoiced. It may also contain generic detail items such as tax or discount. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActInvoiceRootGroupCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceRootGroupCode"> </a> </td> <td> Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. <br/> Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. <br/> Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPINV <a name="v3-ActCode-CPINV"> </a> </td> <td> clinical product invoice</td> <td> Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s). <br/> For example, a crutch or a wheelchair. <br/> </td> </tr> <tr> <td> 4</td> <td>       CSINV <a name="v3-ActCode-CSINV"> </a> </td> <td> clinical service invoice</td> <td> Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. <br/> [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. <br/> For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). <br/> [2] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services. The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together. <br/> For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. <br/> [3] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time. <br/> For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month). <br/> </td> </tr> <tr> <td> 4</td> <td>       CSPINV <a name="v3-ActCode-CSPINV"> </a> </td> <td> clinical service and product</td> <td> A clinical Invoice Grouping consisting of one or more services and one or more product. Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts). <br/> All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. <br/> For example , a brace (product) invoiced together with the fitting (service). <br/> </td> </tr> <tr> <td> 4</td> <td>       FININV <a name="v3-ActCode-FININV"> </a> </td> <td> financial invoice</td> <td> Invoice Grouping without clinical justification. These will not require identification of participants and associations from a clinical context such as patient and provider. <br/> Examples are interest charges and mileage. <br/> </td> </tr> <tr> <td> 4</td> <td>       OHSINV <a name="v3-ActCode-OHSINV"> </a> </td> <td> oral health service</td> <td> A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts). <br/> All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. <br/> </td> </tr> <tr> <td> 4</td> <td>       PAINV <a name="v3-ActCode-PAINV"> </a> </td> <td> preferred accommodation invoice</td> <td> HealthCare facility preferred accommodation invoice. <br/> </td> </tr> <tr> <td> 4</td> <td>       RXCINV <a name="v3-ActCode-RXCINV"> </a> </td> <td> Rx compound invoice</td> <td> Pharmacy dispense invoice for a compound. <br/> </td> </tr> <tr> <td> 4</td> <td>       RXDINV <a name="v3-ActCode-RXDINV"> </a> </td> <td> Rx dispense invoice</td> <td> Pharmacy dispense invoice not involving a compound <br/> </td> </tr> <tr> <td> 4</td> <td>       SBFINV <a name="v3-ActCode-SBFINV"> </a> </td> <td> sessional or block fee invoice</td> <td> Clinical services invoice where the Invoice Group contains one billable item for multiple clinical services in one or more sessions. <br/> </td> </tr> <tr> <td> 4</td> <td>       VRXINV <a name="v3-ActCode-VRXINV"> </a> </td> <td> vision dispense invoice</td> <td> Vision dispense invoice for up to 2 lens (left and right), frame and optional discount. Eye exams are invoiced as a clinical service invoice. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInvoiceElementSummaryCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceElementSummaryCode"> </a> </td> <td> Identifies the different types of summary information that can be reported by queries dealing with Statement of Financial Activity (SOFA). The summary information is generally used to help resolve balance discrepancies between providers and payors. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_InvoiceElementAdjudicated)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_InvoiceElementAdjudicated"> </a> </td> <td> Total counts and total net amounts adjudicated for all Invoice Groupings that were adjudicated within a time period based on the adjudication date of the Invoice Grouping. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFPPELAT <a name="v3-ActCode-ADNFPPELAT"> </a> </td> <td> adjud. nullified prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFPPELCT <a name="v3-ActCode-ADNFPPELCT"> </a> </td> <td> adjud. nullified prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFPPMNAT <a name="v3-ActCode-ADNFPPMNAT"> </a> </td> <td> adjud. nullified prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFPPMNCT <a name="v3-ActCode-ADNFPPMNCT"> </a> </td> <td> adjud. nullified prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFSPELAT <a name="v3-ActCode-ADNFSPELAT"> </a> </td> <td> adjud. nullified same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFSPELCT <a name="v3-ActCode-ADNFSPELCT"> </a> </td> <td> adjud. nullified same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently nullified in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFSPMNAT <a name="v3-ActCode-ADNFSPMNAT"> </a> </td> <td> adjud. nullified same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNFSPMNCT <a name="v3-ActCode-ADNFSPMNCT"> </a> </td> <td> adjud. nullified same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date), subsequently cancelled in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPPPELAT <a name="v3-ActCode-ADNPPPELAT"> </a> </td> <td> adjud. non-payee payable prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPPPELCT <a name="v3-ActCode-ADNPPPELCT"> </a> </td> <td> adjud. non-payee payable prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPPPMNAT <a name="v3-ActCode-ADNPPPMNAT"> </a> </td> <td> adjud. non-payee payable prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPPPMNCT <a name="v3-ActCode-ADNPPPMNCT"> </a> </td> <td> adjud. non-payee payable prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPSPELAT <a name="v3-ActCode-ADNPSPELAT"> </a> </td> <td> adjud. non-payee payable same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPSPELCT <a name="v3-ActCode-ADNPSPELCT"> </a> </td> <td> adjud. non-payee payable same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPSPMNAT <a name="v3-ActCode-ADNPSPMNAT"> </a> </td> <td> adjud. non-payee payable same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADNPSPMNCT <a name="v3-ActCode-ADNPSPMNCT"> </a> </td> <td> adjud. non-payee payable same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPPPELAT <a name="v3-ActCode-ADPPPPELAT"> </a> </td> <td> adjud. payee payable prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPPPELCT <a name="v3-ActCode-ADPPPPELCT"> </a> </td> <td> adjud. payee payable prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPPPMNAT <a name="v3-ActCode-ADPPPPMNAT"> </a> </td> <td> adjud. payee payable prior-period manual amout</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPPPMNCT <a name="v3-ActCode-ADPPPPMNCT"> </a> </td> <td> adjud. payee payable prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPSPELAT <a name="v3-ActCode-ADPPSPELAT"> </a> </td> <td> adjud. payee payable same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPSPELCT <a name="v3-ActCode-ADPPSPELCT"> </a> </td> <td> adjud. payee payable same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPSPMNAT <a name="v3-ActCode-ADPPSPMNAT"> </a> </td> <td> adjud. payee payable same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADPPSPMNCT <a name="v3-ActCode-ADPPSPMNCT"> </a> </td> <td> adjud. payee payable same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as payable during the specified time period (based on adjudication date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFPPELAT <a name="v3-ActCode-ADRFPPELAT"> </a> </td> <td> adjud. refused prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFPPELCT <a name="v3-ActCode-ADRFPPELCT"> </a> </td> <td> adjud. refused prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFPPMNAT <a name="v3-ActCode-ADRFPPMNAT"> </a> </td> <td> adjud. refused prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFPPMNCT <a name="v3-ActCode-ADRFPPMNCT"> </a> </td> <td> adjud. refused prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as refused prior to the specified time period (based on adjudication date) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFSPELAT <a name="v3-ActCode-ADRFSPELAT"> </a> </td> <td> adjud. refused same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFSPELCT <a name="v3-ActCode-ADRFSPELCT"> </a> </td> <td> adjud. refused same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFSPMNAT <a name="v3-ActCode-ADRFSPMNAT"> </a> </td> <td> adjud. refused same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADRFSPMNCT <a name="v3-ActCode-ADRFSPMNCT"> </a> </td> <td> adjud. refused same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were adjudicated as refused during the specified time period (based on adjudication date) and submitted manually. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_InvoiceElementPaid)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_InvoiceElementPaid"> </a> </td> <td> Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFPPELAT <a name="v3-ActCode-PDNFPPELAT"> </a> </td> <td> paid nullified prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFPPELCT <a name="v3-ActCode-PDNFPPELCT"> </a> </td> <td> paid nullified prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFPPMNAT <a name="v3-ActCode-PDNFPPMNAT"> </a> </td> <td> paid nullified prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFPPMNCT <a name="v3-ActCode-PDNFPPMNCT"> </a> </td> <td> paid nullified prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFSPELAT <a name="v3-ActCode-PDNFSPELAT"> </a> </td> <td> paid nullified same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFSPELCT <a name="v3-ActCode-PDNFSPELCT"> </a> </td> <td> paid nullified same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently cancelled in the specified period and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFSPMNAT <a name="v3-ActCode-PDNFSPMNAT"> </a> </td> <td> paid nullified same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNFSPMNCT <a name="v3-ActCode-PDNFSPMNCT"> </a> </td> <td> paid nullified same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date), subsequently nullified in the specified period and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPPPELAT <a name="v3-ActCode-PDNPPPELAT"> </a> </td> <td> paid non-payee payable prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPPPELCT <a name="v3-ActCode-PDNPPPELCT"> </a> </td> <td> paid non-payee payable prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPPPMNAT <a name="v3-ActCode-PDNPPPMNAT"> </a> </td> <td> paid non-payee payable prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPPPMNCT <a name="v3-ActCode-PDNPPPMNCT"> </a> </td> <td> paid non-payee payable prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPSPELAT <a name="v3-ActCode-PDNPSPELAT"> </a> </td> <td> paid non-payee payable same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPSPELCT <a name="v3-ActCode-PDNPSPELCT"> </a> </td> <td> paid non-payee payable same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPSPMNAT <a name="v3-ActCode-PDNPSPMNAT"> </a> </td> <td> paid non-payee payable same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDNPSPMNCT <a name="v3-ActCode-PDNPSPMNCT"> </a> </td> <td> paid non-payee payable same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that do not match a specified payee (e.g. pay patient) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPPPELAT <a name="v3-ActCode-PDPPPPELAT"> </a> </td> <td> paid payee payable prior-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPPPELCT <a name="v3-ActCode-PDPPPPELCT"> </a> </td> <td> paid payee payable prior-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPPPMNAT <a name="v3-ActCode-PDPPPPMNAT"> </a> </td> <td> paid payee payable prior-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPPPMNCT <a name="v3-ActCode-PDPPPPMNCT"> </a> </td> <td> paid payee payable prior-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid prior to the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPSPELAT <a name="v3-ActCode-PDPPSPELAT"> </a> </td> <td> paid payee payable same-period electronic amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPSPELCT <a name="v3-ActCode-PDPPSPELCT"> </a> </td> <td> paid payee payable same-period electronic count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted electronically. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPSPMNAT <a name="v3-ActCode-PDPPSPMNAT"> </a> </td> <td> paid payee payable same-period manual amount</td> <td> Identifies the total net amount of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 3</td> <td>     PDPPSPMNCT <a name="v3-ActCode-PDPPSPMNCT"> </a> </td> <td> paid payee payable same-period manual count</td> <td> Identifies the total number of all Invoice Groupings that were paid during the specified time period (based on payment date) that match a specified payee (e.g. pay provider) and submitted manually. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_InvoiceElementSubmitted)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_InvoiceElementSubmitted"> </a> </td> <td> Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBBLELAT <a name="v3-ActCode-SBBLELAT"> </a> </td> <td> submitted billed electronic amount</td> <td> Identifies the total net amount billed for all submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBBLELCT <a name="v3-ActCode-SBBLELCT"> </a> </td> <td> submitted billed electronic count</td> <td> Identifies the total number of submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBNFELAT <a name="v3-ActCode-SBNFELAT"> </a> </td> <td> submitted nullified electronic amount</td> <td> Identifies the total net amount billed for all submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBNFELCT <a name="v3-ActCode-SBNFELCT"> </a> </td> <td> submitted cancelled electronic count</td> <td> Identifies the total number of submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBPDELAT <a name="v3-ActCode-SBPDELAT"> </a> </td> <td> submitted pending electronic amount</td> <td> Identifies the total net amount billed for all submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. <br/> </td> </tr> <tr> <td> 3</td> <td>     SBPDELCT <a name="v3-ActCode-SBPDELCT"> </a> </td> <td> submitted pending electronic count</td> <td> Identifies the total number of submitted Invoice Groupings that are pended or held by the payor, within a time period and submitted electronically. Adjudicated invoice elements are not included. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActInvoiceOverrideCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInvoiceOverrideCode"> </a> </td> <td> Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results. <br/> </td> </tr> <tr> <td> 2</td> <td>   COVGE <a name="v3-ActCode-COVGE"> </a> </td> <td> coverage problem</td> <td> Insurance coverage problems have been encountered. Additional explanation information to be supplied. <br/> </td> </tr> <tr> <td> 2</td> <td>   EFORM <a name="v3-ActCode-EFORM"> </a> </td> <td> electronic form to follow</td> <td> Electronic form with supporting or additional information to follow. <br/> </td> </tr> <tr> <td> 2</td> <td>   FAX <a name="v3-ActCode-FAX"> </a> </td> <td> fax to follow</td> <td> Fax with supporting or additional information to follow. <br/> </td> </tr> <tr> <td> 2</td> <td>   GFTH <a name="v3-ActCode-GFTH"> </a> </td> <td> good faith indicator</td> <td> The medical service was provided to a patient in good faith that they had medical coverage, although no evidence of coverage was available before service was rendered. <br/> </td> </tr> <tr> <td> 2</td> <td>   LATE <a name="v3-ActCode-LATE"> </a> </td> <td> late invoice</td> <td> Knowingly over the payor's published time limit for this invoice possibly due to a previous payor's delays in processing. Additional reason information will be supplied. <br/> </td> </tr> <tr> <td> 2</td> <td>   MANUAL <a name="v3-ActCode-MANUAL"> </a> </td> <td> manual review</td> <td> Manual review of the invoice is requested. Additional information to be supplied. This may be used in the case of an appeal. <br/> </td> </tr> <tr> <td> 2</td> <td>   OOJ <a name="v3-ActCode-OOJ"> </a> </td> <td> out of jurisdiction</td> <td> The medical service and/or product was provided to a patient that has coverage in another jurisdiction. <br/> </td> </tr> <tr> <td> 2</td> <td>   ORTHO <a name="v3-ActCode-ORTHO"> </a> </td> <td> orthodontic service</td> <td> The service provided is required for orthodontic purposes. If the covered party has orthodontic coverage, then the service may be paid. <br/> </td> </tr> <tr> <td> 2</td> <td>   PAPER <a name="v3-ActCode-PAPER"> </a> </td> <td> paper documentation to follow</td> <td> Paper documentation (or other physical format) with supporting or additional information to follow. <br/> </td> </tr> <tr> <td> 2</td> <td>   PIE <a name="v3-ActCode-PIE"> </a> </td> <td> public insurance exhausted</td> <td> Public Insurance has been exhausted. Invoice has not been sent to Public Insuror and therefore no Explanation Of Benefits (EOB) is provided with this Invoice submission. <br/> </td> </tr> <tr> <td> 2</td> <td>   PYRDELAY <a name="v3-ActCode-PYRDELAY"> </a> </td> <td> delayed by a previous payor</td> <td> Allows provider to explain lateness of invoice to a subsequent payor. <br/> </td> </tr> <tr> <td> 2</td> <td>   REFNR <a name="v3-ActCode-REFNR"> </a> </td> <td> referral not required</td> <td> Rules of practice do not require a physician's referral for the provider to perform a billable service. <br/> </td> </tr> <tr> <td> 2</td> <td>   REPSERV <a name="v3-ActCode-REPSERV"> </a> </td> <td> repeated service</td> <td> The same service was delivered within a time period that would usually indicate a duplicate billing. However, the repeated service is a medical necessity and therefore not a duplicate. <br/> </td> </tr> <tr> <td> 2</td> <td>   UNRELAT <a name="v3-ActCode-UNRELAT"> </a> </td> <td> unrelated service</td> <td> The service provided is not related to another billed service. For example, 2 unrelated services provided on the same day to the same patient which may normally result in a refused payment for one of the items. <br/> </td> </tr> <tr> <td> 2</td> <td>   VERBAUTH <a name="v3-ActCode-VERBAUTH"> </a> </td> <td> verbal authorization</td> <td> The provider has received a verbal permission from an authoritative source to perform the service or supply the item being invoiced. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActListCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActListCode"> </a> </td> <td> Provides codes associated with ActClass value of LIST (working list) <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActObservationList)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActObservationList"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td>     CARELIST <a name="v3-ActCode-CARELIST"> </a> </td> <td> care plan</td> <td> List of acts representing a care plan. The acts can be in a varierty of moods including event (EVN) to record acts that have been carried out as part of the care plan. <br/> </td> </tr> <tr> <td> 3</td> <td>     CONDLIST <a name="v3-ActCode-CONDLIST"> </a> </td> <td> condition list</td> <td> List of condition observations. <br/> </td> </tr> <tr> <td> 4</td> <td>       INTOLIST <a name="v3-ActCode-INTOLIST"> </a> </td> <td> intolerance list</td> <td> List of intolerance observations. <br/> </td> </tr> <tr> <td> 4</td> <td>       PROBLIST <a name="v3-ActCode-PROBLIST"> </a> </td> <td> problem list</td> <td> List of problem observations. <br/> </td> </tr> <tr> <td> 4</td> <td>       RISKLIST <a name="v3-ActCode-RISKLIST"> </a> </td> <td> risk factors</td> <td> List of risk factor observations. <br/> </td> </tr> <tr> <td> 3</td> <td>     GOALLIST <a name="v3-ActCode-GOALLIST"> </a> </td> <td> goal list</td> <td> List of observations in goal mood. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActTherapyDurationWorkingListCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActTherapyDurationWorkingListCode"> </a> </td> <td> Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed& quot;. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActMedicationTherapyDurationWorkingListCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActMedicationTherapyDurationWorkingListCode"> </a> </td> <td> Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists. <br/> Examples:"Continuous/Chronic" "Short-Term" and "As Needed" <br/> </td> </tr> <tr> <td> 4</td> <td>       ACU <a name="v3-ActCode-ACU"> </a> </td> <td> short term/acute</td> <td> Definition:A list of medications which the patient is only expected to consume for the duration of the current order or limited set of orders and which is not expected to be renewed. <br/> </td> </tr> <tr> <td> 4</td> <td>       CHRON <a name="v3-ActCode-CHRON"> </a> </td> <td> continuous/chronic</td> <td> Definition:A list of medications which are expected to be continued beyond the present order and which the patient should be assumed to be taking unless explicitly stopped. <br/> </td> </tr> <tr> <td> 4</td> <td>       ONET <a name="v3-ActCode-ONET"> </a> </td> <td> one time</td> <td> Definition:A list of medications which the patient is intended to be administered only once. <br/> </td> </tr> <tr> <td> 4</td> <td>       PRN <a name="v3-ActCode-PRN"> </a> </td> <td> as needed</td> <td> Definition:A list of medications which the patient will consume intermittently based on the behavior of the condition for which the medication is indicated. <br/> </td> </tr> <tr> <td> 2</td> <td>   MEDLIST <a name="v3-ActCode-MEDLIST"> </a> </td> <td> medication list</td> <td> List of medications. <br/> </td> </tr> <tr> <td> 3</td> <td>     CURMEDLIST <a name="v3-ActCode-CURMEDLIST"> </a> </td> <td> current medication list</td> <td> List of current medications. <br/> </td> </tr> <tr> <td> 3</td> <td>     DISCMEDLIST <a name="v3-ActCode-DISCMEDLIST"> </a> </td> <td> discharge medication list</td> <td> List of discharge medications. <br/> </td> </tr> <tr> <td> 3</td> <td>     HISTMEDLIST <a name="v3-ActCode-HISTMEDLIST"> </a> </td> <td> medication history</td> <td> Historical list of medications. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActMonitoringProtocolCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActMonitoringProtocolCode"> </a> </td> <td> Identifies types of monitoring programs <br/> </td> </tr> <tr> <td> 2</td> <td>   CTLSUB <a name="v3-ActCode-CTLSUB"> </a> </td> <td> Controlled Substance</td> <td> A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction. <br/> </td> </tr> <tr> <td> 2</td> <td>   INV <a name="v3-ActCode-INV"> </a> </td> <td> investigational</td> <td> Definition:A monitoring program that focuses on a drug which is under investigation and has not received regulatory approval for the condition being investigated <br/> </td> </tr> <tr> <td> 2</td> <td>   LU <a name="v3-ActCode-LU"> </a> </td> <td> limited use</td> <td> Description:A drug that can be prescribed (and reimbursed) only if it meets certain criteria. <br/> </td> </tr> <tr> <td> 2</td> <td>   OTC <a name="v3-ActCode-OTC"> </a> </td> <td> non prescription medicine</td> <td> Medicines designated in this way may be supplied for patient use without a prescription. The exact form of categorisation will vary in different realms. <br/> </td> </tr> <tr> <td> 2</td> <td>   RX <a name="v3-ActCode-RX"> </a> </td> <td> prescription only medicine</td> <td> Some form of prescription is required before the related medicine can be supplied for a patient. The exact form of regulation will vary in different realms. <br/> </td> </tr> <tr> <td> 2</td> <td>   SA <a name="v3-ActCode-SA"> </a> </td> <td> special authorization</td> <td> Definition:A drug that requires prior approval (to be reimbursed) before being dispensed <br/> </td> </tr> <tr> <td> 2</td> <td>   SAC <a name="v3-ActCode-SAC"> </a> </td> <td> special access</td> <td> Description:A drug that requires special access permission to be prescribed and dispensed. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActNonObservationIndicationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActNonObservationIndicationCode"> </a> </td> <td> Description:Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms. <br/> </td> </tr> <tr> <td> 2</td> <td>   IND01 <a name="v3-ActCode-IND01"> </a> </td> <td> imaging study requiring contrast</td> <td> Description:Contrast agent required for imaging study. <br/> </td> </tr> <tr> <td> 2</td> <td>   IND02 <a name="v3-ActCode-IND02"> </a> </td> <td> colonoscopy prep</td> <td> Description:Provision of prescription or direction to consume a product for purposes of bowel clearance in preparation for a colonoscopy. <br/> </td> </tr> <tr> <td> 2</td> <td>   IND03 <a name="v3-ActCode-IND03"> </a> </td> <td> prophylaxis</td> <td> Description:Provision of medication as a preventative measure during a treatment or other period of increased risk. <br/> </td> </tr> <tr> <td> 2</td> <td>   IND04 <a name="v3-ActCode-IND04"> </a> </td> <td> surgical prophylaxis</td> <td> Description:Provision of medication during pre-operative phase; e.g., antibiotics before dental surgery or bowel prep before colon surgery. <br/> </td> </tr> <tr> <td> 2</td> <td>   IND05 <a name="v3-ActCode-IND05"> </a> </td> <td> pregnancy prophylaxis</td> <td> Description:Provision of medication for pregnancy --e.g., vitamins, antibiotic treatments for vaginal tract colonization, etc. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActObservationVerificationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActObservationVerificationType"> </a> </td> <td> Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity. <br/> Examples: <br/> Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program <br/> Verification of record - e.g., person has record in an immunization registry <br/> Verification of enumeration - e.g. NPI <br/> Verification of Board Certification - provider specific <br/> Verification of Certification - e.g. JAHCO, NCQA, URAC <br/> Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria <br/> Verification of Provider Credentials <br/> Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB) <br/> </td> </tr> <tr> <td> 2</td> <td>   VFPAPER <a name="v3-ActCode-VFPAPER"> </a> </td> <td> verify paper</td> <td> Definition:Indicates that the paper version of the record has, should be or is being verified against the electronic version. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActPaymentCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPaymentCode"> </a> </td> <td> Code identifying the method or the movement of payment instructions. <br/> Codes are drawn from X12 data element 591 (PaymentMethodCode) <br/> </td> </tr> <tr> <td> 2</td> <td>   ACH <a name="v3-ActCode-ACH"> </a> </td> <td> Automated Clearing House</td> <td> Automated Clearing House (ACH). <br/> </td> </tr> <tr> <td> 2</td> <td>   CHK <a name="v3-ActCode-CHK"> </a> </td> <td> Cheque</td> <td> A written order to a bank to pay the amount specified from funds on deposit. <br/> </td> </tr> <tr> <td> 2</td> <td>   DDP <a name="v3-ActCode-DDP"> </a> </td> <td> Direct Deposit</td> <td> Electronic Funds Transfer (EFT) deposit into the payee's bank account <br/> </td> </tr> <tr> <td> 2</td> <td>   NON <a name="v3-ActCode-NON"> </a> </td> <td> Non-Payment Data</td> <td> Non-Payment Data. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActPharmacySupplyType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPharmacySupplyType"> </a> </td> <td> Identifies types of dispensing events <br/> </td> </tr> <tr> <td> 2</td> <td>   DF <a name="v3-ActCode-DF"> </a> </td> <td> Daily Fill</td> <td> A fill providing sufficient supply for one day <br/> </td> </tr> <tr> <td> 2</td> <td>   EM <a name="v3-ActCode-EM"> </a> </td> <td> Emergency Supply</td> <td> A supply action where there is no 'valid' order for the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription) <br/> </td> </tr> <tr> <td> 3</td> <td>     SO <a name="v3-ActCode-SO"> </a> </td> <td> Script Owing</td> <td> An emergency supply where the expectation is that a formal order authorizing the supply will be provided at a later date. <br/> </td> </tr> <tr> <td> 2</td> <td>   FF <a name="v3-ActCode-FF"> </a> </td> <td> First Fill</td> <td> The initial fill against an order. (This includes initial fills against refill orders.) <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#FFS">FFS</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     FFC <a name="v3-ActCode-FFC"> </a> </td> <td> First Fill - Complete</td> <td> A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets). <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#FFCS">FFCS</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     FFP <a name="v3-ActCode-FFP"> </a> </td> <td> First Fill - Part Fill</td> <td> A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#FFPS">FFPS</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     FFSS <a name="v3-ActCode-FFSS"> </a> </td> <td> first fill, partial strength</td> <td> A first fill where the strength supplied is less than the ordered strength. (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#FFPS">FFPS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#FFCS">FFCS</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#TFS">TFS</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     TF <a name="v3-ActCode-TF"> </a> </td> <td> Trial Fill</td> <td> A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#TFS">TFS</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td>   FS <a name="v3-ActCode-FS"> </a> </td> <td> Floor stock</td> <td> A supply action to restock a smaller more local dispensary. <br/> </td> </tr> <tr> <td> 2</td> <td>   MS <a name="v3-ActCode-MS"> </a> </td> <td> Manufacturer Sample</td> <td> A supply of a manufacturer sample <br/> </td> </tr> <tr> <td> 2</td> <td>   RF <a name="v3-ActCode-RF"> </a> </td> <td> Refill</td> <td> A fill against an order that has already been filled (or partially filled) at least once. <br/> </td> </tr> <tr> <td> 3</td> <td>     <a href="#DF">DF</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     UD <a name="v3-ActCode-UD"> </a> </td> <td> Unit Dose</td> <td> A supply action that provides sufficient material for a single dose. <br/> </td> </tr> <tr> <td> 3</td> <td>     RFC <a name="v3-ActCode-RFC"> </a> </td> <td> Refill - Complete</td> <td> A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) <br/> </td> </tr> <tr> <td> 4</td> <td>       RFCS <a name="v3-ActCode-RFCS"> </a> </td> <td> refill complete partial strength</td> <td> A refill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 3</td> <td>     RFF <a name="v3-ActCode-RFF"> </a> </td> <td> Refill (First fill this facility)</td> <td> The first fill against an order that has already been filled at least once at another facility. <br/> </td> </tr> <tr> <td> 4</td> <td>       RFFS <a name="v3-ActCode-RFFS"> </a> </td> <td> refill partial strength (first fill this facility)</td> <td> The first fill against an order that has already been filled at least once at another facility and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 3</td> <td>     RFP <a name="v3-ActCode-RFP"> </a> </td> <td> Refill - Part Fill</td> <td> A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) <br/> </td> </tr> <tr> <td> 4</td> <td>       RFPS <a name="v3-ActCode-RFPS"> </a> </td> <td> refill part fill partial strength</td> <td> A refill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 3</td> <td>     RFS <a name="v3-ActCode-RFS"> </a> </td> <td> refill partial strength</td> <td> A fill against an order that has already been filled (or partially filled) at least once and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 3</td> <td>     TB <a name="v3-ActCode-TB"> </a> </td> <td> Trial Balance</td> <td> A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided. <br/> </td> </tr> <tr> <td> 4</td> <td>       TBS <a name="v3-ActCode-TBS"> </a> </td> <td> trial balance partial strength</td> <td> A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided and where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets). <br/> </td> </tr> <tr> <td> 2</td> <td>   <a href="#UD">UD</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td>   UDE <a name="v3-ActCode-UDE"> </a> </td> <td> unit dose equivalent</td> <td> A supply action that provides sufficient material for a single dose via multiple products. E.g. 2 50mg tablets for a 100mg unit dose. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActPolicyType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPolicyType"> </a> </td> <td> A mandate, regulation, obligation, principle, requirement, rule, or expectation of how an entity is to conduct itself or execute an activity, which may be dictated and enforced by an authority of competent jurisdiction. <br/> </td> </tr> <tr> <td> 2</td> <td>   _ActConsent <a name="v3-ActCode-_ActConsent"> </a> </td> <td> _ActConsent</td> <td> Specifies the type or actual definition of a contractually binding agreement or a non-binding representation of that agreement between a grantor and a grantee as to the exchange of the grantee’s considerations in return for the grantor’s control of certain assets. The type of assets exchanged include rights, license, terms of service, valued items, information and real property assets and control over such assets such as physical and locatable property; intellectual property; biospecimen; genomic and genetic information related to an individual including that disclosed by genetically related individuals with or without the individual’s consent; personal identifiable, pseudonymized, anonymized, de-identified per some rubric, and relinkable variants. <br/> Usage Note: Types or actual definitions of a contractually binding agreement or a non-binding representation of that agreement include: <br/> _ActDecision (formally ActConsentDirective), which specifies the type of decision made by the grantor. The decision types are mapped to ISO/TS 17975 Health informatics â€� Principles and data requirements for consent in the Collection, Use or Disclosure of personal health information; _ActPrivacyConsentDirective, which is the parent of types of registry participation consent directives, and of realm specific privacy consent directive policies such as _USPrivacyConsentDirective and _GDPRPrivacyConsentDirective. </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActDecision)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActDecision"> </a> </td> <td> Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. <br/> Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective. <br/> Examples: <br/> Healthcare Privacy Consent Directive permitting or restricting in whole or part the collection, access, use, and disclosure of health information, and any associated handling caveats. Healthcare Medical Consent Directive to receive medical procedures after being informed of risks and benefits, thereby reducing the grantee's liability. Research Informed Consent for participation in clinical trials and disclosure of health information after being informed of risks and benefits, thereby reducing the grantee's liability. Substitute decision maker delegation in which the grantee assumes responsibility to act on behalf of the grantor. Contracts in which the agreement requires assent/dissent by the grantor of terms offered by a grantee, a consumer opts out of an "award" system for use of a retailer's marketing or credit card vendor's point collection cards in exchange for allowing purchase tracking and profiling. A mobile device or App privacy policy and terms of service to which a user must agree in whole or in part in order to utilize the service. Agreements between a client and an authorization server or between an authorization server and a resource operator and/or resource owner permitting or restricting e.g., collection, access, use, and disclosure of information, and any associated handling caveats. </td> </tr> <tr> <td> 4</td> <td>       GRANTORCHOICE <a name="v3-ActCode-GRANTORCHOICE"> </a> </td> <td> grantor choice</td> <td> A grantor's terms of agreement to which a grantee may assent or dissent, and which may include an opportunity for a grantee to request restrictions or extensions. <br/> Comment: A grantor typically is able to stipulate preferred terms of agreement when the grantor has control over the topic of the agreement, which a grantee must accept in full or may be offered an opportunity to extend or restrict certain terms. <br/> Usage Note: If the grantor's term of agreement must be accepted in full, then this is considered "basic consent". If a grantee is offered an opportunity to extend or restrict certain terms, then the agreement is considered "granular consent". <br/> Examples: <br/> Healthcare: A PHR account holder [grantor] may require any PHR user [grantee] to accept the terms of agreement in full, or may permit a PHR user to extend or restrict terms selected by the account holder or requested by the PHR user. Non-healthcare: The owner of a resource server [grantor] may require any authorization server [grantee] to meet authorization requirements stipulated in the grantor's terms of agreement. </td> </tr> <tr> <td> 4</td> <td>       IMPLIED <a name="v3-ActCode-IMPLIED"> </a> </td> <td> implied consent</td> <td> A grantor's presumed assent to the grantee's terms of agreement is based on the grantor's behavior, which may result from not expressly assenting to the consent directive offered, or from having no right to assent or dissent offered by the grantee. <br/> Comment: Implied or "implicit" consent occurs when the behavior of the grantor is understood by a reasonable person to signal agreement to the grantee's terms. <br/> Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered "basic consent". <br/> Examples: <br/> Healthcare: A patient schedules an appointment with a provider, and either does not take the opportunity to expressly assent or dissent to the provider's consent directive, does not have an opportunity to do so, as in the case where emergency care is required, or simply behaves as though the patient [grantor] agrees to the rights granted to the provider [grantee] in an implicit consent directive. An injured and unconscious patient is deemed to have assented to emergency treatment by those permitted to do so under jurisdictional laws, e.g., Good Samaritan laws. Non-healthcare: Upon receiving a driver's license, the driver is deemed to have assented without explicitly consenting to undergoing field sobriety tests. A corporation that does business in a foreign nation is deemed to have deemed to have assented without explicitly consenting to abide by that nation's laws. </td> </tr> <tr> <td> 4</td> <td>       IMPLIEDD <a name="v3-ActCode-IMPLIEDD"> </a> </td> <td> implied consent with opportunity to dissent</td> <td> A grantor's presumed assent to the grantee's terms of agreement, which is based on the grantor's behavior, and includes a right to dissent to certain terms. <br/> Comment: A grantor assenting to the grantee's terms of agreement may or may not exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent. <br/> Usage Note: Implied or "implicit" consent with an "opportunity to dissent" occurs when the grantor's behavior is understood by a reasonable person to signal assent to the grantee's terms of agreement whether the grantor requests or the grantee approves further restrictions, is considered "granular consent". <br/> Examples: <br/> Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of health information to family members and friends, but offers an opportunity or permits the patient to dissent to such disclosures. A health information exchanges deems a patient to have assented to disclosure of health information for treatment purposes, but offers the patient an opportunity to dissents to disclosure to particular provider organizations. Non-healthcare Examples: A bank deems a banking customer's assent to specified collection, access, use, or disclosure of financial information as a requirement of holding a bank account, but provides the user an opportunity to limit third-party collection, access, use or disclosure of that information for marketing purposes. </td> </tr> <tr> <td> 4</td> <td>       NOCONSENT <a name="v3-ActCode-NOCONSENT"> </a> </td> <td> no consent</td> <td> No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement. <br/> Comment: A "No Consent" policy scheme provides no opportunity for accommodation of an individual's preferences, and may not comply with Fair Information Practice Principles [FIPP] by enabling the data subject to object, access collected information, correct errors, or have accounting of disclosures. <br/> Usage Note: The grantee's terms of agreement, may be available to the grantor by reviewing the grantee's privacy policies, but there is no notice by which a grantor is apprised of the policy directly or able to acknowledge. <br/> Examples: <br/> Healthcare: Without notification or an opportunity to assent or dissent, a patient's health information is automatically included in and available (often according to certain rules) through a health information exchange. Note that this differs from implied consent, where the patient is assumed to have consented. Without notification or an opportunity to assent or dissent, a patient's health information is collected, accessed, used, or disclosed for research, public health, security, fraud prevention, court order, or law enforcement. Non-healthcare: Without notification or an opportunity to assent or dissent, a consumer's healthcare or non-healthcare internet searches are aggregated for secondary uses such as behavioral tracking and profiling. Without notification or an opportunity to assent or dissent, a consumer's location and activities in a shopping mall are tracked by RFID tags on purchased items. </td> </tr> <tr> <td> 4</td> <td>       OPTIN <a name="v3-ActCode-OPTIN"> </a> </td> <td> opt-in</td> <td> A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. <br/> Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. <br/> Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". <br/> Examples: <br/> Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies. Non-healthcare: An employee [grantor] signs an employer's [grantee's] non-disclosure and non-compete agreement. </td> </tr> <tr> <td> 4</td> <td>       OPTINR <a name="v3-ActCode-OPTINR"> </a> </td> <td> opt-in with restrictions</td> <td> A grantor's assent to the grantee's terms of an agreement with an opportunity for to dissent to certain grantor or grantee selected terms. <br/> Comment: A grantor dissenting to the grantee's terms of agreement may or may not exercise a right to assent to grantor's pre-approved restrictions or to grantee's selected terms to which a grantor may dissent. <br/> Usage Note: Opt-in with restrictions is considered "granular consent" because the grantor has an opportunity to narrow the permissions sought by the grantee. <br/> Examples: <br/> Healthcare: A patient assent to grantee's consent directive terms for collection, access, use, or disclosure of health information, and dissents to disclosure to certain recipients as allowed by the provider's pre-approved restriction list. Non-Healthcare: A cell phone user assents to the cell phone's privacy practices and terms of use, but dissents from location tracking by turning off the cell phone's tracking capability. </td> </tr> <tr> <td> 4</td> <td>       OPTOUT <a name="v3-ActCode-OPTOUT"> </a> </td> <td> op-out</td> <td> A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms. <br/> Comment: Rejection of a grantee's terms of agreement pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. <br/> Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered "basic consent". <br/> Examples: <br/> Healthcare: A patient [grantor] declines to sign a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, revocation policies, and consequences of not assenting. Non-healthcare: An employee [grantor] refuses to sign an employer's [grantee's] agreement not to join unions or participate in a strike where state law protects employee's collective bargaining rights. A citizen [grantor] refuses to enroll in mandatory government [grantee] health insurance based on religious beliefs, which is an exemption. </td> </tr> <tr> <td> 4</td> <td>       OPTOUTE <a name="v3-ActCode-OPTOUTE"> </a> </td> <td> opt-out with exceptions</td> <td> A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms. <br/> Comment: A rejection of a grantee's terms of agreement while assenting to certain permissions sought by the grantee or requesting approval of additional grantor terms. <br/> Usage Note: Opt-out with exceptions is considered a "granular consent" because the grantor has an opportunity to accept certain permissions sought by the grantee or request additional grantor terms, while rejecting other grantee terms. <br/> Examples: <br/> Healthcare: A patient [grantor] dissents to a health information exchange consent directive with the exception of disclosure based on a limited "time to live" shared secret [e.g., a token or password], which the patient can give to a provider when seeking care. Non-healthcare: A social media user [grantor] dissents from public access to their account, but assents to access to a circle of friends. </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActPrivacyConsentDirective)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPrivacyConsentDirective"> </a> </td> <td> Specifies types of consent directives governing the collection, access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActGDPRConsentDirective)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActGDPRConsentDirective"> </a> </td> <td> European Union General Data Protection Regulation (GDPR) consent directives. <br/> </td> </tr> <tr> <td> 5</td> <td>         GDPRCD <a name="v3-ActCode-GDPRCD"> </a> </td> <td> GDPR Consent Directive</td> <td> A consent directive compliant with the European Union General Data Protection Regulation (GDPR) definition: Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. <br/> Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data. If the data subject's consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language. Any part of such a declaration which constitutes an infringement of this Regulation shall not be binding. The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent. When assessing whether consent is freely given, utmost account shall be taken of whether, inter alia, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract. Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject's agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement. This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject's acceptance of the proposed processing of his or her personal data. Silence, pre-ticked boxes or inactivity should not therefore constitute consent. Consent should cover all processing activities carried out for the same purpose or purposes. When the processing has multiple purposes, consent should be given for all of them. If the data subject's consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided. <br/> Usage Note: Article 4.11 GDPR Definitions https://gdpr-info.eu/art-4-gdpr/ 11) 'Consent' of the data subject means any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. Article 7 GDPR Conditions for consent https://gdpr-info.eu/art-7-gdpr Recital 32 Conditions for consent* https://gdpr-info.eu/recitals/no-32 Recital 42 Burden of proof and requirements for consent* https://gdpr-info.eu/recitals/no-42/> Recital 43 Freely given consent* https://gdpr-info.eu/recitals/no-43 GDPR Consent Brief https://gdpr-info.eu/issues/consent/ Art. 4 GDPR Definitions Art. 6 GDPR Lawfulness of processing Art. 7 GDPR Conditions for consent Art. 8 GDPR Conditions applicable to child's consent in relation to information society services Art. 9 GDPR Processing of special categories of personal data Art. 22 GDPR Automated individual decision-making, including profiling Art. 49 GDPR Derogations for specific situations <br/> Relevant GDPR Recitals: (32) Conditions for consent (33) Consent to certain areas of scientific research (38) Special protection of children's personal data (40) Lawfulness of data processing (42) Burden of proof and requirements for consent (43) Freely given consent (50) Further processing of personal data (51) Protecting sensitive personal data (54) Processing of sensitive data in public health sector (71) Profiling (111) Exceptions for certain cases of international transfers (155) Processing in the employment context (161) Consenting to the participation in clinical trials (171) Repeal of Directive 95/46/EC and transitional provisions <br/> </td> </tr> <tr> <td> 5</td> <td>         GDPRResearchCD <a name="v3-ActCode-GDPRResearchCD"> </a> </td> <td> GDPR Research Consent Directive</td> <td> A consent directive that complies with regulatory requirements for a consent directive compliant with the European Union General Data Protection Regulation (GDPR) definition: Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. <br/> GDPR research consent directive has the additional caveat that it is often not possible to fully identify the purpose of personal data processing for scientific research purposes at the time of data collection. Therefore, data subjects should be allowed to give their consent to certain areas of scientific research when in keeping with recognized ethical standards for scientific research. Data subjects should have the opportunity to give their consent only to certain areas of research or parts of research projects to the extent allowed by the intended purpose. <br/> Usage Note: HL7 Purpose of Use codes include specialize research purposes of use, which could be used to convey a data subject’s purpose of use restrictions related to areas of research or parts of research projects. See citations for GDPRResearchCD and below: Recital 33 Consent to certain areas of scientific research https://gdpr-info.eu/recitals/no-33/> Recital 157 Information from registries and scientific research https://gdpr-info.eu/recitals/no-157 Recital 159 Processing for scientific research purposes* https://gdpr-info.eu/recitals/no-159/ <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActGenericConsentDirective)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActGenericConsentDirective"> </a> </td> <td> Specifies types of consent directives authorizing a registry or repository to collect and, under certain terms, manage the access, use, and disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual. <br/> Registries governed by registry consent directives are data management systems, which use metadata to support the collection, access, use, and disclosure of personal information or effects as well as observational or analytic information generated about personal information or effects stored in federated repositories. Such registries are used for a variety of purposes by federated health information exchanges, health information systems, personal record systems, and research organizations to locate and retrieve personal information or effects as well as observational or analytic information generated about personal information stored externally to their systems. <br/> Repositories governed by registry consent directives are data stores used to collect, access, use, and disclose personal information or effects as well as observational or analytic information generated about personal information or effects and metadata used to manage the repository contents. Such repositories are used for a variety of purposes by centralized health information exchanges, health information systems used by providers and payers, personal record systems, and research organizations. A repository typically includes a registry component that provides the data store with content management capabilities for internal purposes. A repository may also interface with one or more external registries, which provide federated content management. <br/> </td> </tr> <tr> <td> 5</td> <td>         OIC <a name="v3-ActCode-OIC"> </a> </td> <td> opt-in to personal information or effect collection in a registry or repository</td> <td> An expressed privacy consent directive permitting the collection of a some or all personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling. <br/> Usage Note: Useful when a more specific jurisdictional or organizational consent directive policy or form is not specified, available, or known, for example, where an individual wishes to opt-in to collection of some or all of the individual’s information by multiple registries and repositories. <br/> Map: An “expressedâ€? consent directive maps to ISO/TS 17975:2015(E) definitions for “Express or Expressed: Consent to Collect, Use and Disclose personal health information is expressly given by the subject of careâ€? and “Opt-inâ€?. <br/> </td> </tr> <tr> <td> 5</td> <td>         OIS <a name="v3-ActCode-OIS"> </a> </td> <td> opt-in to personal information or effect sharing via a registry or repository</td> <td> An expressed privacy consent directive permitting access, use, or disclosure of a some or all personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling. <br/> Usage Note: Useful when a more specific jurisdictional or organizational consent directive policy or form is not specified, available, or known, for example, where an individual wishes to opt-in to access, use, or disclosure of some or all of the individual’s information by multiple registries and repositories. <br/> Map: An “expressedâ€? consent directive maps to ISO/TS 17975:2015(E) Express or Expressed: Consent to Collect, Use and Disclose personal health information is expressly given by the subject of care and “Opt-inâ€?. <br/> </td> </tr> <tr> <td> 5</td> <td>         OOC <a name="v3-ActCode-OOC"> </a> </td> <td> opt-out of personal information or effect collection in a registry or repository</td> <td> An expressed privacy consent directive restricting or prohibiting collection of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling. <br/> Usage Note: Useful when a more specific jurisdictional or organizational consent directive policy or form is not specified, available, or known, for example, where an individual wishes to opt-out of access, use, or disclosure of some or all of the individual’s information by multiple registries and repositories. <br/> Map: An “expressedâ€? opt-out to collection consent directive maps to ISO/TS 17975:2015(E) definitions for “Express or Expressed: Consent to Collect, Use and Disclose personal health information is expressly given by the subject of careâ€? and “Express or Expressed (and Informed) Denialâ€?. <br/> </td> </tr> <tr> <td> 5</td> <td>         OOS <a name="v3-ActCode-OOS"> </a> </td> <td> opt-out of personal information or effect sharing via a registry or repository</td> <td> An expressed privacy consent directive restricting or prohibiting access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling. <br/> Usage Note: Useful when a more specific jurisdictional or organizational consent directive policy or form is not specified, available, or known, for example, where an individual wishes to opt-out of access, use, or disclosure of some or all of the individual’s information by multiple registries and repositories. <br/> Map: An “expressedâ€? opt-out to sharing consent directive maps to ISO/TS 17975:2015(E) definitions for “Express or Expressed: Consent to Collect, Use and Disclose personal health information is expressly given by the subject of careâ€? and “Express or Expressed (and Informed) Denialâ€?. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActUSPrivacyConsentDirective)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActUSPrivacyConsentDirective"> </a> </td> <td> Specific US privacy consent directives in accordance with US federal, state, regional, organizational, or personal privacy policies. <br/> </td> </tr> <tr> <td> 5</td> <td>         42CFRPart2CD <a name="v3-ActCode-42CFRPart2CD"> </a> </td> <td> 42 CFR Part 2 consent directive</td> <td> A code representing an individual’s privacy consent directive that complies with 42 CFR Part 2.31 Consent requirements https://www.gpo.gov/fdsys/pkg/CFR-2017-titl e42-vol1/pdf/CFR-2017-title42-vol1-sec2-31.pdf, which is a US Federal law stipulating the policy elements of a written consent to a disclosure under the regulations in Part 2. <br/> (1) The name of the patient. (2) The specific name(s) or general designation(s) of the part 2 program(s), entity(ies), or individual(s) permitted to make the disclosure. (3) How much and what kind of information is to be disclosed, including an explicit description of the substance use disorder information that may be disclosed. (4) (i) The name(s) of the individual(s) to whom a disclosure is to be made; or (ii)Entities with a treating provider relationship with the patient. If the recipient entity has a treating provider relationship with the patient whose information is being disclosed, such as a hospital, a health care clinic, or a private practice, the name of that entity; or (iii)Entities without a treating provider relationship with the patient. (A) If the recipient entity does not have a treating provider relationship with the patient whose information is being disclosed and is a third-party payer, the name of the entity; or (B) If the recipient entity does not have a treating provider relationship with the patient whose information is being disclosed and is not covered by paragraph (a)(4)(iii)(A) of this section, such as an entity that facilitates the exchange of health information or a research institution, the name(s) of the entity(-ies); and (1) The name(s) of an individual participant(s); or (2) The name(s) of an entity participant(s) that has a treating provider relationship with the patient whose information is being disclosed; or (3) A general designation of an individual or entity participant(s) or class of participants that must be limited to a participant(s) who has a treating provider relationship with the patient whose information is being disclosed. (i) When using a general designation, a statement must be included on the consent form that the patient (or other individual authorized to sign in lieu of the patient), confirms their understanding that, upon their request and consistent with this part, they must be provided a list of entities to which their information has been disclosed pursuant to the general designation (see Section 2.13(d)). (ii) [Reserved] (5) The purpose of the disclosure. In accordance with Section 2.13(a), the disclosure must be limited to that information which is necessary to carry out the stated purpose. (6) A statement that the consent is subject to revocation at any time except to the extent that the part 2 program or other lawful holder of patient identifying information that is permitted to make the disclosure has already acted in reliance on it. Acting in reliance includes the provision of treatment services in reliance on a valid consent to disclose information to a third-party payer (7) The date, event, or condition upon which the consent will expire if not revoked before. This date, event, or condition must ensure that the consent will last no longer than reasonably necessary to serve the purpose for which it is provided. (8) The signature of the patient and, when required for a patient who is a minor, the signature of an individual authorized to give consent under Section 2.14; or, when required for a patient who is incompetent or deceased, the signature of an individual authorized to sign under Section 2.15. Electronic signatures are permitted to the extent that they are not prohibited by any applicable law. (9) The date on which the consent is signed. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by an individual’s 42 CFR Part 2.31 consent directive, “42CFRPart2CDâ€? as the security label policy code. <br/> Since information governed by an individual’s 42 CFR Part 2.31 consent directive has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR § 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol 1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         CompoundResearchCD <a name="v3-ActCode-CompoundResearchCD"> </a> </td> <td> Compound HIPAA Research Authorization and Informed Consent for Research</td> <td> A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508 .pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section specific to disclosures for purposes of research when combined with a Common Rule or Federal Drug Administration consent to participate in research also known as a compound authorization. <br/> Usage Note: The Agency for Healthcare Research and Quality (AHRQ) has developed the Informed Consent and Authorization Toolkit for Minimal Risk Research to facilitate the process of obtaining informed consent and Health Insurance Portability and Accountability Act (HIPAA) authorization from potential research subjects. This toolkit contains information for people responsible for ensuring that potential research subjects are informed in a manner that is consistent with medical ethics and regulatory guidelines. From https://www.ahrq.gov/sites/default/files/publications/files/ictoolkit.pdf. <br/> Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by an individual’s right of access directive under 45 CFR Section 164.508 use “CompoundResearchCDâ€? as the security label policy code. <br/> Information or biospecimen disclosed under the Common Rule are not protected by the HIPAA Privacy Rule. If protected under other laws such as confidentiality provisions under the Common Rule, assign the HL7 Confidentiality code “Mâ€? (moderate). <br/> See ActCode._ActPolicyType._ActPrivacyPolicy._ActPrivacyLaw._ActUSPrivacyLaw .HIPAAAuth (HIPAA Authorization for Disclosure). See: HIPAAAuth and NIH Sample Authorization Language for Research Uses and Disclosures of Individually Identifiable Health Information by a Covered Health Care Provider https://privacyruleandresearch.nih.gov/authorization.asp <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAAuthCD <a name="v3-ActCode-HIPAAAuthCD"> </a> </td> <td> HIPAA Authorization Consent Directive</td> <td> A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508 .pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section. <br/> An “authorizationâ€? is required by the Privacy Rule for uses and disclosures of protected health information not otherwise allowed by the Rule. Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization. An authorization is a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual. <br/> An authorization must specify a number of elements, including a description of the protected health information to be used and disclosed, the person authorized to make the use or disclosure, the person to whom the covered entity may make the disclosure, an expiration date, and, in some cases, the purpose for which the information may be used or disclosed. With limited exceptions, covered entities may not condition treatment or coverage on the individual providing an authorization. https://www.hhs.gov/hipaa/for-pr ofessionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html <br/> A HIPAA Authorization must comply with 45 CFR Section164.508(c) Implementation specifications: Core elements and requirements – (1) Core elements. A valid authorization under this Section must contain at least the following elements: (i) A description of the information to be used or disclosed that identifies the information in a specific and meaningful fashion. (ii) The name or other specific identification of the person(s), or class of persons, authorized to make the requested use or disclosure. (iii) The name or other specific identification of the person(s), or class of persons, to whom the covered entity may make the requested use or disclosure. (iv) A description of each purpose of the requested use or disclosure. The statement “at the request of the individualâ€? is a sufficient description of the purpose when an individual initiates the authorization and does not, or elects not to, provide a statement of the purpose. (v) An expiration date or an expiration event that relates to the individual or the purpose of the use or disclosure. The statement “end of the research study,â€? “none,â€? or similar language is sufficient if the authorization is for a use or disclosure of protected health information for research, including for the creation and maintenance of a research database or research repository. (vi) Signature of the individual and date. If the authorization is signed by a personal representative of the individual, a description of such representative's authority to act for the individual must also be provided. (2)Required statements. In addition to the core elements, the authorization must contain statements adequate to place the individual on notice of all of the following: (i) The individual's right to revoke the authorization in writing, and either: (A) The exceptions to the right to revoke and a description of how the individual may revoke the authorization; or (B) To the extent that the information in paragraph (c)(2)(i)(A) of this section is included in the notice required by Section 164.520, a reference to the covered entity's notice. https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf <br/> Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by a an individual’s HIPAA Authorization for Disclosure, use “HIPAAAuthCDâ€? as the security label policy code. <br/> Information governed under a HIPAA Authorization for Disclosure has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.go v/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, which is considered the “normâ€?, assign the HL7 Confidentiality code “Nâ€? (normal). <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAConsentCD <a name="v3-ActCode-HIPAAConsentCD"> </a> </td> <td> HIPAA Consent Directive</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/ CFR-2017-title45-vol1-sec164-522.pdf, which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent." <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by an individual’s consent directive under 45 CFR Section 164.522 use “HIPAAConsentCDâ€? as the security label policy code. <br/> Since information governed by a 45 CFR Section 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-v ol1-sec164-506.pdf, assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAResearchAuthCD <a name="v3-ActCode-HIPAAResearchAuthCD"> </a> </td> <td> HIPAA Authorization for Disclosure for Research Consent Directive</td> <td> A code representing an individual’s consent directive that complies with HIPAA Privacy rule 45 CFR Section 164.508 Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508 .pdf, which is a US Federal law stipulating the policy elements of a valid authorization under this Section specific to disclosures for purposes of research. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by an individual’s HIPAA Authorization for Disclosure for Research under 45 CFR Section 164.508 use “HIPAAResearchAuthCDâ€? as the security label policy code. <br/> Information disclosed under an individual’s HIPAA Authorization for Disclosure for Research are not protected by the HIPAA Privacy Rule. If protected under other laws such as confidentiality provisions under the Common Rule, assign the HL7 Confidentiality code “Mâ€? (moderate). <br/> See ActCode._ActPolicyType._ActPrivacyPolicy._ActPrivacyLaw._ActUSPrivacyLaw .HIPAAAuth (HIPAA Authorization for Disclosure). See: HIPAAAuth and NIH Sample Authorization Language for Research Uses and Disclosures of Individually Identifiable Health Information by a Covered Health Care Provider https://privacyruleandresearch.nih.gov/authorization.asp <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAROAD <a name="v3-ActCode-HIPAAROAD"> </a> </td> <td> HIPAA Right of Access Directive</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.524 Access of individuals to protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-tit le45-vol1-sec164-524.pdf, stipulating the policy elements of an individual’s written and signed right of access directive requesting that a covered entity send the individual’s protected health information (PHI) to a third party. <br/> See 45 CFR 164.524(c)(3)(ii) If an individual's request for access directs the covered entity to transmit the copy of protected health information directly to another person designated by the individual, the covered entity must provide the copy to the person designated by the individual. The individual's request must be in writing, signed by the individual, and clearly identify the designated person and where to send the copy of protected health information. https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/C FR-2017-title45-vol1-sec164-524.pdf <br/> This right applies to PHI in a designated record set, which is defined as “Designated record set means: (1) A group of records maintained by or for a covered entity that is: (i) The medical records and billing records about individuals maintained by or for a covered health care provider; (ii) The enrollment, payment, claims adjudication, and case or medical management record systems maintained by or for a health plan; or (iii) Used, in whole or in part, by or for the covered entity to make decisions about individuals. [https://www.law.cornell.edu/cfr/text/45/164.501]. Also see HHS Individuals’ Right under HIPAA to Access their Health Information 45 CFR Section 164.524 [https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html#maxi mumflatfee]. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by an individual’s right of access directive under 45 CFR Section 164.524 use “HIPAAROADâ€? as the security label policy code. <br/> Information disclosed under a HIPAA 42 CFR Section 164.524 no longer has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.go v/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is considered the “normâ€?, assign the HL7 Confidentiality code “Mâ€? (moderate), which may be protected under other laws such as the Federal Trade Commission privacy and security regulations. <br/> </td> </tr> <tr> <td> 5</td> <td>         MDHHS-5515 <a name="v3-ActCode-MDHHS-5515"> </a> </td> <td> Michigan Consent to Share Behavioral Health Information for Care Coordination Purposes</td> <td> Michigan’s standard consent form for the sharing of health information specific to behavioral health and substance use treatment in accordance with Public Act 129 of 2014. In Michigan, while providers are not required to use this new standard form (MDHHS-5515), they are required to accept it. <br/> Usage Note: For legislative background, current MDHHS-5515 consent directive form, and provider and patient FAQs see http://www.michigan.gov/mdhhs/0,5885,7-339 -71550_2941_58005-343686--,00.html <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInformationActionPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationActionPolicy"> </a> </td> <td> The type of action permitted on information by jurisdictional, organizational, or personal policy. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOACCESS <a name="v3-ActCode-INFOACCESS"> </a> </td> <td> access information</td> <td> Authorization to obtain information with no further permission to collect and store it. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOCOLLECT <a name="v3-ActCode-INFOCOLLECT"> </a> </td> <td> collect information</td> <td> Authorization to gather and store information. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFODEIDENTIFIY <a name="v3-ActCode-INFODEIDENTIFIY"> </a> </td> <td> deidentify information</td> <td> Authorization to alter or remove identifying characteristics of an entity or individual that is a subject of the information. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFODISCLOSE <a name="v3-ActCode-INFODISCLOSE"> </a> </td> <td> disclose information</td> <td> Authorization to make information known to another party. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOMASK <a name="v3-ActCode-INFOMASK"> </a> </td> <td> mask information</td> <td> Authorization to alter information in order to conceal it from unauthorized recipients. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOREADONLY <a name="v3-ActCode-INFOREADONLY"> </a> </td> <td> read only information</td> <td> Authorization to access information within a specific context for communication purposes only. Storing, manipulating, and further disclosure are prohibited and may be technically disabled. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOREDACT <a name="v3-ActCode-INFOREDACT"> </a> </td> <td> redact information</td> <td> Authorization to remove information that a recipient is not authorized to access. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOREDISCLOSE <a name="v3-ActCode-INFOREDISCLOSE"> </a> </td> <td> redisclose information</td> <td> Authorization to make disclosed information known to another party. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOREIDENTIFY <a name="v3-ActCode-INFOREIDENTIFY"> </a> </td> <td> reidentify information</td> <td> Authorization to alter or relink deidentified information so that an entity or individual that is the subject of that information identifiable. <br/> </td> </tr> <tr> <td> 3</td> <td>     INFOUSE <a name="v3-ActCode-INFOUSE"> </a> </td> <td> use information</td> <td> Authorization to employ or alter information. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActInformationPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationPolicy"> </a> </td> <td> Information management directives related to privacy, security, integrity, and control concerns, which may be governed by specific laws; based on private sector self-governance; adopted "best practices" recognized by a community of interest; or terms of license, participation, or service as implemented in jurisdictional, organizational, or personal policies. <br/> </td> </tr> <tr> <td> 3</td> <td>     JurisIP <a name="v3-ActCode-JurisIP"> </a> </td> <td> jurisdictional information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of information as defined by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisCUI <a name="v3-ActCode-JurisCUI"> </a> </td> <td> jurisdictional controlled unclassified information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of controlled unclassified information as defined by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisDEID <a name="v3-ActCode-JurisDEID"> </a> </td> <td> jurisdictional de-identified information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of de-identified information as defined by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisLDS <a name="v3-ActCode-JurisLDS"> </a> </td> <td> jurisdictional limited data set</td> <td> Jurisdictional policy on collection, access, use, or disclosure of information in a limited data set as defined by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisNSI <a name="v3-ActCode-JurisNSI"> </a> </td> <td> jurisdictional non-sensitive information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of information deemed non-sensitive by applicable jurisdiction law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisPI <a name="v3-ActCode-JurisPI"> </a> </td> <td> jurisdictional public information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of information deemed public by applicable jurisdiction law. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisSP-CUI <a name="v3-ActCode-JurisSP-CUI"> </a> </td> <td> jurisdictional specified controlled unclassified information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by applicable jurisdictional policy. <br/> </td> </tr> <tr> <td> 4</td> <td>       JurisUUI <a name="v3-ActCode-JurisUUI"> </a> </td> <td> jurisdictional uncontrolled unclassified information policy</td> <td> Jurisdictional policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by applicable jurisdictional policy. <br/> </td> </tr> <tr> <td> 3</td> <td>     OrgIP <a name="v3-ActCode-OrgIP"> </a> </td> <td> organizational information policy</td> <td> Organizational policy on collection, access, use, or disclosure of information, which does not conflict with jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgCUI <a name="v3-ActCode-OrgCUI"> </a> </td> <td> organizational basic controlled unclassified information policy</td> <td> Organizational policy on collection, access, use, or disclosure of basic controlled unclassified information as defined by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgDEID <a name="v3-ActCode-OrgDEID"> </a> </td> <td> organizational de-identified informati)on policy</td> <td> Organizational policy on collection, access, use, or disclosure of de-identified information as defined by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgLDS <a name="v3-ActCode-OrgLDS"> </a> </td> <td> organizational limited data set information policy</td> <td> Organizational policy on collection, access, use, or disclosure of information in a limited data set as defined by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgNSI <a name="v3-ActCode-OrgNSI"> </a> </td> <td> organizational non-sensitive information policy</td> <td> Organizational policy on collection, access, use, or disclosure of information deemed non-sensitive by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgPI <a name="v3-ActCode-OrgPI"> </a> </td> <td> organizational public information policy</td> <td> Organizational policy on collection, access, use, or disclosure of public information as defined by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgSP-CUI <a name="v3-ActCode-OrgSP-CUI"> </a> </td> <td> organizational specified controlled unclassified information policy</td> <td> Organizational policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by the organization or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       OrgUUI <a name="v3-ActCode-OrgUUI"> </a> </td> <td> organizational uncontrolled unclassified information policy</td> <td> Organizational policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by the organization or governing jurisdiction. <br/> </td> </tr> <tr> <td> 3</td> <td>     PersIP <a name="v3-ActCode-PersIP"> </a> </td> <td> personal information policy</td> <td> Personal policy on collection, access, use, or disclosure of information. <br/> </td> </tr> <tr> <td> 4</td> <td>       PersDEID <a name="v3-ActCode-PersDEID"> </a> </td> <td> personal de-identified information policy</td> <td> Personal policy on collection, access, use, or disclosure of de-identified information as defined by the information subject or by applicable jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       PersLDS <a name="v3-ActCode-PersLDS"> </a> </td> <td> personal limited data set information policy</td> <td> Personal policy personal policy on collection, access, use, or disclosure of information in a limited data set by the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       PersNSI <a name="v3-ActCode-PersNSI"> </a> </td> <td> personal non-sensitive information policy</td> <td> Personal policy on collection, access, use, or disclosure of information deemed non-sensitive by the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       PersPI <a name="v3-ActCode-PersPI"> </a> </td> <td> personal public information policy</td> <td> Personal policy on collection, access, use, or disclosure of information deemed public by the information subject. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActPrivacyPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPrivacyPolicy"> </a> </td> <td> A policy deeming certain information to be private to an individual or organization. <br/> Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy. <br/> Discussion: ActPrivacyPolicyType codes support the designation of the 1..* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor. 1..* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode. Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates. <br/> Usage Note: Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActConsentDirective)</i> </span> <b> <i> Abstract</i> </b> <b> <i> Deprecated</i> </b> </td> <td> <a name="v3-ActCode-_ActConsentDirective"> </a> </td> <td> Specifies the type of agreement between one or more grantor and grantee in which rights and obligations related to one or more shared items of interest are allocated. <br/> Usage Note: Such agreements may be considered "consent directives" or "contracts" depending on the context, and are considered closely related or synonymous from a legal perspective. <br/> Examples: <br/> Healthcare Privacy Consent Directive permitting or restricting in whole or part the collection, access, use, and disclosure of health information, and any associated handling caveats. Healthcare Medical Consent Directive to receive medical procedures after being informed of risks and benefits, thereby reducing the grantee's liability. Research Informed Consent for participation in clinical trials and disclosure of health information after being informed of risks and benefits, thereby reducing the grantee's liability. Substitute decision maker delegation in which the grantee assumes responsibility to act on behalf of the grantor. Contracts in which the agreement requires assent/dissent by the grantor of terms offered by a grantee, a consumer opts out of an "award" system for use of a retailer's marketing or credit card vendor's point collection cards in exchange for allowing purchase tracking and profiling. A mobile device or App privacy policy and terms of service to which a user must agree in whole or in part in order to utilize the service. Agreements between a client and an authorization server or between an authorization server and a resource operator and/or resource owner permitting or restricting e.g., collection, access, use, and disclosure of information, and any associated handling caveats. </td> </tr> <tr> <td> 4</td> <td>       EMRGONLY <a name="v3-ActCode-EMRGONLY"> </a> </td> <td> emergency only</td> <td> Privacy consent directive restricting or prohibiting access, use, or disclosure of personal information, including de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, which may be used to identify an individual in a registry or repository for all purposes except for emergency treatment generally, which may include treatment during a disaster, a threat, in an emergency department and for break the glass purposes of use as specified by applicable domain policy. <br/> Usage Note: To specify the scope of an “EMRGONLYâ€? consent directive within a policy domain, use one or more of the following Purpose of Use codes in the ActReason code system OID: 2.16.840.1.113883.5.8. <br/> ETREAT (Emergency Treatment): To perform one or more operations on information for provision of immediately needed health care for an emergent condition. BTG (break the glass): To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access. ERTREAT (emergency 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. THREAT (threat): To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence. DISASTER (disaster): To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone. Map: An “emergency onlyâ€? consent directive maps to ISO/TS 17975:2015(E) 5.13 Exceptional access <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#GRANTORCHOICE">GRANTORCHOICE</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#IMPLIED">IMPLIED</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#IMPLIEDD">IMPLIEDD</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#NOCONSENT">NOCONSENT</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       NOPP <a name="v3-ActCode-NOPP"> </a> </td> <td> notice of privacy practices</td> <td> An implied privacy consent directive or notification, which the data subject may or may not acknowledge. The notification specifies permitted actions, which may include access, use, or disclosure of any and all personal information. The notification specifies the scope of personal information, which may include de-identified information, and personal effects, such as biometrics, biospecimen or genetic material, that may be used to identify an individual in a registry or repository. The notification specifies the purposes for which personal information may be used such as treatment, payment, operations, research, information exchange, public health, disaster, quality and safety reporting; as required by law including court order, law enforcement, national security, military authorities; and for data analytics, marketing, and profiling. <br/> Usage Notes: Map: An "implied" consent directive maps to ISO/TS 17975:2015(E) definition forImplied: Consent to Collect, Use and Disclose personal health information is implied by the actions or inactions of the individual and the circumstances under which it was implied". <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#OPTIN">OPTIN</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#OPTINR">OPTINR</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#OPTOUT">OPTOUT</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#OPTOUTE">OPTOUTE</a> </td> <td/> <td/> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActPrivacyLaw)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPrivacyLaw"> </a> </td> <td> A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on: <br/> The activity of a governed party The behavior of a governed party The manner in which an act is executed by a governed party </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActGDPRPrivacyLaw)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActGDPRPrivacyLaw"> </a> </td> <td> GDPR is a regulation on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (Data Protection Directive). Promulgated by the European Parliament and Council of the European Union. Regulation available at L119, 4 May 2016, p. 1–88. <br/> GDPR privacy policies specifying types of lawful personal data processing based on a controller meeting one or more processing condition such as specified by law, compliance with data controller legal obligations, protection of data subject’s vital interests, perform tasks in the public interest, related to legal claims, research and statistics, management of health or social care systems, legitimate interests of controller or third party. Processing sensitive personal data, including genetic, biometric and health data, as well as personal data from which racial and ethnic origin, political opinions, religious or ideological convictions or membership in a union can be attributed to a person, requires meeting at least one sensitive personal processing condition. <br/> GDPR ‘processing’ means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. Article 4 https://gdpr-info.eu/art-4-gdpr/ <br/> Usage Note: <br/> Confidentiality: e.g., U (unrestricted) for anonymized personal information; L (low) for pseudonymized U (unrestricted) for anonymized personal information; M (moderate) for indirectly identifiable information such as test scores and work times; N (normal) for personal information; and R (restricted) for sensitive personal information DPR sensitivity [personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation, some of which are defined at Article 4 https://gdpr-info.eu/art-4-gdpr/ GDPR processing policies and GDPR ConsentDirectiveTypes, such as data subject consent and research consent. Other security category codes, such as compartment codes for legitimate relationship, Handling instructions including Purpose of use stipulated in a GDPR consent or contract restricting processing or related to the scope of the processing policy such as public health, research, and legal obligations Obligation policies such as GDPR Information Obligations https://gdpr-inf o.eu/issues/information-obligations, data minimization and deleting when processing is complete Refrain policies such as no relinking See Intersoft GDPR at https://gdpr-info.eu/issues/personal-data/ Art. 4 GDPR Definitions https://gdpr-info.eu/art-4-gdpr/ Art. 9 GDPR Processing of special categories of personal data https://gdpr-info.eu/art-9-gdpr/ Relevant Recitals (26) Not applicable to anonymous data (30) Online identifiers for profiling and identification (34) Genetic data (35) Health data (51) Protecting sensitive personal data at Intersoft GDPR briefing papers and navigating tool https://gdpr-info.eu/ <br/> Authorities <br/> European Data Protection Supervisor - Security Measures for Personal Data Processing (Link) Data Protection Authority Isle of Man - Know your data – Mapping the 5 W’s (Link) Data Protection Authority UK - Key definitions (Link) European Commission - What is personal data? (Link) European Commission - What personal data is considered sensitive? (Link) EU publications - Handbook on European data protection law – Personal data, page 83 (Link) Expert contribution A&L Goodbody - The GDPR: A Guide for Businesses – Definition of Personal & Sensitive Data, Page 8 (Link) Bird & Bird - Sensitive data and lawful processing (Link) https://ec.europa.eu/commission/priorities/justice-and-fundamental-rights/data-protection/2018-refor m-eu-data-protection-rules_en General Data Protection Regulation https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1528874672298&uri=CELEX%3A32016R0679 Communication on data protection – guidance on direct application of the GDPR http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1517578296944&uri=CELEX%3A52018DC0043 Intersoft GDPR briefing papers and navigating tool https://gdpr-info.eu/ <br/> </td> </tr> <tr> <td> 5</td> <td>         GDPRCONSENT <a name="v3-ActCode-GDPRCONSENT"> </a> </td> <td> GDPR Consent</td> <td> Processing of personal data, inclusive of the special categories of data, is lawful only if the data subject has given explicit consent to the processing of his or her personal data, inclusive of the special categories of data, for one or more specific purposes, except where Union or Member State law provide that the prohibition to use the data may not be lifted by the data subject; and for personal data which are manifestly made public by the data subject. <br/> Usage Note: The description is based on the following GDPR provisions: Article 6.1.a https://gdpr-info.eu/art-6-gdpr/ 1Processing shall be lawful only if and to the extent that at least one of the following applies: (a) the data subject has given consent to the processing of his or her personal data for one or more specific purposes. Article 9.1, 9.2a., 9.2.e https://gdpr-info.eu/art-9-gdpr/ 1. Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation shall be prohibited. 2. Paragraph 1 shall not apply if one of the following applies: (a) the data subject has given explicit consent to the processing of those personal data for one or more specified purposes, except where Union or Member State law provide that the prohibition referred to in paragraph 1 may not be lifted by the data subject; and (e) processing relates to personal data which are manifestly made public by the data subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       _ActUSPrivacyLaw <a name="v3-ActCode-_ActUSPrivacyLaw"> </a> </td> <td> _ActUSPrivacyLaw</td> <td> Definition: A jurisdictional mandate in the U.S. relating to privacy. <br/> Usage Note: ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1. <br/> </td> </tr> <tr> <td> 5</td> <td>         42CFRPart2 <a name="v3-ActCode-42CFRPart2"> </a> </td> <td> 42 CFR Part2</td> <td> A code representing 42 CFR Part 2 Confidentiality of Substance Use Disorder Patient Records. 42 CFR Part 2 stipulates the privacy rights of an individual who has applied for or been given diagnosis or treatment for alcohol or drug abuse at a federally assisted program, which includes non-disclosure of health information relating to health care paid for by a federally assisted substance use disorder program without patient consent. https://www.gpo.gov/fdsys/pkg/CFR-2010-title42-vol1/pdf/CFR-2010-title42-vol1-part 2.pdf <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, the collection, access, use, and disclosure of healthcare information is governed by 42 CFR Part 2 Confidentiality of Substance Use Disorder Patient Records https://www.gpo.gov/fdsys/pkg/CFR-2010-title42-vol1/pdf/CFR-2010-title42-vol1-part2.pdf use “42CFRPart2â€? as the security label policy code. <br/> Since information governed by a 42 CFR Part 2 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         a) HIPAAConsent <a name="v3-ActCode-a.41HIPAAConsent"> </a> </td> <td> HIPAA Consent</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.522), which stipulates the process by which a covered entity seeks agreement from an individual regarding how it will use and disclose the individual's protected health information for treatment, payment, and health care operations is termed a "consent." The Privacy Rule permits, but does not require, a covered entity to voluntarily obtain patient consent for uses and disclosures of protected health information for treatment, payment, and health care operations. Covered entities that do so have complete discretion to design a process that best suits their needs. From https://www.hhs.gov/hipaa/for-professionals/faq/264/what-is-the-di fference-between-consent-and-authorization/index.html. The provisions relating to consent are largely contained in Section 164.522 Rights to request privacy protection for protected health information https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec 164-522.pdf. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by 45 CFR Section 164.522 use “HIPAAConsentâ€? as the security label policy code. <br/> Since information governed by a 45 CFR Section 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-v ol1-sec164-506.pdf, assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         CommonRule <a name="v3-ActCode-CommonRule"> </a> </td> <td> Common Rule</td> <td> A code representing U.S. Federal laws governing research-related privacy policies known as the “Common Ruleâ€?. The Common Rule is the U.S. Federal regulations governing the protection of human subjects in research (codified at Subpart A of 45 CFR part 46), which has been adopted by 15 U.S. Federal departments and agencies in an effort to promote uniformity, understanding, and compliance with human subject protections. Existing regulations governing the protection of human subjects in Food and Drug Administration (FDA)-regulated research (21 CFR parts 50, 56, 312, and 812) are separate from the Common Rule but include similar requirements. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information or biospecimen is governed by the Common Rule use “COMMONRULEâ€? as the security label policy code. Information or biospecimen disclosed under the Common Rule are not protected by the HIPAA Privacy Rule. If protected under other laws such as confidentiality provisions under the Common Rule, assign the HL7 Confidentiality code “Mâ€? (moderate). <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAAuth <a name="v3-ActCode-HIPAAAuth"> </a> </td> <td> HIPAA Authorization for Disclosure</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508) Uses and disclosures for which an authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2 017-title45-vol1-sec164-508.pdf, which stipulates the process by which a covered entity seeks agreement from an individual to use or disclose protected health information for other purposes, or to authorize another covered entity to disclose protected health information to the requesting covered entity, are termed "authorizations". <br/> An “authorizationâ€? is required by the Privacy Rule for uses and disclosures of protected health information not otherwise allowed by the Rule. Where the Privacy Rule requires patient authorization, voluntary consent is not sufficient to permit a use or disclosure of protected health information unless it also satisfies the requirements of a valid authorization. An authorization is a detailed document that gives covered entities permission to use protected health information for specified purposes, which are generally other than treatment, payment, or health care operations, or to disclose protected health information to a third party specified by the individual. <br/> An authorization must specify a number of elements, including a description of the protected health information to be used and disclosed, the person authorized to make the use or disclosure, the person to whom the covered entity may make the disclosure, an expiration date, and, in some cases, the purpose for which the information may be used or disclosed. With limited exceptions, covered entities may not condition treatment or coverage on the individual providing an authorization. https://www.hhs.gov/hipaa/for-pr ofessionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html <br/> Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, where use or disclosure of healthcare information is governed by a covered entity’s HIPAA Authorization for Disclosure, use “HIPAAAuthâ€? as the security label policy code. <br/> Information disclosed under a HIPAA Authorization for Disclosure no longer has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is considered the “normâ€?, assign the HL7 Confidentiality code “Mâ€? (moderate), which may be protected under other laws such as the Federal Trade Commission privacy and security regulations. <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAANOPP <a name="v3-ActCode-HIPAANOPP"> </a> </td> <td> HIPAA notice of privacy practices</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.520), which stipulates an individual’s right to adequate notice of the uses and disclosures of protected health information that may be made by the covered entity, and of the individual's rights and the covered entity's legal duties with respect to protected health information. Relevant HIPAA Privacy Rule provisions are at Section 164.520 (a) Standard: Notice of privacy practices. https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-520. pdf <br/> Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, if collection, access, use, or disclosure of healthcare information is governed by a covered entity’s HIPAA Notice of Privacy Practices, use “HIPAANOPPâ€? as the security label policy code. <br/> Information governed under a HIPAA Notice of Privacy Practices has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.go v/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf , which is considered the “normâ€?, assign the HL7 Confidentiality code “Nâ€? (normal). <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAPsyNotes <a name="v3-ActCode-HIPAAPsyNotes"> </a> </td> <td> HIPAA psychotherapy notes</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule (45 CFR Section 164.508), which stipulates the privacy rights of an individual who is the subject of psychotherapy notes, and requires authorization for certain uses and disclosure of that information. <br/> Definition of Psychotherapy notes 45 CFR Section 164.501 https://www.gpo.go v/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-501.pdf: Psychotherapy notes means notes recorded (in any medium) by a health care provider who is a mental health professional documenting or analyzing the contents of conversation during a private counseling session or a group, joint, or family counseling session and that are separated from the rest of the individual's medical record. Psychotherapy notes excludes medication prescription and monitoring, counseling session start and stop times, the modalities and frequencies of treatment furnished, results of clinical tests, and any summary of the following items: Diagnosis, functional status, the treatment plan, symptoms, prognosis, and progress to date. <br/> See Section 164.508 Uses and disclosures for which an authorization is required. (2)Authorization required: Psychotherapy notes https://www.gpo.gov/fdsys/pkg/CFR-2017-t itle45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf: Notwithstanding any provision of this subpart, other than the transition provisions in Section 164.532, a covered entity must obtain an authorization for any use or disclosure of psychotherapy notes, except: (i) To carry out the following treatment, payment, or health care operations: (A) Use by the originator of the psychotherapy notes for treatment; (B) Use or disclosure by the covered entity for its own training programs in which students, trainees, or practitioners in mental health learn under supervision to practice or improve their skills in group, joint, family, or individual counseling; or (C) Use or disclosure by the covered entity to defend itself in a legal action or other proceeding brought by the individual; and (ii) A use or disclosure that is required by Section 164.502(a)(2)(ii) or permitted by Section 164.512(a); Section 164.512(d) with respect to the oversight of the originator of the psychotherapy notes; Section 164.512(g)(1); Section 164.512(j)(1)(i). <br/> Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, the collection, access, use, or disclosure of healthcare information is governed by HIPAA 45 CFR 164.508 (2) Authorization required: Psychotherapy notes https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title 45-vol1-sec164-506.pdf , use “HIPAAPsyNotesâ€? as the security label policy code. <br/> Since information governed by a HIPAA 45 CFR 164.508 (2) has a level of confidentiality protection that is more stringent than the normal level of protection under 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1 -sec164-506.pdf, assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAAROA <a name="v3-ActCode-HIPAAROA"> </a> </td> <td> HIPAA Right of Access</td> <td> A code representing U.S. Public Law 104-191 Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule 45 CFR Section 164.524 Access of individuals to protected health information https://www.govinfo.gov/app/details/CFR-2017-title45-vol1/CFR-2017-t itle45-vol1-sec164-524, which stipulates that an individual has a right of access to inspect and obtain a copy of protected health information about the individual in a designated record set, for as long as the protected health information is maintained in the designated record set with exceptions stipulated in HIPAA Privacy Rule Section 164.524. Exceptions include psychotherapy notes and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding. <br/> If an individual's request for access directs the covered entity to transmit the copy of protected health information directly to another person designated by the individual, the covered entity must provide the copy to the person designated by the individual. The individual's request must be in writing, signed by the individual, and clearly identify the designated person and where to send the copy of protected health information. <br/> For discussion on extent of right, grounds for denial, and documentation requirements see: HHS Individuals’ Right under HIPAA to Access their Health Information 45 CFR Section 164.524 https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.htm l and HHS FAQ on Right of Access vs. HIPAA Authorization https://www.hhs.gov/hipaa/for-professionals /faq/2041/why-depend-on-the-individuals-right/index.html <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed under 45 CFR Section 164.5224 use “HIPAAROAâ€? as the security label policy code. <br/> Information disclosed under a HIPAA 42 CFR Section 164.524 no longer has the level of confidentiality protection afforded under the 45 CFR Section 164.506 - Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.go v/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-508.pdf, which is considered the “normâ€?, assign the HL7 Confidentiality code “Mâ€? (moderate), which may be protected under other laws such as the Federal Trade Commission privacy and security regulations. <br/> </td> </tr> <tr> <td> 5</td> <td>         HIPAASelfPay <a name="v3-ActCode-HIPAASelfPay"> </a> </td> <td> HIPAA self-pay</td> <td> A code representing 45 CFR 164.522 Rights to request privacy protection for protected health information, which is a US Federal law stipulating the privacy rights of an individual to restrict disclosure of information related to health care items or services for which the individual pays out of pocket in full to a health plan or payer. <br/> See 45 CFR 164.522 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/C FR-2017-title45-vol1-sec164-522.pdf. (vi) A covered entity must agree to the request of an individual to restrict disclosure of protected health information about the individual to a health plan if: (A) The disclosure is for the purpose of carrying out payment or health care operations and is not otherwise required by law; and (B) The protected health information pertains solely to a health care item or service for which the individual, or person other than the health plan on behalf of the individual, has paid the covered entity in full. <br/> Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In this case, the collection, access, use, or disclosure of healthcare information is governed by HIPAA 45 CFR 164.522 https://www.gpo.gov/fdsy s/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf use “HIPAASelfPayâ€? as the security label policy code. <br/> Since information governed by a HIPAA 45 CFR 164.522 has a level of confidentiality protection that is more stringent than the normal level of protection under 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1 -sec164-506.pdf, assign the HL7 Confidentiality code “Râ€? (restricted). <br/> </td> </tr> <tr> <td> 5</td> <td>         Title38Section7332 <a name="v3-ActCode-Title38Section7332"> </a> </td> <td> Title 38 Section 7332</td> <td> A code representing Title 38 Section 7332, which is a US Federal law stipulating the privacy rights of veterans diagnosed and treated for substance use disorders, infection with the human immunodeficiency virus, or sickle cell anemia. <br/> https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-pa rtV-chap73-subchapIII-sec7332/content-detail.html . (1) Records of the identity, diagnosis, prognosis, or treatment of any patient or subject which are maintained in connection with the performance of any program or activity (including education, training, treatment, rehabilitation, or research) relating to drug abuse, alcoholism or alcohol abuse, infection with the human immunodeficiency virus, or sickle cell anemia which is carried out by or for the Department under this title shall, except as provided in subsections (e) and (f), be confidential, and (section 5701 of this title to the contrary notwithstanding) such records may be disclosed only for the purposes and under the circumstances expressly authorized under subsection (b). (2) Paragraph (1) prohibits the disclosure to any person or entity other than the patient or subject concerned of the fact that a special written consent is required in order for such records to be disclosed. (b) (1) The content of any record referred to in subsection (a) may be disclosed by the Secretary in accordance with the prior written consent of the patient or subject with respect to whom such record is maintained, but only to such extent, under such circumstances, and for such purposes as may be allowed in regulations prescribed by the Secretary. (2) Whether or not any patient or subject, with respect to whom any given record referred to in subsection (a) is maintained, gives written consent, the content of such record may be disclosed by the Secretary as follows: (A) To medical personnel to the extent necessary to meet a bona fide medical emergency. (B) To qualified personnel for the purpose of conducting scientific research, management audits, financial audits, or program evaluation, but such personnel may not identify, directly or indirectly, any individual patient or subject in any report of such research, audit, or evaluation, or otherwise disclose patient or subject identities in any manner. (C) (i) In the case of any record which is maintained in connection with the performance of any program or activity relating to infection with the human immunodeficiency virus, to a Federal, State, or local public-health authority charged under Federal or State law with the protection of the public health, and to which Federal or State law requires disclosure of such record, if a qualified representative of such authority has made a written request that such record be provided as required pursuant to such law for a purpose authorized by such law. (ii) A person to whom a record is disclosed under this paragraph may not redisclose or use such record for a purpose other than that for which the disclosure was made. (D) If authorized by an appropriate order of a court of competent jurisdiction granted after application showing good cause therefor. In assessing good cause the court shall weigh the public interest and the need for disclosure against the injury to the patient or subject, to the physician-patient relationship, and to the treatment services. Upon the granting of such order, the court, in determining the extent to which any disclosure of all or any part of any record is necessary, shall impose appropriate safeguards against unauthorized disclosure. (E) To an entity described in paragraph (1)(B) of section 5701(k) of this title, but only to the extent authorized by such section. (F) (i) To a representative of a patient who lacks decision-making capacity, when a practitioner deems the content of the given record necessary for that representative to make an informed decision regarding the patient's treatment. (ii) In this subparagraph, the term “representativeâ€? means an individual, organization, or other body authorized under section 7331 of this title and its implementing regulations to give informed consent on behalf of a patient who lacks decision-making capacity. (G) To a State controlled substance monitoring program, including a program approved by the Secretary of Health and Human Services under section 399O of the Public Health Service Act (42 U.S.C. 280g-3), to the extent necessary to prevent misuse and diversion of prescription medicines. (H) (i) To a non-Department entity (including private entities and other Federal agencies) for purposes of providing health care, including hospital care, medical services, and extended care services, to Veterans or performing other health care-related activities or functions. (ii) An entity to which a record is disclosed under this subparagraph may not disclose or use such record for a purpose other than that for which the disclosure was made or as permitted by law. (I) To a third party in order to recover or collect reasonable charges for care furnished to, or paid on behalf of, a Veteran in connection with a non-service connected disability as permitted by section 1729 of this title or for a condition for which recovery is authorized or with respect to which the United States is deemed to be a third party beneficiary under the Act entitled 'An Act to provide for the recovery from tortiously liable third persons of the cost of hospital and medical care and treatment furnished by the United States' (Public Law 87-693; 42 U.S.C. 2651 et seq.; commonly known as the 'Federal Medical Care Recovery Act'). <br/> Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In this case, where collection, access, use, or disclosure of healthcare information is governed by 38 U.S. Code Section 7332 - Confidentiality of certain medical records https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-partV-chap73-subchapIII-se c7332/content-detail.html use "Title38Section7332" as the security label policy code. <br/> Since information governed by a Title 38 Section 7332 has a level of confidentiality protection that is more stringent than the normal level of protection under HIPAA 45 CFR Section 164.506 Uses and disclosures to carry out treatment, payment, or health care operations https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-v ol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted). <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_InformationSensitivityPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_InformationSensitivityPolicy"> </a> </td> <td> A mandate, obligation, requirement, rule, or expectation characterizing the value or importance of a resource and may include its vulnerability. (Based on ISO7498-2:1989. Note: The vulnerability of personally identifiable sensitive information may be based on concerns that the unauthorized disclosure may result in social stigmatization or discrimination.) Description: Types of Sensitivity policy that apply to Acts or Roles. A sensitivity policy is adopted by an enterprise or group of enterprises (a 'policy domain') through a formal data use agreement that stipulates the value, importance, and vulnerability of information. A sensitivity code representing a sensitivity policy may be associated with criteria such as categories of information or sets of information identifiers (e.g., a value set of clinical codes or branch in a code system hierarchy). These criteria may in turn be used for the Policy Decision Point in a Security Engine. A sensitivity code may be used to set the confidentiality code used on information about Acts and Roles to trigger the security mechanisms required to control how security principals (i.e., a person, a machine, a software application) may act on the information (e.g., collection, access, use, or disclosure). Sensitivity codes are never assigned to the transport or business envelope containing patient specific information being exchanged outside of a policy domain as this would disclose the information intended to be protected by the policy. When sensitive information is exchanged with others outside of a policy domain, the confidentiality code on the transport or business envelope conveys the receiver's responsibilities and indicates the how the information is to be safeguarded without unauthorized disclosure of the sensitive information. This ensures that sensitive information is treated by receivers as the sender intends, accomplishing interoperability without point to point negotiations. <br/> Usage Note: Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an employee's sensitivity code would make little sense for use outside of a policy domain. 'Taboo' would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable InformationSensitivityPolicy Act.code may be useful in some scenarios if used in combination with a sensitivity identifier and/or Act.title. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActInformationSensitivityPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActInformationSensitivityPolicy"> </a> </td> <td> Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." <br/> Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. <br/> </td> </tr> <tr> <td> 5</td> <td>         ETH <a name="v3-ActCode-ETH"> </a> </td> <td> substance abuse information sensitivity</td> <td> Policy for handling alcohol or drug-abuse information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to alcohol or drug-abuse information that is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         GDIS <a name="v3-ActCode-GDIS"> </a> </td> <td> genetic disease information sensitivity</td> <td> Policy for handling genetic disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to genetic disease information that is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         HIV <a name="v3-ActCode-HIV"> </a> </td> <td> HIV/AIDS information sensitivity</td> <td> Policy for handling HIV or AIDS information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to HIV or AIDS information that is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         MST <a name="v3-ActCode-MST"> </a> </td> <td> military sexual trauma information sensitivity</td> <td> Policy for handling information related to sexual assault or repeated, threatening sexual harassment that occurred while the patient was in the military, which is afforded heightened confidentiality. <br/> Access control concerns for military sexual trauma is based on the patient being subject to control by a higher ranking military perpetrator and/or censure by others within the military unit. Due to the relatively unfettered access to healthcare information by higher ranking military personnel and those who have command over the patient, there is a need to sequester this information outside of the typical controls on access to military health records. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         PREGNANT <a name="v3-ActCode-PREGNANT"> </a> </td> <td> pregnancy information sensitivity</td> <td> Policy for handling information about an individual's current or past pregnancy status, deemed sensitive by the individual or by policy, which may be afforded heightened confidentiality. <br/> Usage Note: <br/> Information about a patient's current or past pregnancy status may be considered sensitive in circumstances in which that status could result in discrimination or stigmatization. </td> </tr> <tr> <td> 5</td> <td>         SCA <a name="v3-ActCode-SCA"> </a> </td> <td> sickle cell anemia information sensitivity</td> <td> Policy for handling sickle cell disease information, which is afforded heightened confidentiality. Information handling protocols are based on organizational policies related to sickle cell disease information, which is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then the Act valued with this ActCode should be associated with an Act valued with any applicable laws from the ActPrivacyLaw code system. <br/> </td> </tr> <tr> <td> 5</td> <td>         SDV <a name="v3-ActCode-SDV"> </a> </td> <td> sexual assault, abuse, or domestic violence information sensitivity</td> <td> Policy for handling sexual assault, abuse, or domestic violence information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexual assault, abuse, or domestic violence information that is deemed sensitive. <br/> SDV code covers violence perpetrated by related and non-related persons. This code should be specific to physical and mental trauma caused by a related person only. The access control concerns are keeping the patient safe from the perpetrator who may have an abusive psychological control over the patient, may be stalking the patient, or may try to manipulate care givers into allowing the perpetrator to make contact with the patient. The definition needs to be clarified. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         SEX <a name="v3-ActCode-SEX"> </a> </td> <td> sexuality and reproductive health information sensitivity</td> <td> Policy for handling sexuality and reproductive health information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexuality and reproductive health information that is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         SPI <a name="v3-ActCode-SPI"> </a> </td> <td> specially protected information sensitivity</td> <td> Policy for handling information deemed specially protected by law or policy including substance abuse, substance use, psychiatric, mental health, behavioral health, and cognitive disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 6</td> <td>           BH <a name="v3-ActCode-BH"> </a> </td> <td> behavioral health information sensitivity</td> <td> Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 7</td> <td>             COGN <a name="v3-ActCode-COGN"> </a> </td> <td> cognitive disability information sensitivity</td> <td> Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> Examples may include dementia, traumatic brain injury, attention deficit, hearing and visual disability such as dyslexia and other disorders and related conditions which impair learning and self-sufficiency. However, the cognitive disabilities to which this term may apply versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. <br/> </td> </tr> <tr> <td> 7</td> <td>             DVD <a name="v3-ActCode-DVD"> </a> </td> <td> developmental disability information sensitivity</td> <td> Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> A diverse group of chronic conditions that are due to mental or physical impairments impacting activities of daily living, self-care, language acuity, learning, mobility, independent living and economic self-sufficiency. Examples may include Down syndrome and Autism spectrum. However, the developmental disabilities to which this term applies versus other behavioral health categories varies by jurisdiction and organizational policy in part due to overlap with other behavioral health conditions. Implementers should constrain to those diagnoses applicable in the domain in which this code is used. <br/> </td> </tr> <tr> <td> 7</td> <td>             EMOTDIS <a name="v3-ActCode-EMOTDIS"> </a> </td> <td> emotional disturbance information sensitivity</td> <td> Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> Typical used to characterize behavioral and mental health issues of adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term. <br/> </td> </tr> <tr> <td> 6</td> <td>           MH <a name="v3-ActCode-MH"> </a> </td> <td> mental health information sensitivity</td> <td> Policy for handling information related to psychological disorders, which is afforded heightened confidentiality. Mental health information may be deemed specifically sensitive and distinct from physical health, substance use disorders, and behavioral disabilities and disorders in some jurisdictions. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 6</td> <td>           PSY <a name="v3-ActCode-PSY"> </a> </td> <td> psychiatry disorder information sensitivity</td> <td> Policy for handling psychiatry psychiatric disorder information, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 6</td> <td>           PSYTHPN <a name="v3-ActCode-PSYTHPN"> </a> </td> <td> psychotherapy note information sensitivity</td> <td> Policy for handling psychotherapy note information, which is afforded heightened confidentiality. <br/> Usage Note: In some jurisdiction, disclosure of psychotherapy notes requires patient consent. <br/> If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 6</td> <td>           SUD <a name="v3-ActCode-SUD"> </a> </td> <td> substance use disorder information sensitivity</td> <td> Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 7</td> <td>             ETHUD <a name="v3-ActCode-ETHUD"> </a> </td> <td> alcohol use disorder information sensitivity</td> <td> Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 7</td> <td>             OPIOIDUD <a name="v3-ActCode-OPIOIDUD"> </a> </td> <td> opioid use disorder information sensitivity</td> <td> Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         STD <a name="v3-ActCode-STD"> </a> </td> <td> sexually transmitted disease information sensitivity</td> <td> Policy for handling sexually transmitted disease information, which will be afforded heightened confidentiality. Information handling protocols based on organizational policies related to sexually transmitted disease information that is deemed sensitive. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         TBOO <a name="v3-ActCode-TBOO"> </a> </td> <td> taboo</td> <td> Policy for handling information not to be initially disclosed or discussed with patient except by a physician assigned to patient in this case. Information handling protocols based on organizational policies related to sensitive patient information that must be initially discussed with the patient by an attending physician before being disclosed to the patient. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> Open Issue: This definition conflates a rule and a characteristic, and there may be a similar issue with ts sibling codes. <br/> </td> </tr> <tr> <td> 5</td> <td>         VIO <a name="v3-ActCode-VIO"> </a> </td> <td> violence information sensitivity</td> <td> Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person. <br/> Access control concerns for information about mental or physical harm resulting from violence caused by an unrelated person may include manipulation of care givers or access to records that enable the perpetrator contact or locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         SICKLE <a name="v3-ActCode-SICKLE"> </a> </td> <td> sickle cell</td> <td> Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." <br/> Usage Note: ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_EntitySensitivityPolicyType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_EntitySensitivityPolicyType"> </a> </td> <td> Types of sensitivity policies that may apply to a sensitive attribute on an Entity. <br/> Usage Note: EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." <br/> </td> </tr> <tr> <td> 5</td> <td>         DEMO <a name="v3-ActCode-DEMO"> </a> </td> <td> all demographic information sensitivity</td> <td> Policy for handling all demographic information about an information subject, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to all demographic about an information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         DOB <a name="v3-ActCode-DOB"> </a> </td> <td> date of birth information sensitivity</td> <td> Policy for handling information related to an information subject's date of birth, which will be afforded heightened confidentiality.Policies may govern sensitivity of information related to an information subject's date of birth, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         GENDER <a name="v3-ActCode-GENDER"> </a> </td> <td> gender and sexual orientation information sensitivity</td> <td> Policy for handling information related to an information subject's gender and sexual orientation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's gender and sexual orientation, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         LIVARG <a name="v3-ActCode-LIVARG"> </a> </td> <td> living arrangement information sensitivity</td> <td> Policy for handling information related to an information subject's living arrangement, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's living arrangement, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         MARST <a name="v3-ActCode-MARST"> </a> </td> <td> marital status information sensitivity</td> <td> Policy for handling information related to an information subject's marital status, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's marital status, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         PATLOC <a name="v3-ActCode-PATLOC"> </a> </td> <td> patient location</td> <td> Policy for handling information related to an individual's location, which is deemed sensitive when the disclosure could impact the privacy, well-being, or safety of that subject, and requires additional protection. <br/> Usage Note: If there is a jurisdictional, organizational, or individual mandate, then use the applicable ActPrivacyLaw or ActConsentDirective code from the ActCode system to and specify the law in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         RACE <a name="v3-ActCode-RACE"> </a> </td> <td> race information sensitivity</td> <td> Policy for handling information related to an information subject's race, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's race, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         REL <a name="v3-ActCode-REL"> </a> </td> <td> religion information sensitivity</td> <td> Policy for handling information related to an information subject's religious affiliation, which will be afforded heightened confidentiality. Policies may govern sensitivity of information related to an information subject's religion, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_RoleInformationSensitivityPolicy)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_RoleInformationSensitivityPolicy"> </a> </td> <td> Types of sensitivity policies that apply to Roles. <br/> Usage Notes: RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity." <br/> </td> </tr> <tr> <td> 5</td> <td>         B <a name="v3-ActCode-B"> </a> </td> <td> business information sensitivity</td> <td> Policy for handling trade secrets such as financial information or intellectual property, which will be afforded heightened confidentiality. Description: Since the service class can represent knowledge structures that may be considered a trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. <br/> Usage Notes: No patient related information may ever be of this confidentiality level. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         EMPL <a name="v3-ActCode-EMPL"> </a> </td> <td> employer information sensitivity</td> <td> Policy for handling information related to an employer which is deemed classified to protect an employee who is the information subject, and which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to an employer, such as law enforcement or national security, the identity of which could impact the privacy, well-being, or safety of an information subject who is an employee. <br/> Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         LOCIS <a name="v3-ActCode-LOCIS"> </a> </td> <td> location information sensitivity</td> <td> Policy for handling information related to the location of the information subject, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to the location of the information subject, the disclosure of which could impact the privacy, well-being, or safety of that subject. <br/> Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 5</td> <td>         SSP <a name="v3-ActCode-SSP"> </a> </td> <td> sensitive service provider information sensitivity</td> <td> Policy for handling information related to a provider of sensitive services, which will be afforded heightened confidentiality. Description: Policies may govern sensitivity of information related to providers who deliver sensitive healthcare services in order to protect the privacy, well-being, and safety of the provider and of patients receiving sensitive services. <br/> Usage Notes: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       ADOL <a name="v3-ActCode-ADOL"> </a> </td> <td> adolescent information sensitivity</td> <td> Policy for handling information related to an adolescent, which will be afforded heightened confidentiality per applicable organizational or jurisdictional policy. An enterprise may have a policy that requires that adolescent patient information be provided heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. <br/> Usage Note: For use within an enterprise in which an adolescent is the information subject. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       CEL <a name="v3-ActCode-CEL"> </a> </td> <td> celebrity information sensitivity</td> <td> Policy for handling information related to a celebrity (people of public interest (VIP), which will be afforded heightened confidentiality. Celebrities are people of public interest (VIP) about whose information an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive may include health information and patient role information including patient status, demographics, next of kin, and location. <br/> Usage Note: For use within an enterprise in which the information subject is deemed a celebrity or very important person. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       DIA <a name="v3-ActCode-DIA"> </a> </td> <td> diagnosis information sensitivity</td> <td> Policy for handling information related to a diagnosis, health condition or health problem, which will be afforded heightened confidentiality. Diagnostic, health condition or health problem related information may be deemed sensitive by organizational policy, and require heightened confidentiality. <br/> Usage Note: For use within an enterprise that provides heightened confidentiality to diagnostic, health condition or health problem related information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       DRGIS <a name="v3-ActCode-DRGIS"> </a> </td> <td> drug information sensitivity</td> <td> Policy for handling information related to a drug, which will be afforded heightened confidentiality. Drug information may be deemed sensitive by organizational policy, and require heightened confidentiality. <br/> Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 4</td> <td>       EMP <a name="v3-ActCode-EMP"> </a> </td> <td> employee information sensitivity</td> <td> Policy for handling information related to an employee, which will be afforded heightened confidentiality. When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. <br/> Usage Note: Policy for handling information related to an employee, which will be afforded heightened confidentiality. Description: When a patient is an employee, an enterprise may have a policy that requires heightened confidentiality. Information deemed sensitive typically includes health information and patient role information including patient status, demographics, next of kin, and location. <br/> </td> </tr> <tr> <td> 4</td> <td>       PDS <a name="v3-ActCode-PDS"> </a> </td> <td> patient default information sensitivity</td> <td> Policy for specially protecting information reported by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whether the patient requested that the information be deemed sensitive for another reason.) For example information reported by the patient about another person, e.g., a family member, may be deemed sensitive by default. Organizational policy may allow the sensitivity tag to be cleared on patient's request. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. <br/> For example, VA deems employee information sensitive by default. Information about a patient who is being stalked or a victim of abuse or violence may be deemed sensitive by default per a provider organization's policies. <br/> </td> </tr> <tr> <td> 4</td> <td>       PHY <a name="v3-ActCode-PHY"> </a> </td> <td> physician requested information sensitivity</td> <td> Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the provider, this may trigger alerts for follow up actions according to organizational policy or jurisdictional law. <br/> Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a physician as sensitive. If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> Use cases in which this code could be used are, e.g., in systems that lack the ability to automatically detect sensitive information and must rely on manual tagging; a system that lacks an applicable sensitivity tag, or for ad hoc situations where criticality of the situation requires that the tagging be done immediately by the provider before coding or transcription of consult notes can be completed, e.g., upon detection of a patient with suicidal tendencies or potential for violence. <br/> </td> </tr> <tr> <td> 4</td> <td>       PRS <a name="v3-ActCode-PRS"> </a> </td> <td> patient requested information sensitivity</td> <td> Policy for specially protecting information reported by or about a patient, which the patient deems sensitive, and the patient requests that collection, access, use, or disclosure of that information be restricted. For example, a minor patient may request that information about reproductive health not be disclosed to the patient's family or to particular providers and payers. <br/> Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code. <br/> </td> </tr> <tr> <td> 3</td> <td>     COMPT <a name="v3-ActCode-COMPT"> </a> </td> <td> compartment</td> <td> This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. <br/> Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk." <br/> </td> </tr> <tr> <td> 4</td> <td>       ACOCOMPT <a name="v3-ActCode-ACOCOMPT"> </a> </td> <td> accountable care organization compartment</td> <td> A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who coordinate care for reimbursement based on quality metrics for improving outcomes and lowering costs, and may be authorized to access the consumer's health information because of membership in that group. <br/> Security Compartment Labels assigned to a consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a an accountable care workflow who is requesting access to that information <br/> </td> </tr> <tr> <td> 4</td> <td>       CTCOMPT <a name="v3-ActCode-CTCOMPT"> </a> </td> <td> care team compartment</td> <td> Care coordination across participants in a care plan requires sharing of a healthcare consumer's information specific to that workflow. A care team member should only have access to that information while participating in that workflow or for other authorized uses. <br/> Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information <br/> </td> </tr> <tr> <td> 4</td> <td>       FMCOMPT <a name="v3-ActCode-FMCOMPT"> </a> </td> <td> financial management compartment</td> <td> Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows. <br/> Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a financial management workflow who is requesting access to that information. <br/> </td> </tr> <tr> <td> 4</td> <td>       HRCOMPT <a name="v3-ActCode-HRCOMPT"> </a> </td> <td> human resource compartment</td> <td> A security category label field value, which indicates that access and use of an IT resource is restricted to members of human resources department or workflow. <br/> </td> </tr> <tr> <td> 4</td> <td>       LRCOMPT <a name="v3-ActCode-LRCOMPT"> </a> </td> <td> legitimate relationship compartment</td> <td> Providers and care givers who have an established relationship per criteria determined by policy are considered to have an established care provision relations with a healthcare consumer, and may be authorized to access the consumer's health information because of that relationship. Providers and care givers should only have access to that information while participating in legitimate relationship workflows or for other authorized uses. <br/> Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information. <br/> </td> </tr> <tr> <td> 4</td> <td>       PACOMPT <a name="v3-ActCode-PACOMPT"> </a> </td> <td> patient administration compartment</td> <td> Patient administration members who have access to healthcare consumer information as part of a patient administration workflows. <br/> Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the Security Compartment attribute claimed by a participant in a patient administration workflow who is requesting access to that information. <br/> </td> </tr> <tr> <td> 4</td> <td>       RESCOMPT <a name="v3-ActCode-RESCOMPT"> </a> </td> <td> research project compartment</td> <td> A security category label field value, which indicates that access and use of an IT resource is restricted to members of a research project. <br/> </td> </tr> <tr> <td> 4</td> <td>       RMGTCOMPT <a name="v3-ActCode-RMGTCOMPT"> </a> </td> <td> records management compartment</td> <td> A security category label field value, which indicates that access and use of an IT resource is restricted to members of records management department or workflow. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (ActTrustPolicyType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-ActTrustPolicyType"> </a> </td> <td> A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions. <br/> Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). <br/> Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain's trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. [Based on ISO IEC 10181-1 and NIST SP 800-63-2] <br/> For example, identity proofing , level of assurance, and Trust Framework. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTACCRD <a name="v3-ActCode-TRSTACCRD"> </a> </td> <td> trust accreditation</td> <td> Type of security metadata about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTAGRE <a name="v3-ActCode-TRSTAGRE"> </a> </td> <td> trust agreement</td> <td> Type of security metadata about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTASSUR <a name="v3-ActCode-TRSTASSUR"> </a> </td> <td> trust assurance</td> <td> Type of security metadata about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTCERT <a name="v3-ActCode-TRSTCERT"> </a> </td> <td> trust certificate</td> <td> Type of security metadata about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTFWK <a name="v3-ActCode-TRSTFWK"> </a> </td> <td> trust framework</td> <td> Type of security metadata about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTMEC <a name="v3-ActCode-TRSTMEC"> </a> </td> <td> trust mechanism</td> <td> Type of security metadata about a security architecture system component that supports enforcement of security policies. <br/> </td> </tr> <tr> <td> 2</td> <td>   COVPOL <a name="v3-ActCode-COVPOL"> </a> </td> <td> benefit policy</td> <td> Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed on benefit coverage under a policy or program by a sponsor, underwriter or payor on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> Examples:A clinical protocol imposed by a payer to which a provider must adhere in order to be paid for providing the service. A formulary from which a provider must select prescribed drugs in order for the patient to incur a lower copay. <br/> </td> </tr> <tr> <td> 2</td> <td>   SecurityPolicy <a name="v3-ActCode-SecurityPolicy"> </a> </td> <td> security policy</td> <td> Types of security policies that further specify the ActClassPolicy value set. <br/> Examples: <br/> obligation to encrypt refrain from redisclosure without consent </td> </tr> <tr> <td> 3</td> <td>     AUTHPOL <a name="v3-ActCode-AUTHPOL"> </a> </td> <td> authorization policy</td> <td> Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system. <br/> A positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions. (Based on PONDERS) <br/> </td> </tr> <tr> <td> 4</td> <td>       ACCESSCONSCHEME <a name="v3-ActCode-ACCESSCONSCHEME"> </a> </td> <td> access control scheme</td> <td> An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies. <br/> Usage Note: Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service. <br/> There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also. <br/> An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these. An access control scheme is a component of an access control mechanism or "service") along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a PDP). (Based on ISO/IEC 10181-3:1996) <br/> Examples: <br/> Attribute Based Access Control (ABAC) Discretionary Access Control (DAC) History Based Access Control (HBAC) Identity Based Access Control (IBAC) Mandatory Access Control (MAC) Organization Based Access Control (OrBAC) Relationship Based Access Control (RelBac) Responsibility Based Access Control (RespBAC) Risk Adaptable Access Control (RAdAC) > </td> </tr> <tr> <td> 3</td> <td>     DELEPOL <a name="v3-ActCode-DELEPOL"> </a> </td> <td> delegation policy</td> <td> Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated. <br/> Delegation policies are aimed at subjects delegating rights to servers or third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden. <br/> A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of delegation policy, positive and negative. (Based on PONDERS) <br/> </td> </tr> <tr> <td> 3</td> <td>     ObligationPolicy <a name="v3-ActCode-ObligationPolicy"> </a> </td> <td> obligation policy</td> <td> Conveys the mandated workflow action that an information custodian, receiver, or user must perform. <br/> Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANONY <a name="v3-ActCode-ANONY"> </a> </td> <td> anonymize</td> <td> Custodian system must remove any information that could result in identifying the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       AOD <a name="v3-ActCode-AOD"> </a> </td> <td> accounting of disclosure</td> <td> Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested. <br/> </td> </tr> <tr> <td> 4</td> <td>       AUDIT <a name="v3-ActCode-AUDIT"> </a> </td> <td> audit</td> <td> Custodian system must monitor systems to ensure that all users are authorized to operate on information objects. <br/> </td> </tr> <tr> <td> 4</td> <td>       AUDTR <a name="v3-ActCode-AUDTR"> </a> </td> <td> audit trail</td> <td> Custodian system must monitor and maintain retrievable log for each user and operation on information. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYCC <a name="v3-ActCode-CPLYCC"> </a> </td> <td> comply with confidentiality code</td> <td> Custodian security system must retrieve, evaluate, and comply with the information handling directions of the Confidentiality Code associated with an information target. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYCD <a name="v3-ActCode-CPLYCD"> </a> </td> <td> comply with consent directive</td> <td> Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYJPP <a name="v3-ActCode-CPLYJPP"> </a> </td> <td> comply with jurisdictional privacy policy</td> <td> Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYOPP <a name="v3-ActCode-CPLYOPP"> </a> </td> <td> comply with organizational privacy policy</td> <td> Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYOSP <a name="v3-ActCode-CPLYOSP"> </a> </td> <td> comply with organizational security policy</td> <td> Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information. <br/> </td> </tr> <tr> <td> 4</td> <td>       CPLYPOL <a name="v3-ActCode-CPLYPOL"> </a> </td> <td> comply with policy</td> <td> Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information. <br/> </td> </tr> <tr> <td> 4</td> <td>       DECLASSIFYLABEL <a name="v3-ActCode-DECLASSIFYLABEL"> </a> </td> <td> declassify security label</td> <td> Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. <br/> </td> </tr> <tr> <td> 4</td> <td>       DEID <a name="v3-ActCode-DEID"> </a> </td> <td> deidentify</td> <td> Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       DELAU <a name="v3-ActCode-DELAU"> </a> </td> <td> delete after use</td> <td> Custodian system must remove target information from access after use. <br/> </td> </tr> <tr> <td> 4</td> <td>       DOWNGRDLABEL <a name="v3-ActCode-DOWNGRDLABEL"> </a> </td> <td> downgrade security label</td> <td> Custodian security system must downgrade information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. <br/> </td> </tr> <tr> <td> 4</td> <td>       DRIVLABEL <a name="v3-ActCode-DRIVLABEL"> </a> </td> <td> derive security label</td> <td> Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. <br/> </td> </tr> <tr> <td> 4</td> <td>       ENCRYPT <a name="v3-ActCode-ENCRYPT"> </a> </td> <td> encrypt</td> <td> Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. <br/> <br/> Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is a security feature that assures that only the parties who are supposed to be participating in a videoconference or data transfer are able to do so. It can include a password, public and private keys, or a complex combination of all. (Per Infoway.) <br/> </td> </tr> <tr> <td> 5</td> <td>         ENCRYPTR <a name="v3-ActCode-ENCRYPTR"> </a> </td> <td> encrypt at rest</td> <td> Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage. <br/> </td> </tr> <tr> <td> 5</td> <td>         ENCRYPTT <a name="v3-ActCode-ENCRYPTT"> </a> </td> <td> encrypt in transit</td> <td> Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means. <br/> </td> </tr> <tr> <td> 5</td> <td>         ENCRYPTU <a name="v3-ActCode-ENCRYPTU"> </a> </td> <td> encrypt in use</td> <td> Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user. <br/> </td> </tr> <tr> <td> 4</td> <td>       HUAPRV <a name="v3-ActCode-HUAPRV"> </a> </td> <td> human approval</td> <td> Custodian system must require human review and approval for permission requested. <br/> </td> </tr> <tr> <td> 4</td> <td>       LABEL <a name="v3-ActCode-LABEL"> </a> </td> <td> assign security label</td> <td> Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. <br/> Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes. <br/> </td> </tr> <tr> <td> 4</td> <td>       MASK <a name="v3-ActCode-MASK"> </a> </td> <td> mask</td> <td> Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret". <br/> </td> </tr> <tr> <td> 4</td> <td>       MINEC <a name="v3-ActCode-MINEC"> </a> </td> <td> minimum necessary</td> <td> Custodian must limit access and disclosure to the minimum information required to support an authorized user's purpose of use. <br/> Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in order to perform permitted workflow or purpose of use. <br/> </td> </tr> <tr> <td> 4</td> <td>       PERSISTLABEL <a name="v3-ActCode-PERSISTLABEL"> </a> </td> <td> persist security label</td> <td> Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the assignment and binding. <br/> </td> </tr> <tr> <td> 4</td> <td>       PRIVMARK <a name="v3-ActCode-PRIVMARK"> </a> </td> <td> privacy mark</td> <td> Custodian must create and/or maintain human readable security label tags as required by policy. <br/> Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label." <br/> </td> </tr> <tr> <td> 4</td> <td>       PSEUD <a name="v3-ActCode-PSEUD"> </a> </td> <td> pseudonymize</td> <td> Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a key to relink data necessary to reidentify the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       REDACT <a name="v3-ActCode-REDACT"> </a> </td> <td> redact</td> <td> Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users. <br/> </td> </tr> <tr> <td> 4</td> <td>       UPGRDLABEL <a name="v3-ActCode-UPGRDLABEL"> </a> </td> <td> upgrade security label</td> <td> Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (PrivacyMark)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-PrivacyMark"> </a> </td> <td> An abstract code for human readable marks indicating, e.g., the level of confidentiality protection, an authorized compartment, the integrity, or the handling instruction required by applicable policy. Such markings must be displayed as directed by applicable policy on electronically rendered information content and any electronic transmittal envelope or container; or on hardcopy information and any physical transmittal envelope or container. <br/> Examples of protocols for marking displays on electronic or hardcopy rendered content: Across the top or "banner" of each page ; as a watermark placed diagonally cross each page; at the bottom or "footer" of each page; and may be displayed at the beginning of any portion within the content that required markings different than other portions of the content. The banner or top of page marking typically acts as a "high watermark" by including all of the markings made on any marked portions within the entirety of the information content. <br/> Usage Note: A "Privacy Mark" is a Security Control Observation (SECCONOBS) named tag set as specified by the HL7 Privacy and Security Classification System (HCS). A Privacy Mark Named Tag Set is valued with a Privacy Mark leaf code "tag", which is a member of the Security Control Observation Value (_SecurityObservationValue) tag set. Related Security Control Observation named tag sets are Purpose of Use, Obligation Policy, and Refrain Policy, each with their own Security Control Observation Value tag sets. <br/> Foundational standard definitions: ISO 22600-3 Section A.3.4.3 - If present, the privacy-mark is not used for access control. The content of the privacy-mark may be defined by the security policy in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the value may be determined by the originator of the security-label. IEEE Security Glossary Compendium 93- CESG Memorandum No.1 Issue 1.2 Oct 1992 - Human readable word or phrase acting as an indicator of all or part of the security constraints that apply to a document so marked. NOTE: A machine readable representation of a marking. <br/> Comment: While policies requiring creators, processors, custodians, senders or recipients apply, enforce, and persist applicable Privacy Marks may be dictated by a jurisdiction, organization or personal privacy, security, or integrity policy, those required to comply may be governed under different policies, so compliance may need to be enforced through trust contracts. For example, information content marked with GDPR related policies may require adherence by processors or recipients outside of the European Union. For this reason, this code system is likely to evolve with the inclusion of multiple policy domains needing to communicate encoded policies in a standard, interoperable manner. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (ControlledUnclassifiedInformation)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-ControlledUnclassifiedInformation"> </a> </td> <td> Information the US Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. However, CUI does not include classified information (see definition above) or information a non-executive branch entity possesses and maintains in its own systems that did not come from, or was not created or possessed by or for, an executive branch agency or an entity acting for an agency. Law, regulation, or Government-wide policy may require or permit safeguarding or dissemination controls in three ways: Requiring or permitting agencies to control or protect the information but providing no specific controls, which makes the information CUI Basic; requiring or permitting agencies to control or protect the information and providing specific controls for doing so, which makes the information CUI Specified; or requiring or permitting agencies to control the information and specifying only some of those controls, which makes the information CUI Specified, but with CUI Basic controls where the authority does not specify. Based on CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html . <br/> Usage Note: Mandatory control marking, which must be displayed on the top portion of each rendered or printed page containing controlled information. Should be displayed at the bottom of each rendered or printed page containing controlled information. Must be displayed on each portion of controlled information at the portion level if portions are uncontrolled unclassified information. Based on CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf. For definitions of key terms see CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> </td> </tr> <tr> <td> 5</td> <td>         CONTROLLED <a name="v3-ActCode-CONTROLLED"> </a> </td> <td> CONTROLLED</td> <td> A displayed mark, required to be rendered as "CONTROLLED", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archi ves.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Mandatory control marking, which must be displayed on the top portion of each rendered or printed page containing controlled information. Should be displayed at the bottom of each rendered or printed page containing controlled information. Must be displayed on each portion of controlled information at the portion level if portions are uncontrolled unclassified information. Based on CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUI <a name="v3-ActCode-CUI"> </a> </td> <td> CUI</td> <td> A displayed mark, required to be rendered as "CUI", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archi ves.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Mandatory control marking, which must be displayed on the top portion of each rendered or printed page containing controlled information. Should be displayed at the bottom of each rendered or printed page containing controlled information. Must be displayed on each portion of controlled information at the portion level if portions are uncontrolled unclassified information. Based on CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUIHLTH <a name="v3-ActCode-CUIHLTH"> </a> </td> <td> CUI//HLTH</td> <td> A displayed mark, required to be rendered as "CUI//HLTH", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archi ves.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of healthcare regulation governing CUI Basic marking include HIPAA Unique Identifier provisions 42 USC 1320d-2 note(b) https://www.govinfo. gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf; Title 38 Section 7332 https://www.govinfo.gov/content/pkg/USCODE-2016-title38/pdf/USCODE-2016-title3 8-partV-chap73-subchapIII-sec7332.pdf; and several sections of 42 CFR Part 2.related to consent and confidentiality, e.g., https://www.govinfo.gov/content/pkg/CFR-2017-title42-vol1/pdf/CFR -2017-title42-vol1-sec2-12.pdf <br/> </td> </tr> <tr> <td> 5</td> <td>         CUIHLTHP <a name="v3-ActCode-CUIHLTHP"> </a> </td> <td> (CUI//HLTH)</td> <td> A displayed mark, required to be rendered as "(CUI//HLTH)", indicating that a portion of an electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of healthcare regulation governing CUI Basic marking include HIPAA Unique Identifier provisions 42 USC 1320d-2 note(b) https://www.govinfo. gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf; Title 38 Section 7332 https://www.govinfo.gov/content/pkg/USCODE-2016-title38/pdf/USCODE-2016-title3 8-partV-chap73-subchapIII-sec7332.pdf; and several sections of 42 CFR Part 2.related to consent and confidentiality, e.g., https://www.govinfo.gov/content/pkg/CFR-2017-title42-vol1/pdf/CFR -2017-title42-vol1-sec2-12.pdf <br/> </td> </tr> <tr> <td> 5</td> <td>         CUIP <a name="v3-ActCode-CUIP"> </a> </td> <td> (CUI)</td> <td> A displayed mark, required to be rendered as "(CUI)", indicating that a portion of an electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of healthcare regulation governing CUI Basic marking include HIPAA Unique Identifier provisions 42 USC 1320d-2 note(b) https://www.govinfo. gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf; Title 38 Section 7332 https://www.govinfo.gov/content/pkg/USCODE-2016-title38/pdf/USCODE-2016-title3 8-partV-chap73-subchapIII-sec7332.pdf; and several sections of 42 CFR Part 2.related to consent and confidentiality, e.g., https://www.govinfo.gov/content/pkg/CFR-2017-title42-vol1/pdf/CFR -2017-title42-vol1-sec2-12.pdf <br/> </td> </tr> <tr> <td> 5</td> <td>         CUIPRVCY <a name="v3-ActCode-CUIPRVCY"> </a> </td> <td> CUI//PRVCY</td> <td> A displayed mark, required to be rendered as "CUI//PRVCY", indicating that the electronic or hardcopy controlled unclassified basic privacy information is private and must be protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of privacy regulation governing CUI Basic marking include 20 CFR 401.100 related to SSA disclosure of personal, program, and non-program information. https://www.govinfo.gov/content/pkg/CFR-2017-title20-vol2/pdf/CFR-2017-title20-vol2-sec 401-100.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUIPRVCYP <a name="v3-ActCode-CUIPRVCYP"> </a> </td> <td> (CUI//PRVCY)</td> <td> A displayed mark, required to be rendered as "(CUI//PRVCY)", indicating that a portion of an electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of privacy regulation governing CUI Basic marking include 20 CFR 401.100 related to SSA disclosure of personal, program, and non-program information. https://www.govinfo.gov/content/pkg/CFR-2017-title20-vol2/pdf/CFR-2017-title20-vol2-sec 401-100.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUISP-HLTH <a name="v3-ActCode-CUISP-HLTH"> </a> </td> <td> CUI//SP-HLTH</td> <td> A displayed mark, required to be rendered as "CUI//SP-HLTH", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI in which the authorizing law, regulation, or Government-wide policy contains specific handling controls that it requires or permits agencies to use that differ from those for CUI Basic. The CUI Registry indicates which laws, regulations, and Government-wide policies include such specific requirements. CUI Specified controls may be more stringent than, or may simply differ from, those required by CUI Basic; the distinction is that the underlying authority spells out the controls for CUI Specified information and does not for CUI Basic information. CUI Basic controls apply to those aspects of CUI Specified where the authorizing laws, regulations, and Government-wide policies do not provide specific guidance. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of healthcare regulation governing CUI Specified marking include HIPAA Transaction and Code Sets and references the Congressional requirement that HHS promulgate Privacy, and Security rules https://www.govinfo.gov/content/pkg/USC ODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUISP-HLTHP <a name="v3-ActCode-CUISP-HLTHP"> </a> </td> <td> (CUI//SP-HLTH)</td> <td> A displayed mark, required to be rendered as "(CUI//SP-HLTH)", indicating that a portion of an electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of healthcare regulation governing CUI Specified marking include HIPAA Transaction and Code Sets and references the Congressional requirement that HHS promulgate Privacy, and Security rules https://www.govinfo.gov/content/pkg/USC ODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf <br/> </td> </tr> <tr> <td> 5</td> <td>         CUISP-PRVCY <a name="v3-ActCode-CUISP-PRVCY"> </a> </td> <td> CUI//SP-PRVCY</td> <td> A displayed mark, required to be rendered as "CUI//SP-PRVCY", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archi ves.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of privacy regulation governing CUI Specified marking is OMB M-17-12ï‡? This Memorandum sets forth the policy for Federal agencies to prepare for and respond to a breach of personally identifiable information (PII). It includes a framework for assessing and mitigating the risk of harm to individuals potentially affected by a breach, as well as guidance on whether and how to provide notification and services to those individuals. https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m-17- 12_0.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         CUISP-PRVCYP <a name="v3-ActCode-CUISP-PRVCYP"> </a> </td> <td> (CUI//SP-PRVCY)</td> <td> A displayed mark, required to be rendered as "(CUI//SP-PRVCY)", indicating that a portion of an electronic or hardcopy information is protected at the level of the subset of CUI for which the authorizing law, regulation, or Government-wide policy does not set out specific handling or dissemination controls. Agencies handle CUI Basic according to the uniform set of controls set forth in this part and the CUI Registry. CUI Basic differs from CUI Specified (see definition for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. <br/> Usage Note: Examples of privacy regulation governing CUI Specified marking is OMB M-17-12ï‡? This Memorandum sets forth the policy for Federal agencies to prepare for and respond to a breach of personally identifiable information (PII). It includes a framework for assessing and mitigating the risk of harm to individuals potentially affected by a breach, as well as guidance on whether and how to provide notification and services to those individuals. https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m-17- 12_0.pdf. <br/> </td> </tr> <tr> <td> 5</td> <td>         UUI <a name="v3-ActCode-UUI"> </a> </td> <td> (U)</td> <td> A displayed mark, required to be rendered as "(U)", indicating that a portion of an electronic or hardcopy information is neither Executive Order 13556 nor classified information authorities cover as protected. Although this information is not controlled or classified, agencies must still handle it in accordance with Federal Information Security Modernization Act (FISMA) requirements. From CUI Glossary https://www.archives. gov/cui/registry/cui-glossary.html <br/> Usage Note: Regulatory Source: 32 CFR § 2002.20 Marking. Federal Register Page 63344 63344 (ii) Authorized holders permitted to designate CUI must portion mark both CUI and uncontrolled unclassified portions. <br/> CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking -handbook-v1-1.pdf <br/> CUI Portion Marking: Portion marking of CUI is optional in a fully unclassified document, but is permitted and encouraged to facilitate information sharing and proper handling of the information. Agency heads may approve the required use of CUI Portion marking on all CUI generated within their agency. As such, users should consult their agency CUI policy when creating CUI documents. When CUI Portion Markings are used and a portion does not contain CUI a “Uâ€? is placed in parentheses to indicate that the portion contains Uncontrolled Unclassified Information. (Page 14) <br/> CUI Portion Markings are placed at the beginning of the portion to which they apply and must be used throughout the entire document. They are presented in all capital letters and separated as indicated in this handbook and the CUI Registry. The presence of EVEN ONE item of CUI in a document requires CUI marking of that document. Because of this, CUI Portion Markings can be of great assistance in determining if a document contains CUI and therefore must be marked as such. Remember: When portion markings are used and any portion does not contain CUI, a “(U)â€? is placed in front of that portion to indicate that it contains Uncontrolled - or non-CUI - Unclassified Information. (Page 15) <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (SecurityLabelMark)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-SecurityLabelMark"> </a> </td> <td> An abstract code for displayed Security Label tags. <br/> Usage Note: These marks may be based on any of the HL7 Security Labeling related codes from various code systems and values sets, which are organized according to the HL7 Privacy and Security Classification System into HL7 Security Observation Type Named Tag Sets and valued with codes associated with the HL7 Security Observation Value Tag Set Names. <br/> </td> </tr> <tr> <td> 5</td> <td>         ConfidentialMark <a name="v3-ActCode-ConfidentialMark"> </a> </td> <td> confidential mark</td> <td> A displayed mark rendered as "Confidential", which indicates to end users that the electronic or hardcopy information they are viewing must be protected at a level of protection as dictated by applicable policy. <br/> May be used to indicate proprietary or classified information that is, for example, business, intelligence, or project related, e.g., secret ingredients in a therapeutic substance; location of disaster health facilities and providers, or the name of a manufacturer or project contractor. Example use cases include a display to alert authorized business system users that they are viewing additionally protected proprietary and business confidential information deemed proprietary under an applicable jurisdictional or organizational policy. <br/> Usage Note: <br/> The ConfidentialMark (confidential mark) description is based on the HL7 Confidentiality Concept Domain: Types of privacy metadata classifying an IT resource (data, information object, service, or system capability) according to its level of sensitivity, which is based on an analysis of applicable privacy policies and the risk of financial, reputational, or other harm to an individual or entity that could result if made available or disclosed to unauthorized individuals, entities, or processes. Usage Note: Confidentiality codes may be used in security labels and privacy markings to classify IT resources based on sensitivity to indicate the obligation of a custodian or receiver to ensure that the protected resource is not made available or disclosed to individuals, entities, or processes (security principals) unless authorized per applicable policies. Confidentiality codes may also be used in the clearances of initiators requesting access to protected resources. <br/> Map: Definition aligns with ISO 7498-2:1989 - Confidentiality is the property that information is not made available or disclosed to unauthorized individuals, entities, or processes. <br/> </td> </tr> <tr> <td> 5</td> <td>         COPYMark <a name="v3-ActCode-COPYMark"> </a> </td> <td> copy of original mark</td> <td> A displayed mark indicating that the electronic or hardcopy information is a copy of an authoritative source for the information. The copy is not considered authoritative but is a duplicate of the authoritative content. <br/> Usage Note: Applicable policy will dictate how the COPY mark will be displayed. Typical renderings include the marking appearing at the top or "banner" ; of electronic or hardcopy pages, or as watermarks set diagonally across each page. <br/> </td> </tr> <tr> <td> 5</td> <td>         DeliverToAddresseeOnlyMark <a name="v3-ActCode-DeliverToAddresseeOnlyMark"> </a> </td> <td> deliver only to addressee mark</td> <td> A displayed mark on an electronic transmission or physical container such as an electronic transmittal wrapper, batch file, message header, or a physical envelop or package indicating that the contents, whether electronic or hardcopy information, must only be delivered to the authorized recipient(s) named in the address. <br/> Usage Note: Required by US 32 CRF Part 2002 for container storing or transmitting CUI. <br/> </td> </tr> <tr> <td> 5</td> <td>         RedisclosureProhibitionMark <a name="v3-ActCode-RedisclosureProhibitionMark"> </a> </td> <td> prohibition against redisclosure mark</td> <td> A displayed mark rendered to end users as a prescribed text warning that the electronic or hardcopy information shall not be further disclosed without consent of the subject of the information. For example, in order to warn a recipient of 42 CFR Part 2 information of the redisclosure restrictions, the rule mandates that end users receive a written prohibition against redisclosure unless authorized by patient consent or otherwise permitted by Part 2. See 42 CFR § 2.32 Prohibition on re-disclosure. (a)Notice to accompany disclosure. Each disclosure made with the patient's written consent must be accompanied by one of the following written statements: (1) This information has been disclosed to you from records protected by federal confidentiality rules ( 42 CFR part 2). The federal rules prohibit you from making any further disclosure of information in this record that identifies a patient as having or having had a substance use disorder either directly, by reference to publicly available information, or through verification of such identification by another person unless further disclosure is expressly permitted by the written consent of the individual whose information is being disclosed or as otherwise permitted by 42 CFR part 2. A general authorization for the release of medical or other information is NOT sufficient for this purpose (see § 2.31). The federal rules restrict any use of the information to investigate or prosecute with regard to a crime any patient with a substance use disorder, except as provided at §§ 2.12(c)(5) and 2.65; or (2) 42 CFR part 2 prohibits unauthorized disclosure of these records. https://www.law.c ornell.edu/cfr/text/42/2.32 <br/> Usage Note: Example of marking requirement from SAMHSA FAQ Response to question 13: <br/> Would a logon or splash page notification on an HIO’s portal that contains the Part 2 notice prohibiting redisclosure be sufficient to meet Part 2’s requirement that disclosures made with patient consent be accompanied by such a statement? <br/> No. Part 2 requires each disclosure made with written patient consent to be accompanied by a written statement that the information disclosed is protected by federal law and that the recipient cannot make any further disclosure of it unless permitted by the regulations (42 CFR § 2.32). A logon page is the page where a user logs onto a computer system; a splash page is an introductory page to a web site. A logon or splash page notification on a HIO's portal including the statement as required by § 2.32 would not be sufficient notification regarding prohibitions on redisclosure since it would not accompany a specific disclosure. The notification must be tied to the Part 2 information being disclosed in order to ensure that the recipient of that information knows that specific information is protected by Part 2 and cannot be redisclosed except as authorized by the express written consent of the person to whom it pertains or as otherwise permitted by Part 2. https://www.samhsa.gov/about-us/who-we-are/laws-regulations/confidentiality-regulations-faq s <br/> </td> </tr> <tr> <td> 5</td> <td>         RestrictedConfidentialityMark <a name="v3-ActCode-RestrictedConfidentialityMark"> </a> </td> <td> restricted confidentiality mark</td> <td> A displayed mark rendered to end users as "Restricted Confidentiality&q uot;, which indicates that the electronic or hardcopy information they are viewing, must be protected at a restricted level of confidentiality protection as defined by HL7 Confidentiality code "R" (restricted). Examples: Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. Use cases include a display to alert authorized EHR users that they are viewing additionally protected health information deemed sensitive by an applicable jurisdictional, organizational, or personal privacy policy. <br/> Usage Note: The definition is based on HL7 Confidentiality code "R" (restricted), which is described as: <br/> Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a high risk to the information subject if disclosed without authorization. May be pre-empted by jurisdictional law, e.g., for public health reporting or emergency treatment. Foundational definitions of Confidentiality: From HL7 Confidentiality Concept Domain: Types of privacy metadata classifying an IT resource (data, information object, service, or system capability) according to its level of sensitivity, which is based on an analysis of applicable privacy policies and the risk of financial, reputational, or other harm to an individual or entity that could result if made available or disclosed to unauthorized individuals, entities, or processes. <br/> Usage Note from HL7 Confidentiality code "R": Confidentiality codes may be used in security labels and privacy markings to classify IT resources based on sensitivity to indicate the obligation of a custodian or receiver to ensure that the protected resource is not made available or disclosed to individuals, entities, or processes (security principals) unless authorized per applicable policies. Confidentiality codes may also be used in the clearances of initiators requesting access to protected resources. <br/> This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization. <br/> Map: Definition aligns with ISO 7498-2:1989 - Confidentiality is the property that information is not made available or disclosed to unauthorized individuals, entities, or processes. Map: Partial Map to ISO 13606-4 Sensitivity Level (3) Clinical Care: Default for normal clinical care access (i.e. most clinical staff directly caring for the patient should be able to access nearly all of the EHR). Maps to normal confidentiality for treatment information but not to ancillary care, payment and operations. <br/> </td> </tr> <tr> <td> 3</td> <td>     RefrainPolicy <a name="v3-ActCode-RefrainPolicy"> </a> </td> <td> refrain policy</td> <td> Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. <br/> <br/> Usage Notes: ISO 22600-2 species that a Refrain Policy "defines actions the subjects must refrain from performing". Per HL7 Composite Security and Privacy Domain Analysis Model: May be used to indicate that a specific action is prohibited based on specific access control attributes e.g., purpose of use, information type, user role, etc. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOAUTH <a name="v3-ActCode-NOAUTH"> </a> </td> <td> no disclosure without subject authorization</td> <td> Prohibition on disclosure without information subject's authorization. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOCOLLECT <a name="v3-ActCode-NOCOLLECT"> </a> </td> <td> no collection</td> <td> Prohibition on collection or storage of the information. <br/> </td> </tr> <tr> <td> 4</td> <td>       NODSCLCD <a name="v3-ActCode-NODSCLCD"> </a> </td> <td> no disclosure without consent directive</td> <td> Prohibition on disclosure without organizational approved patient restriction. <br/> </td> </tr> <tr> <td> 4</td> <td>       NODSCLCDS <a name="v3-ActCode-NODSCLCDS"> </a> </td> <td> no disclosure without information subject's consent directive</td> <td> Prohibition on disclosure without a consent directive from the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOINTEGRATE <a name="v3-ActCode-NOINTEGRATE"> </a> </td> <td> no integration</td> <td> Prohibition on Integration into other records. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOLIST <a name="v3-ActCode-NOLIST"> </a> </td> <td> no unlisted entity disclosure</td> <td> Prohibition on disclosure except to entities on specific access list. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOMOU <a name="v3-ActCode-NOMOU"> </a> </td> <td> no disclosure without MOU</td> <td> Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU). <br/> </td> </tr> <tr> <td> 4</td> <td>       NOORGPOL <a name="v3-ActCode-NOORGPOL"> </a> </td> <td> no disclosure without organizational authorization</td> <td> Prohibition on disclosure without organizational authorization. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOPAT <a name="v3-ActCode-NOPAT"> </a> </td> <td> no disclosure to patient, family or caregivers without attending provider's authorization</td> <td> Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. <br/> Usage Note: The information may be labeled with the ActInformationSensiti vity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. <br/> Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. <br/> FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. <br/> displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that the author chose to hide from the patient until the content can be disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone). <br/> </td> </tr> <tr> <td> 4</td> <td>       NOPERSISTP <a name="v3-ActCode-NOPERSISTP"> </a> </td> <td> no collection beyond purpose of use</td> <td> Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited. <br/> </td> </tr> <tr> <td> 4</td> <td>       NORDSCLCD <a name="v3-ActCode-NORDSCLCD"> </a> </td> <td> no redisclosure without consent directive</td> <td> Prohibition on redisclosure without patient consent directive. <br/> </td> </tr> <tr> <td> 4</td> <td>       NORDSCLCDS <a name="v3-ActCode-NORDSCLCDS"> </a> </td> <td> no redisclosure without information subject's consent directive</td> <td> Prohibition on redisclosure without a consent directive from the information subject. <br/> </td> </tr> <tr> <td> 4</td> <td>       NORDSCLW <a name="v3-ActCode-NORDSCLW"> </a> </td> <td> no disclosure without jurisdictional authorization</td> <td> Prohibition on disclosure without authorization under jurisdictional law. <br/> </td> </tr> <tr> <td> 4</td> <td>       NORELINK <a name="v3-ActCode-NORELINK"> </a> </td> <td> no relinking</td> <td> Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOREUSE <a name="v3-ActCode-NOREUSE"> </a> </td> <td> no reuse beyond purpose of use</td> <td> Prohibition on use of the information beyond the purpose of use initially authorized. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOVIP <a name="v3-ActCode-NOVIP"> </a> </td> <td> no unauthorized VIP disclosure</td> <td> Prohibition on disclosure except to principals with access permission to specific VIP information. <br/> </td> </tr> <tr> <td> 4</td> <td>       ORCON <a name="v3-ActCode-ORCON"> </a> </td> <td> no disclosure without originator authorization</td> <td> Prohibition on disclosure except as permitted by the information originator. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActProductAcquisitionCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActProductAcquisitionCode"> </a> </td> <td> The method that a product is obtained for use by the subject of the supply act (e.g. patient). Product examples are consumable or durable goods. <br/> </td> </tr> <tr> <td> 2</td> <td>   LOAN <a name="v3-ActCode-LOAN"> </a> </td> <td> Loan</td> <td> Temporary supply of a product without transfer of ownership for the product. <br/> </td> </tr> <tr> <td> 3</td> <td>     RENT <a name="v3-ActCode-RENT"> </a> </td> <td> Rent</td> <td> Temporary supply of a product with financial compensation, without transfer of ownership for the product. <br/> </td> </tr> <tr> <td> 2</td> <td>   TRANSFER <a name="v3-ActCode-TRANSFER"> </a> </td> <td> Transfer</td> <td> Transfer of ownership for a product. <br/> </td> </tr> <tr> <td> 3</td> <td>     SALE <a name="v3-ActCode-SALE"> </a> </td> <td> Sale</td> <td> Transfer of ownership for a product for financial compensation. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActSpecimenTransportCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActSpecimenTransportCode"> </a> </td> <td> Transportation of a specimen. <br/> </td> </tr> <tr> <td> 2</td> <td>   SREC <a name="v3-ActCode-SREC"> </a> </td> <td> specimen received</td> <td> Description:Specimen has been received by the participating organization/department. <br/> </td> </tr> <tr> <td> 2</td> <td>   SSTOR <a name="v3-ActCode-SSTOR"> </a> </td> <td> specimen in storage</td> <td> Description:Specimen has been placed into storage at a participating location. <br/> </td> </tr> <tr> <td> 2</td> <td>   STRAN <a name="v3-ActCode-STRAN"> </a> </td> <td> specimen in transit</td> <td> Description:Specimen has been put in transit to a participating receiver. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActSpecimenTreatmentCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActSpecimenTreatmentCode"> </a> </td> <td> Set of codes related to specimen treatments <br/> </td> </tr> <tr> <td> 2</td> <td>   ACID <a name="v3-ActCode-ACID"> </a> </td> <td> Acidification</td> <td> The lowering of specimen pH through the addition of an acid <br/> </td> </tr> <tr> <td> 2</td> <td>   ALK <a name="v3-ActCode-ALK"> </a> </td> <td> Alkalization</td> <td> The act rendering alkaline by impregnating with an alkali; a conferring of alkaline qualities. <br/> </td> </tr> <tr> <td> 2</td> <td>   DEFB <a name="v3-ActCode-DEFB"> </a> </td> <td> Defibrination</td> <td> The removal of fibrin from whole blood or plasma through physical or chemical means <br/> </td> </tr> <tr> <td> 2</td> <td>   FILT <a name="v3-ActCode-FILT"> </a> </td> <td> Filtration</td> <td> The passage of a liquid through a filter, accomplished by gravity, pressure or vacuum (suction). <br/> </td> </tr> <tr> <td> 2</td> <td>   LDLP <a name="v3-ActCode-LDLP"> </a> </td> <td> LDL Precipitation</td> <td/> </tr> <tr> <td> 2</td> <td>   NEUT <a name="v3-ActCode-NEUT"> </a> </td> <td> Neutralization</td> <td> The act or process by which an acid and a base are combined in such proportions that the resulting compound is neutral. <br/> </td> </tr> <tr> <td> 2</td> <td>   RECA <a name="v3-ActCode-RECA"> </a> </td> <td> Recalcification</td> <td> The addition of calcium back to a specimen after it was removed by chelating agents <br/> </td> </tr> <tr> <td> 2</td> <td>   UFIL <a name="v3-ActCode-UFIL"> </a> </td> <td> Ultrafiltration</td> <td> The filtration of a colloidal substance through a semipermeable medium that allows only the passage of small molecules. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActSubstanceAdministrationCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActSubstanceAdministrationCode"> </a> </td> <td> Description: Describes the type of substance administration being performed. This should not be used to carry codes for identification of products. Use an associated role or entity to carry such information. <br/> </td> </tr> <tr> <td> 2</td> <td>   DRUG <a name="v3-ActCode-DRUG"> </a> </td> <td> Drug therapy</td> <td> The introduction of a drug into a subject with the intention of altering its biologic state with the intent of improving its health status. <br/> </td> </tr> <tr> <td> 2</td> <td>   FD <a name="v3-ActCode-FD"> </a> </td> <td> food</td> <td> Description: The introduction of material into a subject with the intent of providing nutrition or other dietary supplements (e.g. minerals or vitamins). <br/> </td> </tr> <tr> <td> 2</td> <td>   IMMUNIZ <a name="v3-ActCode-IMMUNIZ"> </a> </td> <td> Immunization</td> <td> The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents. <br/> </td> </tr> <tr> <td> 3</td> <td>     BOOSTER <a name="v3-ActCode-BOOSTER"> </a> </td> <td> Booster Immunization</td> <td> An additional immunization administration within a series intended to bolster or enhance immunity. <br/> </td> </tr> <tr> <td> 3</td> <td>     INITIMMUNIZ <a name="v3-ActCode-INITIMMUNIZ"> </a> </td> <td> Initial Immunization</td> <td> The first immunization administration in a series intended to produce immunity <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActTaskCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActTaskCode"> </a> </td> <td> Description: A task or action that a user may perform in a clinical information system (e.g., medication order entry, laboratory test results review, problem list entry). <br/> </td> </tr> <tr> <td> 2</td> <td>   OE <a name="v3-ActCode-OE"> </a> </td> <td> order entry task</td> <td> A clinician creates a request for a service to be performed for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     LABOE <a name="v3-ActCode-LABOE"> </a> </td> <td> laboratory test order entry task</td> <td> A clinician creates a request for a laboratory test to be done for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     MEDOE <a name="v3-ActCode-MEDOE"> </a> </td> <td> medication order entry task</td> <td> A clinician creates a request for the administration of one or more medications to a given patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   PATDOC <a name="v3-ActCode-PATDOC"> </a> </td> <td> patient documentation task</td> <td> A person enters documentation about a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     ALLERLREV <a name="v3-ActCode-ALLERLREV"> </a> </td> <td> allergy list review</td> <td> Description: A person reviews a list of known allergies of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     CLINNOTEE <a name="v3-ActCode-CLINNOTEE"> </a> </td> <td> clinical note entry task</td> <td> A clinician enters a clinical note about a given patient <br/> </td> </tr> <tr> <td> 4</td> <td>       DIAGLISTE <a name="v3-ActCode-DIAGLISTE"> </a> </td> <td> diagnosis list entry task</td> <td> A clinician enters a diagnosis for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       DISCHINSTE <a name="v3-ActCode-DISCHINSTE"> </a> </td> <td> discharge instruction entry</td> <td> A person provides a discharge instruction to a patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       DISCHSUME <a name="v3-ActCode-DISCHSUME"> </a> </td> <td> discharge summary entry task</td> <td> A clinician enters a discharge summary for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       PATEDUE <a name="v3-ActCode-PATEDUE"> </a> </td> <td> patient education entry</td> <td> A person provides a patient-specific education handout to a patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       PATREPE <a name="v3-ActCode-PATREPE"> </a> </td> <td> pathology report entry task</td> <td> A pathologist enters a report for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       PROBLISTE <a name="v3-ActCode-PROBLISTE"> </a> </td> <td> problem list entry task</td> <td> A clinician enters a problem for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       RADREPE <a name="v3-ActCode-RADREPE"> </a> </td> <td> radiology report entry task</td> <td> A radiologist enters a report for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     IMMLREV <a name="v3-ActCode-IMMLREV"> </a> </td> <td> immunization list review</td> <td> Description: A person reviews a list of immunizations due or received for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     REMLREV <a name="v3-ActCode-REMLREV"> </a> </td> <td> reminder list review</td> <td> Description: A person reviews a list of health care reminders for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       WELLREMLREV <a name="v3-ActCode-WELLREMLREV"> </a> </td> <td> wellness reminder list review</td> <td> Description: A person reviews a list of wellness or preventive care reminders for a given patient. <br/> </td> </tr> <tr> <td> 2</td> <td>   PATINFO <a name="v3-ActCode-PATINFO"> </a> </td> <td> patient information review task</td> <td> A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record. <br/> </td> </tr> <tr> <td> 3</td> <td>     ALLERLE <a name="v3-ActCode-ALLERLE"> </a> </td> <td> allergy list entry</td> <td> Description: A person enters a known allergy for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     CDSREV <a name="v3-ActCode-CDSREV"> </a> </td> <td> clinical decision support intervention review</td> <td> A person reviews a recommendation/assessment provided automatically by a clinical decision support application for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     CLINNOTEREV <a name="v3-ActCode-CLINNOTEREV"> </a> </td> <td> clinical note review task</td> <td> A person reviews a clinical note of a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       DISCHSUMREV <a name="v3-ActCode-DISCHSUMREV"> </a> </td> <td> discharge summary review task</td> <td> A person reviews a discharge summary of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     DIAGLISTREV <a name="v3-ActCode-DIAGLISTREV"> </a> </td> <td> diagnosis list review task</td> <td> A person reviews a list of diagnoses of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     IMMLE <a name="v3-ActCode-IMMLE"> </a> </td> <td> immunization list entry</td> <td> Description: A person enters an immunization due or received for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     LABRREV <a name="v3-ActCode-LABRREV"> </a> </td> <td> laboratory results review task</td> <td> A person reviews a list of laboratory results of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     MICRORREV <a name="v3-ActCode-MICRORREV"> </a> </td> <td> microbiology results review task</td> <td> A person reviews a list of microbiology results of a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       MICROORGRREV <a name="v3-ActCode-MICROORGRREV"> </a> </td> <td> microbiology organisms results review task</td> <td> A person reviews organisms of microbiology results of a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       MICROSENSRREV <a name="v3-ActCode-MICROSENSRREV"> </a> </td> <td> microbiology sensitivity test results review task</td> <td> A person reviews the sensitivity test of microbiology results of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     MLREV <a name="v3-ActCode-MLREV"> </a> </td> <td> medication list review task</td> <td> A person reviews a list of medication orders submitted to a given patient <br/> </td> </tr> <tr> <td> 4</td> <td>       MARWLREV <a name="v3-ActCode-MARWLREV"> </a> </td> <td> medication administration record work list review task</td> <td> A clinician reviews a work list of medications to be administered to a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     OREV <a name="v3-ActCode-OREV"> </a> </td> <td> orders review task</td> <td> A person reviews a list of orders submitted to a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     PATREPREV <a name="v3-ActCode-PATREPREV"> </a> </td> <td> pathology report review task</td> <td> A person reviews a pathology report of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     PROBLISTREV <a name="v3-ActCode-PROBLISTREV"> </a> </td> <td> problem list review task</td> <td> A person reviews a list of problems of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     RADREPREV <a name="v3-ActCode-RADREPREV"> </a> </td> <td> radiology report review task</td> <td> A person reviews a radiology report of a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     REMLE <a name="v3-ActCode-REMLE"> </a> </td> <td> reminder list entry</td> <td> Description: A person enters a health care reminder for a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       WELLREMLE <a name="v3-ActCode-WELLREMLE"> </a> </td> <td> wellness reminder list entry</td> <td> Description: A person enters a wellness or preventive care reminder for a given patient. <br/> </td> </tr> <tr> <td> 3</td> <td>     RISKASSESS <a name="v3-ActCode-RISKASSESS"> </a> </td> <td> risk assessment instrument task</td> <td> A person reviews a Risk Assessment Instrument report of a given patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       FALLRISK <a name="v3-ActCode-FALLRISK"> </a> </td> <td> falls risk assessment instrument task</td> <td> A person reviews a Falls Risk Assessment Instrument report of a given patient. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActTransportationModeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActTransportationModeCode"> </a> </td> <td> Characterizes how a transportation act was or will be carried out. <br/> Examples: Via private transport, via public transit, via courier. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActPatientTransportationModeCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActPatientTransportationModeCode"> </a> </td> <td> Definition: Characterizes how a patient was or will be transported to the site of a patient encounter. <br/> Examples: Via ambulance, via public transit, on foot. <br/> </td> </tr> <tr> <td> 3</td> <td>     AFOOT <a name="v3-ActCode-AFOOT"> </a> </td> <td> pedestrian transport</td> <td/> </tr> <tr> <td> 3</td> <td>     AMBT <a name="v3-ActCode-AMBT"> </a> </td> <td> ambulance transport</td> <td/> </tr> <tr> <td> 4</td> <td>       AMBAIR <a name="v3-ActCode-AMBAIR"> </a> </td> <td> fixed-wing ambulance transport</td> <td/> </tr> <tr> <td> 4</td> <td>       AMBGRND <a name="v3-ActCode-AMBGRND"> </a> </td> <td> ground ambulance transport</td> <td/> </tr> <tr> <td> 4</td> <td>       AMBHELO <a name="v3-ActCode-AMBHELO"> </a> </td> <td> helicopter ambulance transport</td> <td/> </tr> <tr> <td> 3</td> <td>     LAWENF <a name="v3-ActCode-LAWENF"> </a> </td> <td> law enforcement transport</td> <td/> </tr> <tr> <td> 3</td> <td>     PRVTRN <a name="v3-ActCode-PRVTRN"> </a> </td> <td> private transport</td> <td/> </tr> <tr> <td> 3</td> <td>     PUBTRN <a name="v3-ActCode-PUBTRN"> </a> </td> <td> public transport</td> <td/> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ObservationType"> </a> </td> <td> Identifies the kinds of observations that can be performed <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActSpecObsCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActSpecObsCode"> </a> </td> <td> Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation <br/> </td> </tr> <tr> <td> 3</td> <td>     ARTBLD <a name="v3-ActCode-ARTBLD"> </a> </td> <td> ActSpecObsArtBldCode</td> <td> Describes the artificial blood identifier that is associated with the specimen. <br/> </td> </tr> <tr> <td> 3</td> <td>     DILUTION <a name="v3-ActCode-DILUTION"> </a> </td> <td> ActSpecObsDilutionCode</td> <td> An observation that reports the dilution of a sample. <br/> </td> </tr> <tr> <td> 4</td> <td>       AUTO-HIGH <a name="v3-ActCode-AUTO-HIGH"> </a> </td> <td> Auto-High Dilution</td> <td> The dilution of a sample performed by automated equipment. The value is specified by the equipment <br/> </td> </tr> <tr> <td> 4</td> <td>       AUTO-LOW <a name="v3-ActCode-AUTO-LOW"> </a> </td> <td> Auto-Low Dilution</td> <td> The dilution of a sample performed by automated equipment. The value is specified by the equipment <br/> </td> </tr> <tr> <td> 4</td> <td>       PRE <a name="v3-ActCode-PRE"> </a> </td> <td> Pre-Dilution</td> <td> The dilution of the specimen made prior to being loaded onto analytical equipment <br/> </td> </tr> <tr> <td> 4</td> <td>       RERUN <a name="v3-ActCode-RERUN"> </a> </td> <td> Rerun Dilution</td> <td> The value of the dilution of a sample after it had been analyzed at a prior dilution value <br/> </td> </tr> <tr> <td> 3</td> <td>     EVNFCTS <a name="v3-ActCode-EVNFCTS"> </a> </td> <td> ActSpecObsEvntfctsCode</td> <td> Domain provides codes that qualify the ActLabObsEnvfctsCode domain. (Environmental Factors) <br/> </td> </tr> <tr> <td> 3</td> <td>     INTFR <a name="v3-ActCode-INTFR"> </a> </td> <td> ActSpecObsInterferenceCode</td> <td> An observation that relates to factors that may potentially cause interference with the observation <br/> </td> </tr> <tr> <td> 4</td> <td>       FIBRIN <a name="v3-ActCode-FIBRIN"> </a> </td> <td> Fibrin</td> <td> The Fibrin Index of the specimen. In the case of only differentiating between Absent and Present, recommend using 0 and 1 <br/> </td> </tr> <tr> <td> 4</td> <td>       HEMOLYSIS <a name="v3-ActCode-HEMOLYSIS"> </a> </td> <td> Hemolysis</td> <td> An observation of the hemolysis index of the specimen in g/L <br/> </td> </tr> <tr> <td> 4</td> <td>       ICTERUS <a name="v3-ActCode-ICTERUS"> </a> </td> <td> Icterus</td> <td> An observation that describes the icterus index of the specimen. It is recommended to use mMol/L of bilirubin <br/> </td> </tr> <tr> <td> 4</td> <td>       LIPEMIA <a name="v3-ActCode-LIPEMIA"> </a> </td> <td> Lipemia</td> <td> An observation used to describe the Lipemia Index of the specimen. It is recommended to use the optical turbidity at 600 nm (in absorbance units). <br/> </td> </tr> <tr> <td> 3</td> <td>     VOLUME <a name="v3-ActCode-VOLUME"> </a> </td> <td> ActSpecObsVolumeCode</td> <td> An observation that reports the volume of a sample. <br/> </td> </tr> <tr> <td> 4</td> <td>       AVAILABLE <a name="v3-ActCode-AVAILABLE"> </a> </td> <td> Available Volume</td> <td> The available quantity of specimen. This is the current quantity minus any planned consumption (e.g., tests that are planned) <br/> </td> </tr> <tr> <td> 4</td> <td>       CONSUMPTION <a name="v3-ActCode-CONSUMPTION"> </a> </td> <td> Consumption Volume</td> <td> The quantity of specimen that is used each time the equipment uses this substance <br/> </td> </tr> <tr> <td> 4</td> <td>       CURRENT <a name="v3-ActCode-CURRENT"> </a> </td> <td> Current Volume</td> <td> The current quantity of the specimen, i.e., initial quantity minus what has been actually used. <br/> </td> </tr> <tr> <td> 4</td> <td>       INITIAL <a name="v3-ActCode-INITIAL"> </a> </td> <td> Initial Volume</td> <td> The initial quantity of the specimen in inventory <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_AnnotationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_AnnotationType"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td>     _ActPatientAnnotationType <a name="v3-ActCode-_ActPatientAnnotationType"> </a> </td> <td> ActPatientAnnotationType</td> <td> Description:Provides a categorization for annotations recorded directly against the patient . <br/> </td> </tr> <tr> <td> 4</td> <td>       ANNDI <a name="v3-ActCode-ANNDI"> </a> </td> <td> diagnostic image note</td> <td> Description:A note that is specific to a patient's diagnostic images, either historical, current or planned. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANNGEN <a name="v3-ActCode-ANNGEN"> </a> </td> <td> general note</td> <td> Description:A general or uncategorized note. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANNIMM <a name="v3-ActCode-ANNIMM"> </a> </td> <td> immunization note</td> <td> A note that is specific to a patient's immunizations, either historical, current or planned.</td> </tr> <tr> <td> 4</td> <td>       ANNLAB <a name="v3-ActCode-ANNLAB"> </a> </td> <td> laboratory note</td> <td> Description:A note that is specific to a patient's laboratory results, either historical, current or planned. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANNMED <a name="v3-ActCode-ANNMED"> </a> </td> <td> medication note</td> <td> Description:A note that is specific to a patient's medications, either historical, current or planned. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_GeneticObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_GeneticObservationType"> </a> </td> <td> Description: None provided <br/> </td> </tr> <tr> <td> 3</td> <td>     GENE <a name="v3-ActCode-GENE"> </a> </td> <td> gene</td> <td> Description: A DNA segment that contributes to phenotype/function. In the absence of demonstrated function a gene may be characterized by sequence, transcription or homology <br/> </td> </tr> <tr> <td> 2</td> <td>   _ImmunizationObservationType <a name="v3-ActCode-_ImmunizationObservationType"> </a> </td> <td> ImmunizationObservationType</td> <td> Description: Observation codes which describe characteristics of the immunization material. <br/> </td> </tr> <tr> <td> 3</td> <td>     OBSANTC <a name="v3-ActCode-OBSANTC"> </a> </td> <td> antigen count</td> <td> Description: Indicates the valid antigen count. <br/> </td> </tr> <tr> <td> 3</td> <td>     OBSANTV <a name="v3-ActCode-OBSANTV"> </a> </td> <td> antigen validity</td> <td> Description: Indicates whether an antigen is valid or invalid. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_IndividualCaseSafetyReportType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_IndividualCaseSafetyReportType"> </a> </td> <td> A code that is used to indicate the type of case safety report received from sender. The current code example reference is from the International Conference on Harmonisation (ICH) Expert Workgroup guideline on Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports. The unknown/unavailable option allows the transmission of information from a secondary sender where the initial sender did not specify the type of report. <br/> Example concepts include: Spontaneous, Report from study, Other. <br/> </td> </tr> <tr> <td> 3</td> <td>     PAT_ADV_EVNT <a name="v3-ActCode-PAT_ADV_EVNT"> </a> </td> <td> patient adverse event</td> <td> Indicates that the ICSR is describing problems that a patient experienced after receiving a vaccine product.</td> </tr> <tr> <td> 3</td> <td>     VAC_PROBLEM <a name="v3-ActCode-VAC_PROBLEM"> </a> </td> <td> vaccine product problem</td> <td> Indicates that the ICSR is describing a problem with the actual vaccine product such as physical defects (cloudy, particulate matter) or inability to confer immunity.</td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_LOINCObservationActContextAgeType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_LOINCObservationActContextAgeType"> </a> </td> <td> Definition:The set of LOINC codes for the act of determining the period of time that has elapsed since an entity was born or created. <br/> </td> </tr> <tr> <td> 3</td> <td>     21611-9 <a name="v3-ActCode-21611-9"> </a> </td> <td> age patient qn est</td> <td> Definition:Estimated age. <br/> </td> </tr> <tr> <td> 3</td> <td>     21612-7 <a name="v3-ActCode-21612-7"> </a> </td> <td> age patient qn reported</td> <td> Definition:Reported age. <br/> </td> </tr> <tr> <td> 3</td> <td>     29553-5 <a name="v3-ActCode-29553-5"> </a> </td> <td> age patient qn calc</td> <td> Definition:Calculated age. <br/> </td> </tr> <tr> <td> 3</td> <td>     30525-0 <a name="v3-ActCode-30525-0"> </a> </td> <td> age patient qn definition</td> <td> Definition:General specification of age with no implied method of determination. <br/> </td> </tr> <tr> <td> 3</td> <td>     30972-4 <a name="v3-ActCode-30972-4"> </a> </td> <td> age at onset of adverse event</td> <td> Definition:Age at onset of associated adverse event; no implied method of determination. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_MedicationObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_MedicationObservationType"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td>     REP_HALF_LIFE <a name="v3-ActCode-REP_HALF_LIFE"> </a> </td> <td> representative half-life</td> <td> Description:This observation represents an 'average' or 'expected' half-life typical of the product. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLCOATING <a name="v3-ActCode-SPLCOATING"> </a> </td> <td> coating</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, indicating whether it has one or more coatings such as sugar coating, film coating, or enteric coating. Only coatings to the external surface or the dosage form should be considered (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration). <br/> Constraints: The Observation.value must be a Boolean (BL) with true for the presence or false for the absence of one or more coatings on a solid dosage form. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLCOLOR <a name="v3-ActCode-SPLCOLOR"> </a> </td> <td> color</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the color or colors that most predominantly define the appearance of the dose form. SPLCOLOR is not an FDA specification for the actual color of solid dosage forms or the names of colors that can appear in labeling. <br/> Constraints: The Observation.value must be a single coded value or a list of multiple coded values, specifying one or more distinct colors that approximate of the color(s) of distinct areas of the solid dosage form, such as the different sides of a tablet or one-part capsule, or the different halves of a two-part capsule. Bands on banded capsules, regardless of the color, are not considered when assigning an SPLCOLOR. Imprints on the dosage form, regardless of their color are not considered when assigning an SPLCOLOR. If more than one color exists on a particular side or half, then the most predominant color on that side or half is recorded. If the gelatin capsule shell is colorless and transparent, use the predominant color of the contents that appears through the colorless and transparent capsule shell. Colors can include: Black;Gray;White;Red;Pink;Purple;Green;Yellow;Ora nge;Brown;Blue;Turquoise. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLIMAGE <a name="v3-ActCode-SPLIMAGE"> </a> </td> <td> image</td> <td> Description: A characteristic representing a single file reference that contains two or more views of the same dosage form of the product; in most cases this should represent front and back views of the dosage form, but occasionally additional views might be needed in order to capture all of the important physical characteristics of the dosage form. Any imprint and/or symbol should be clearly identifiable, and the viewer should not normally need to rotate the image in order to read it. Images that are submitted with SPL should be included in the same directory as the SPL file. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLIMPRINT <a name="v3-ActCode-SPLIMPRINT"> </a> </td> <td> imprint</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the alphanumeric text that appears on the solid dosage form, including text that is embossed, debossed, engraved or printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL. <br/> Examples: Included in SPLIMPRINT are alphanumeric text that appears on the bands of banded capsules and logos and other symbols that can be interpreted as letters or numbers. <br/> Constraints: The Observation.value must be of type Character String (ST). Excluded from SPLIMPRINT are internal and external cut-outs in the form of alphanumeric text and the letter 'R' with a circle around it (when referring to a registered trademark) and the letters 'TM' (when referring to a 'trade mark'). To record text, begin on either side or part of the dosage form. Start at the top left and progress as one would normally read a book. Enter a semicolon to show separation between words or line divisions. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLSCORING <a name="v3-ActCode-SPLSCORING"> </a> </td> <td> scoring</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the number of equal pieces that the solid dosage form can be divided into using score line(s). <br/> Example: One score line creating two equal pieces is given a value of 2, two parallel score lines creating three equal pieces is given a value of 3. <br/> Constraints: Whether three parallel score lines create four equal pieces or two intersecting score lines create two equal pieces using one score line and four equal pieces using both score lines, both have the scoring value of 4. Solid dosage forms that are not scored are given a value of 1. Solid dosage forms that can only be divided into unequal pieces are given a null-value with nullFlavor other (OTH). <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLSHAPE <a name="v3-ActCode-SPLSHAPE"> </a> </td> <td> shape</td> <td> Description: A characteristic of an oral solid dosage form of a medicinal product, specifying the two dimensional representation of the solid dose form, in terms of the outside perimeter of a solid dosage form when the dosage form, resting on a flat surface, is viewed from directly above, including slight rounding of corners. SPLSHAPE does not include embossing, scoring, debossing, or internal cut-outs. SPLSHAPE is independent of the orientation of the imprint and logo. Shapes can include: Triangle (3 sided); Square; Round; Semicircle; Pentagon (5 sided); Diamond; Double circle; Bullet; Hexagon (6 sided); Rectangle; Gear; Capsule; Heptagon (7 sided); Trapezoid; Oval; Clover; Octagon (8 sided); Tear; Freeform. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLSIZE <a name="v3-ActCode-SPLSIZE"> </a> </td> <td> size</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, specifying the longest single dimension of the solid dosage form as a physical quantity in the dimension of length (e.g., 3 mm). The length is should be specified in millimeters and should be rounded to the nearest whole millimeter. <br/> Example: SPLSIZE for a rectangular shaped tablet is the length and SPLSIZE for a round shaped tablet is the diameter. <br/> </td> </tr> <tr> <td> 3</td> <td>     SPLSYMBOL <a name="v3-ActCode-SPLSYMBOL"> </a> </td> <td> symbol</td> <td> Definition: A characteristic of an oral solid dosage form of a medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and definite recognition. Score lines, letters, numbers, and internal and external cut-outs are not considered marks or symbols. See SPLSCORING and SPLIMPRINT for these characteristics. <br/> Constraints: The Observation.value must be a Boolean (BL) with <u>true</u> indicating the presence and <u>false</u> for the absence of marks or symbols. <br/> Example: <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ObservationIssueTriggerCodedObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ObservationIssueTriggerCodedObservationType"> </a> </td> <td> Distinguishes the kinds of coded observations that could be the trigger for clinical issue detection. These are observations that are not measurable, but instead can be defined with codes. Coded observation types include: Allergy, Intolerance, Medical Condition, Pregnancy status, etc. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_CaseTransmissionMode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_CaseTransmissionMode"> </a> </td> <td> Code for the mechanism by which disease was acquired by the living subject involved in the public health case. Includes sexually transmitted, airborne, bloodborne, vectorborne, foodborne, zoonotic, nosocomial, mechanical, dermal, congenital, environmental exposure, indeterminate. <br/> </td> </tr> <tr> <td> 4</td> <td>       AIRTRNS <a name="v3-ActCode-AIRTRNS"> </a> </td> <td> airborne transmission</td> <td> Communication of an agent from a living subject or environmental source to a living subject through indirect contact via oral or nasal inhalation. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANANTRNS <a name="v3-ActCode-ANANTRNS"> </a> </td> <td> animal to animal transmission</td> <td> Communication of an agent from one animal to another proximate animal. <br/> </td> </tr> <tr> <td> 4</td> <td>       ANHUMTRNS <a name="v3-ActCode-ANHUMTRNS"> </a> </td> <td> animal to human transmission</td> <td> Communication of an agent from an animal to a proximate person. <br/> </td> </tr> <tr> <td> 4</td> <td>       BDYFLDTRNS <a name="v3-ActCode-BDYFLDTRNS"> </a> </td> <td> body fluid contact transmission</td> <td> Communication of an agent from one living subject to another living subject through direct contact with any body fluid. <br/> </td> </tr> <tr> <td> 4</td> <td>       BLDTRNS <a name="v3-ActCode-BLDTRNS"> </a> </td> <td> blood borne transmission</td> <td> Communication of an agent to a living subject through direct contact with blood or blood products whether the contact with blood is part of a therapeutic procedure or not. <br/> </td> </tr> <tr> <td> 4</td> <td>       DERMTRNS <a name="v3-ActCode-DERMTRNS"> </a> </td> <td> transdermal transmission</td> <td> Communication of an agent from a living subject or environmental source to a living subject via agent migration through intact skin. <br/> </td> </tr> <tr> <td> 4</td> <td>       ENVTRNS <a name="v3-ActCode-ENVTRNS"> </a> </td> <td> environmental exposure transmission</td> <td> Communication of an agent from an environmental surface or source to a living subject by direct contact. <br/> </td> </tr> <tr> <td> 4</td> <td>       FECTRNS <a name="v3-ActCode-FECTRNS"> </a> </td> <td> fecal-oral transmission</td> <td> Communication of an agent from a living subject or environmental source to a living subject through oral contact with material contaminated by person or animal fecal material. <br/> </td> </tr> <tr> <td> 4</td> <td>       FOMTRNS <a name="v3-ActCode-FOMTRNS"> </a> </td> <td> fomite transmission</td> <td> Communication of an agent from an non-living material to a living subject through direct contact. <br/> </td> </tr> <tr> <td> 4</td> <td>       FOODTRNS <a name="v3-ActCode-FOODTRNS"> </a> </td> <td> food-borne transmission</td> <td> Communication of an agent from a food source to a living subject via oral consumption. <br/> </td> </tr> <tr> <td> 4</td> <td>       HUMHUMTRNS <a name="v3-ActCode-HUMHUMTRNS"> </a> </td> <td> human to human transmission</td> <td> Communication of an agent from a person to a proximate person. <br/> </td> </tr> <tr> <td> 4</td> <td>       INDTRNS <a name="v3-ActCode-INDTRNS"> </a> </td> <td> indeterminate disease transmission mode</td> <td> Communication of an agent to a living subject via an undetermined route. <br/> </td> </tr> <tr> <td> 4</td> <td>       LACTTRNS <a name="v3-ActCode-LACTTRNS"> </a> </td> <td> lactation transmission</td> <td> Communication of an agent from one living subject to another living subject through direct contact with mammalian milk or colostrum. <br/> </td> </tr> <tr> <td> 4</td> <td>       NOSTRNS <a name="v3-ActCode-NOSTRNS"> </a> </td> <td> nosocomial transmission</td> <td> Communication of an agent from any entity to a living subject while the living subject is in the patient role in a healthcare facility. <br/> </td> </tr> <tr> <td> 4</td> <td>       PARTRNS <a name="v3-ActCode-PARTRNS"> </a> </td> <td> parenteral transmission</td> <td> Communication of an agent from a living subject or environmental source to a living subject where the acquisition of the agent is not via the alimentary canal. <br/> </td> </tr> <tr> <td> 4</td> <td>       PLACTRNS <a name="v3-ActCode-PLACTRNS"> </a> </td> <td> transplacental transmission</td> <td> Communication of an agent from a living subject to the progeny of that living subject via agent migration across the maternal-fetal placental membranes while in utero. <br/> </td> </tr> <tr> <td> 4</td> <td>       SEXTRNS <a name="v3-ActCode-SEXTRNS"> </a> </td> <td> sexual transmission</td> <td> Communication of an agent from one living subject to another living subject through direct contact with genital or oral tissues as part of a sexual act. <br/> </td> </tr> <tr> <td> 4</td> <td>       TRNSFTRNS <a name="v3-ActCode-TRNSFTRNS"> </a> </td> <td> transfusion transmission</td> <td> Communication of an agent from one living subject to another living subject through direct contact with blood or blood products where the contact with blood is part of a therapeutic procedure. <br/> </td> </tr> <tr> <td> 4</td> <td>       VECTRNS <a name="v3-ActCode-VECTRNS"> </a> </td> <td> vector-borne transmission</td> <td> Communication of an agent from a living subject acting as a required intermediary in the agent transmission process to a recipient living subject via direct contact. <br/> </td> </tr> <tr> <td> 4</td> <td>       WATTRNS <a name="v3-ActCode-WATTRNS"> </a> </td> <td> water-borne transmission</td> <td> Communication of an agent from a contaminated water source to a living subject whether the water is ingested as a food or not. The route of entry of the water may be through any bodily orifice. <br/> </td> </tr> <tr> <td> 2</td> <td>   _ObservationQualityMeasureAttribute <a name="v3-ActCode-_ObservationQualityMeasureAttribute"> </a> </td> <td> ObservationQualityMeasureAttribute</td> <td> Codes used to define various metadata aspects of a health quality measure. <br/> </td> </tr> <tr> <td> 3</td> <td>     AGGREGATE <a name="v3-ActCode-AGGREGATE"> </a> </td> <td> aggregate measure observation</td> <td> Indicates that the observation is carrying out an aggregation calculation, contained in the value element. <br/> </td> </tr> <tr> <td> 3</td> <td>     CMPMSRMTH <a name="v3-ActCode-CMPMSRMTH"> </a> </td> <td> composite measure method</td> <td> Indicates what method is used in a quality measure to combine the component measure results included in an composite measure. <br/> </td> </tr> <tr> <td> 3</td> <td>     CMPMSRSCRWGHT <a name="v3-ActCode-CMPMSRSCRWGHT"> </a> </td> <td> component measure scoring weight</td> <td> An attribute of a quality measure describing the weight this component measure score is to carry in determining the overall composite measure final score. The value is real value greater than 0 and less than 1.0. Each component measure score will be multiplied by its CMPMSRSCRWGHT and then summed with the other component measures to determine the final overall composite measure score. The sum across all CMPMSRSCRWGHT values within a single composite measure SHALL be 1.0. The value assigned is scoped to the composite measure referencing this component measure only. <br/> </td> </tr> <tr> <td> 3</td> <td>     COPY <a name="v3-ActCode-COPY"> </a> </td> <td> copyright</td> <td> Identifies the organization(s) who own the intellectual property represented by the eMeasure. <br/> </td> </tr> <tr> <td> 3</td> <td>     CRS <a name="v3-ActCode-CRS"> </a> </td> <td> clinical recommendation statement</td> <td> Summary of relevant clinical guidelines or other clinical recommendations supporting this eMeasure. <br/> </td> </tr> <tr> <td> 3</td> <td>     DEF <a name="v3-ActCode-DEF"> </a> </td> <td> definition</td> <td> Description of individual terms, provided as needed. <br/> </td> </tr> <tr> <td> 3</td> <td>     DISC <a name="v3-ActCode-DISC"> </a> </td> <td> disclaimer</td> <td> Disclaimer information for the eMeasure. <br/> </td> </tr> <tr> <td> 3</td> <td>     FINALDT <a name="v3-ActCode-FINALDT"> </a> </td> <td> finalized date/time</td> <td> The timestamp when the eMeasure was last packaged in the Measure Authoring Tool. <br/> </td> </tr> <tr> <td> 3</td> <td>     GUIDE <a name="v3-ActCode-GUIDE"> </a> </td> <td> guidance</td> <td> Used to allow measure developers to provide additional guidance for implementers to understand greater specificity than could be provided in the logic for data criteria. <br/> </td> </tr> <tr> <td> 3</td> <td>     IDUR <a name="v3-ActCode-IDUR"> </a> </td> <td> improvement notation</td> <td> Information on whether an increase or decrease in score is the preferred result (e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range). <br/> </td> </tr> <tr> <td> 3</td> <td>     ITMCNT <a name="v3-ActCode-ITMCNT"> </a> </td> <td> items counted</td> <td> Describes the items counted by the measure (e.g., patients, encounters, procedures, etc.) <br/> </td> </tr> <tr> <td> 3</td> <td>     KEY <a name="v3-ActCode-KEY"> </a> </td> <td> keyword</td> <td> A significant word that aids in discoverability. <br/> </td> </tr> <tr> <td> 3</td> <td>     MEDT <a name="v3-ActCode-MEDT"> </a> </td> <td> measurement end date</td> <td> The end date of the measurement period. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSD <a name="v3-ActCode-MSD"> </a> </td> <td> measurement start date</td> <td> The start date of the measurement period. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRADJ <a name="v3-ActCode-MSRADJ"> </a> </td> <td> risk adjustment</td> <td> The method of adjusting for clinical severity and conditions present at the start of care that can influence patient outcomes for making valid comparisons of outcome measures across providers. Indicates whether an eMeasure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow more useful comparisons. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRAGG <a name="v3-ActCode-MSRAGG"> </a> </td> <td> rate aggregation</td> <td> Describes how to combine information calculated based on logic in each of several populations into one summarized result. It can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure. (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). <br/> Open Issue: The description does NOT align well with the definition used in the HQMF specfication; correct the MSGAGG definition, and the possible distinction of MSRAGG as a child of AGGREGATE. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRIMPROV <a name="v3-ActCode-MSRIMPROV"> </a> </td> <td> health quality measure improvement notation</td> <td> Information on whether an increase or decrease in score is the preferred result. This should reflect information on which way is better, an increase or decrease in score. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRJUR <a name="v3-ActCode-MSRJUR"> </a> </td> <td> jurisdiction</td> <td> The list of jurisdiction(s) for which the measure applies. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRRPTR <a name="v3-ActCode-MSRRPTR"> </a> </td> <td> reporter type</td> <td> Type of person or organization that is expected to report the issue. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRRPTTIME <a name="v3-ActCode-MSRRPTTIME"> </a> </td> <td> timeframe for reporting</td> <td> The maximum time that may elapse following completion of the measure until the measure report must be sent to the receiver. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRSCORE <a name="v3-ActCode-MSRSCORE"> </a> </td> <td> measure scoring</td> <td> Indicates how the calculation is performed for the eMeasure (e.g., proportion, continuous variable, ratio) <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRSET <a name="v3-ActCode-MSRSET"> </a> </td> <td> health quality measure care setting</td> <td> Location(s) in which care being measured is rendered <br/> Usage Note: MSRSET is used rather than RoleCode because the setting applies to what is being measured, as opposed to participating directly in the health quality measure documantion itself). <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRTOPIC <a name="v3-ActCode-MSRTOPIC"> </a> </td> <td> health quality measure topic type</td> <td> <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRTP <a name="v3-ActCode-MSRTP"> </a> </td> <td> measurement period</td> <td> The time period for which the eMeasure applies. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRTYPE <a name="v3-ActCode-MSRTYPE"> </a> </td> <td> measure type</td> <td> Indicates whether the eMeasure is used to examine a process or an outcome over time (e.g., Structure, Process, Outcome). <br/> </td> </tr> <tr> <td> 3</td> <td>     RAT <a name="v3-ActCode-RAT"> </a> </td> <td> rationale</td> <td> Succinct statement of the need for the measure. Usually includes statements pertaining to Importance criterion: impact, gap in care and evidence. <br/> </td> </tr> <tr> <td> 3</td> <td>     REF <a name="v3-ActCode-REF"> </a> </td> <td> reference</td> <td> Identifies bibliographic citations or references to clinical practice guidelines, sources of evidence, or other relevant materials supporting the intent and rationale of the eMeasure. <br/> </td> </tr> <tr> <td> 3</td> <td>     SDE <a name="v3-ActCode-SDE"> </a> </td> <td> supplemental data elements</td> <td> Comparison of results across strata can be used to show where disparities exist or where there is a need to expose differences in results. For example, Centers for Medicare & Medicaid Services (CMS) in the U.S. defines four required Supplemental Data Elements (payer, ethnicity, race, and gender), which are variables used to aggregate data into various subgroups. Additional supplemental data elements required for risk adjustment or other purposes of data aggregation can be included in the Supplemental Data Element section. <br/> </td> </tr> <tr> <td> 3</td> <td>     STRAT <a name="v3-ActCode-STRAT"> </a> </td> <td> stratification</td> <td> Describes the strata for which the measure is to be evaluated. There are three examples of reasons for stratification based on existing work. These include: (1) evaluate the measure based on different age groupings within the population described in the measure (e.g., evaluate the whole [age 14-25] and each sub-stratum [14-19] and [20-25]); (2) evaluate the eMeasure based on either a specific condition, a specific discharge location, or both; (3) evaluate the eMeasure based on different locations within a facility (e.g., evaluate the overall rate for all intensive care units and also some strata include additional findings [specific birth weights for neonatal intensive care units]). <br/> </td> </tr> <tr> <td> 3</td> <td>     TRANF <a name="v3-ActCode-TRANF"> </a> </td> <td> transmission format</td> <td> Can be a URL or hyperlinks that link to the transmission formats that are specified for a particular reporting program. <br/> </td> </tr> <tr> <td> 3</td> <td>     USE <a name="v3-ActCode-USE"> </a> </td> <td> notice of use</td> <td> Usage notes. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ObservationSequenceType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ObservationSequenceType"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td>     TIME_ABSOLUTE <a name="v3-ActCode-TIME_ABSOLUTE"> </a> </td> <td> absolute time sequence</td> <td> A sequence of values in the "absolute" time domain. This is the same time domain that all HL7 timestamps use. It is time as measured by the Gregorian calendar <br/> </td> </tr> <tr> <td> 3</td> <td>     TIME_RELATIVE <a name="v3-ActCode-TIME_RELATIVE"> </a> </td> <td> relative time sequence</td> <td> A sequence of values in a "relative" time domain. The time is measured relative to the earliest effective time in the Observation Series containing this sequence. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ObservationSeriesType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ObservationSeriesType"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ECGObservationSeriesType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ECGObservationSeriesType"> </a> </td> <td/> </tr> <tr> <td> 4</td> <td>       REPRESENTATIVE_BEAT <a name="v3-ActCode-REPRESENTATIVE_BEAT"> </a> </td> <td> ECG representative beat waveforms</td> <td> This Observation Series type contains waveforms of a "representative beat" (a.k.a. "median beat" or "average beat"). The waveform samples are measured in relative time, relative to the beginning of the beat as defined by the Observation Series effective time. The waveforms are not directly acquired from the subject, but rather algorithmically derived from the "rhythm" waveforms. <br/> </td> </tr> <tr> <td> 4</td> <td>       RHYTHM <a name="v3-ActCode-RHYTHM"> </a> </td> <td> ECG rhythm waveforms</td> <td> This Observation type contains ECG "rhythm" waveforms. The waveform samples are measured in absolute time (a.k.a. "subject time" or "effective time"). These waveforms are usually "raw" with some minimal amount of noise reduction and baseline filtering applied. <br/> </td> </tr> <tr> <td> 2</td> <td>   _PatientImmunizationRelatedObservationType <a name="v3-ActCode-_PatientImmunizationRelatedObservationType"> </a> </td> <td> PatientImmunizationRelatedObservationType</td> <td> Description: Reporting codes that are related to an immunization event. <br/> </td> </tr> <tr> <td> 3</td> <td>     CLSSRM <a name="v3-ActCode-CLSSRM"> </a> </td> <td> classroom</td> <td> Description: The class room associated with the patient during the immunization event. <br/> </td> </tr> <tr> <td> 3</td> <td>     GRADE <a name="v3-ActCode-GRADE"> </a> </td> <td> grade</td> <td> Description: The school grade or level the patient was in when immunized. <br/> </td> </tr> <tr> <td> 3</td> <td>     SCHL <a name="v3-ActCode-SCHL"> </a> </td> <td> school</td> <td> Description: The school the patient attended when immunized. <br/> </td> </tr> <tr> <td> 3</td> <td>     SCHLDIV <a name="v3-ActCode-SCHLDIV"> </a> </td> <td> school division</td> <td> Description: The school division or district associated with the patient during the immunization event. <br/> </td> </tr> <tr> <td> 3</td> <td>     TEACHER <a name="v3-ActCode-TEACHER"> </a> </td> <td> teacher</td> <td> Description: The patient's teacher when immunized. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_PopulationInclusionObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_PopulationInclusionObservationType"> </a> </td> <td> Observation types for specifying criteria used to assert that a subject is included in a particular population. <br/> </td> </tr> <tr> <td> 3</td> <td>     DENEX <a name="v3-ActCode-DENEX"> </a> </td> <td> denominator exclusions</td> <td> Criteria which specify subjects who should be removed from the eMeasure population and denominator before determining if numerator criteria are met. Denominator exclusions are used in proportion and ratio measures to help narrow the denominator. <br/> </td> </tr> <tr> <td> 3</td> <td>     DENEXCEP <a name="v3-ActCode-DENEXCEP"> </a> </td> <td> denominator exceptions</td> <td> Criteria which specify the removal of a subject, procedure or unit of measurement from the denominator, only if the numerator criteria are not met. Denominator exceptions allow for adjustment of the calculated score for those providers with higher risk populations. Denominator exceptions are used only in proportion eMeasures. They are not appropriate for ratio or continuous variable eMeasures. Denominator exceptions allow for the exercise of clinical judgment and should be specifically defined where capturing the information in a structured manner fits the clinical workflow. Generic denominator exception reasons used in proportion eMeasures fall into three general categories: <br/> Medical reasons Patient (or subject) reasons System reasons </td> </tr> <tr> <td> 3</td> <td>     DENOM <a name="v3-ActCode-DENOM"> </a> </td> <td> denominator</td> <td> Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). The denominator can be the same as the initial population, or it may be a subset of the initial population to further constrain it for the purpose of the eMeasure. Different measures within an eMeasure set may have different denominators. Continuous Variable eMeasures do not have a denominator, but instead define a measure population. <br/> </td> </tr> <tr> <td> 3</td> <td>     IPOP <a name="v3-ActCode-IPOP"> </a> </td> <td> initial population</td> <td> Criteria for specifying the entities to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). <br/> </td> </tr> <tr> <td> 4</td> <td>       IPPOP <a name="v3-ActCode-IPPOP"> </a> </td> <td> initial patient population</td> <td> Criteria for specifying the patients to be evaluated by a specific quality measure, based on a shared common set of characteristics (within a specific measurement set to which a given measure belongs). Details often include information based upon specific age groups, diagnoses, diagnostic and procedure codes, and enrollment periods. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSROBS <a name="v3-ActCode-MSROBS"> </a> </td> <td> measure observation</td> <td> Defines the observation to be performed for each patient or event in the measure population. Measure observations for each case in the population are aggregated to determine the overall measure score for the population. <br/> Examples: <br/> the median time from arrival in the Emergency Room to departure the median time from decision to admit to a hospital to the actual admission for Emergency Room patients </td> </tr> <tr> <td> 3</td> <td>     MSRPOPL <a name="v3-ActCode-MSRPOPL"> </a> </td> <td> measure population</td> <td> Criteria for specifying the measure population as a narrative description (e.g., all patients seen in the Emergency Department during the measurement period). This is used only in continuous variable eMeasures. <br/> </td> </tr> <tr> <td> 3</td> <td>     MSRPOPLEX <a name="v3-ActCode-MSRPOPLEX"> </a> </td> <td> measure population exclusions</td> <td> Criteria for specifying subjects who should be removed from the eMeasure's Initial Population and Measure Population. Measure Population Exclusions are used in Continuous Variable measures to help narrow the Measure Population before determining the value(s) of the continuous variable(s). <br/> </td> </tr> <tr> <td> 3</td> <td>     NUMER <a name="v3-ActCode-NUMER"> </a> </td> <td> numerator</td> <td> Criteria for specifying the processes or outcomes expected for each patient, procedure, or other unit of measurement defined in the denominator for proportion measures, or related to (but not directly derived from) the denominator for ratio measures (e.g., a numerator listing the number of central line blood stream infections and a denominator indicating the days per thousand of central line usage in a specific time period). <br/> </td> </tr> <tr> <td> 3</td> <td>     NUMEX <a name="v3-ActCode-NUMEX"> </a> </td> <td> numerator exclusions</td> <td> Criteria for specifying instances that should not be included in the numerator data. (e.g., if the number of central line blood stream infections per 1000 catheter days were to exclude infections with a specific bacterium, that bacterium would be listed as a numerator exclusion). Numerator Exclusions are used only in ratio eMeasures. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_PreferenceObservationType)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_PreferenceObservationType"> </a> </td> <td> Types of observations that can be made about Preferences. <br/> </td> </tr> <tr> <td> 3</td> <td>     PREFSTRENGTH <a name="v3-ActCode-PREFSTRENGTH"> </a> </td> <td> preference strength</td> <td> An observation about how important a preference is to the target of the preference. <br/> </td> </tr> <tr> <td> 2</td> <td>   ADVERSE_REACTION <a name="v3-ActCode-ADVERSE_REACTION"> </a> </td> <td> Adverse Reaction</td> <td> Indicates that the observation is of an unexpected negative occurrence in the subject suspected to result from the subject's exposure to one or more agents. Observation values would be the symptom resulting from the reaction. <br/> </td> </tr> <tr> <td> 2</td> <td>   ASSERTION <a name="v3-ActCode-ASSERTION"> </a> </td> <td> Assertion</td> <td> Description:Refines classCode OBS to indicate an observation in which observation.value contains a finding or other nominalized statement, where the encoded information in Observation.value is not altered by Observation.code. For instance, observation.code="ASSERTION" and observation.value="fracture of femur present" is an assertion of a clinical finding of femur fracture. <br/> </td> </tr> <tr> <td> 2</td> <td>   CASESER <a name="v3-ActCode-CASESER"> </a> </td> <td> case seriousness criteria</td> <td> Definition:An observation that provides a characterization of the level of harm to an investigation subject as a result of a reaction or event. <br/> </td> </tr> <tr> <td> 2</td> <td>   CDIO <a name="v3-ActCode-CDIO"> </a> </td> <td> case disease imported observation</td> <td> An observation that states whether the disease was likely acquired outside the jurisdiction of observation, and if so, the nature of the inter-jurisdictional relationship. <br/> OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. <br/> </td> </tr> <tr> <td> 2</td> <td>   CRIT <a name="v3-ActCode-CRIT"> </a> </td> <td> criticality</td> <td> A clinical judgment as to the worst case result of a future exposure (including substance administration). When the worst case result is assessed to have a life-threatening or organ system threatening potential, it is considered to be of high criticality. <br/> </td> </tr> <tr> <td> 2</td> <td>   CTMO <a name="v3-ActCode-CTMO"> </a> </td> <td> case transmission mode observation</td> <td> An observation that states the mechanism by which disease was acquired by the living subject involved in the public health case. <br/> OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it. <br/> </td> </tr> <tr> <td> 2</td> <td>   DX <a name="v3-ActCode-DX"> </a> </td> <td> ObservationDiagnosisTypes</td> <td> Includes all codes defining types of indications such as diagnosis, symptom and other indications such as contrast agents for lab tests. <br/> </td> </tr> <tr> <td> 3</td> <td>     ADMDX <a name="v3-ActCode-ADMDX"> </a> </td> <td> admitting diagnosis</td> <td> Admitting diagnosis are the diagnoses documented for administrative purposes as the basis for a hospital admission. <br/> </td> </tr> <tr> <td> 3</td> <td>     DISDX <a name="v3-ActCode-DISDX"> </a> </td> <td> discharge diagnosis</td> <td> Discharge diagnosis are the diagnoses documented for administrative purposes as the time of hospital discharge. <br/> </td> </tr> <tr> <td> 3</td> <td>     INTDX <a name="v3-ActCode-INTDX"> </a> </td> <td> intermediate diagnosis</td> <td> Intermediate diagnoses are those diagnoses documented for administrative purposes during the course of a hospital stay. <br/> </td> </tr> <tr> <td> 3</td> <td>     NOI <a name="v3-ActCode-NOI"> </a> </td> <td> nature of injury</td> <td> The type of injury that the injury coding specifies. <br/> </td> </tr> <tr> <td> 2</td> <td>   GISTIER <a name="v3-ActCode-GISTIER"> </a> </td> <td> GIS tier</td> <td> Description: Accuracy determined as per the GIS tier code system. <br/> </td> </tr> <tr> <td> 2</td> <td>   HHOBS <a name="v3-ActCode-HHOBS"> </a> </td> <td> household situation observation</td> <td> Indicates that the observation is of a person’s living situation in a household including the household composition and circumstances. <br/> </td> </tr> <tr> <td> 2</td> <td>   ISSUE <a name="v3-ActCode-ISSUE"> </a> </td> <td> detected issue</td> <td> There is a clinical issue for the therapy that makes continuation of the therapy inappropriate. <br/> Open Issue: The definition of this code does not correctly represent the concept space of its specializations (children) <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActAdministrativeDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdministrativeDetectedIssueCode"> </a> </td> <td> Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActAdministrativeAuthorizationDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdministrativeAuthorizationDetectedIssueCode"> </a> </td> <td/> </tr> <tr> <td> 5</td> <td>         NAT <a name="v3-ActCode-NAT"> </a> </td> <td> Insufficient authorization</td> <td> The requesting party has insufficient authorization to invoke the interaction. <br/> </td> </tr> <tr> <td> 5</td> <td>         SUPPRESSED <a name="v3-ActCode-SUPPRESSED"> </a> </td> <td> record suppressed</td> <td> Description: One or more records in the query response have been suppressed due to consent or privacy restrictions. <br/> </td> </tr> <tr> <td> 5</td> <td>         VALIDAT <a name="v3-ActCode-VALIDAT"> </a> </td> <td> validation issue</td> <td> Description:The specified element did not pass business-rule validation. <br/> </td> </tr> <tr> <td> 6</td> <td>           KEY204 <a name="v3-ActCode-KEY204"> </a> </td> <td> Unknown key identifier</td> <td> The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient. <br/> </td> </tr> <tr> <td> 6</td> <td>           KEY205 <a name="v3-ActCode-KEY205"> </a> </td> <td> Duplicate key identifier</td> <td> The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.). <br/> </td> </tr> <tr> <td> 6</td> <td>           COMPLY <a name="v3-ActCode-COMPLY"> </a> </td> <td> Compliance Alert</td> <td> There may be an issue with the patient complying with the intentions of the proposed therapy <br/> </td> </tr> <tr> <td> 7</td> <td>             DUPTHPY <a name="v3-ActCode-DUPTHPY"> </a> </td> <td> Duplicate Therapy Alert</td> <td> The proposed therapy appears to duplicate an existing therapy <br/> </td> </tr> <tr> <td> 8</td> <td>               DUPTHPCLS <a name="v3-ActCode-DUPTHPCLS"> </a> </td> <td> duplicate therapeutic alass alert</td> <td> Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy, though the specific mechanisms of action vary. <br/> </td> </tr> <tr> <td> 8</td> <td>               DUPTHPGEN <a name="v3-ActCode-DUPTHPGEN"> </a> </td> <td> duplicate generic alert</td> <td> Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy and uses the same mechanisms of action as the existing therapy. <br/> </td> </tr> <tr> <td> 7</td> <td>             ABUSE <a name="v3-ActCode-ABUSE"> </a> </td> <td> commonly abused/misused alert</td> <td> Description:The proposed therapy is frequently misused or abused and therefore should be used with caution and/or monitoring. <br/> </td> </tr> <tr> <td> 7</td> <td>             FRAUD <a name="v3-ActCode-FRAUD"> </a> </td> <td> potential fraud</td> <td> Description:The request is suspected to have a fraudulent basis. <br/> </td> </tr> <tr> <td> 7</td> <td>             PLYDOC <a name="v3-ActCode-PLYDOC"> </a> </td> <td> Poly-orderer Alert</td> <td> A similar or identical therapy was recently ordered by a different practitioner. <br/> </td> </tr> <tr> <td> 7</td> <td>             PLYPHRM <a name="v3-ActCode-PLYPHRM"> </a> </td> <td> Poly-supplier Alert</td> <td> This patient was recently supplied a similar or identical therapy from a different pharmacy or supplier. <br/> </td> </tr> <tr> <td> 6</td> <td>           DOSE <a name="v3-ActCode-DOSE"> </a> </td> <td> Dosage problem</td> <td> Proposed dosage instructions for therapy differ from standard practice. <br/> </td> </tr> <tr> <td> 7</td> <td>             DOSECOND <a name="v3-ActCode-DOSECOND"> </a> </td> <td> dosage-condition alert</td> <td> Description:Proposed dosage is inappropriate due to patient's medical condition. <br/> </td> </tr> <tr> <td> 7</td> <td>             DOSEDUR <a name="v3-ActCode-DOSEDUR"> </a> </td> <td> Dose-Duration Alert</td> <td> Proposed length of therapy differs from standard practice. <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEDURH <a name="v3-ActCode-DOSEDURH"> </a> </td> <td> Dose-Duration High Alert</td> <td> Proposed length of therapy is longer than standard practice <br/> </td> </tr> <tr> <td> 9</td> <td>                 DOSEDURHIND <a name="v3-ActCode-DOSEDURHIND"> </a> </td> <td> Dose-Duration High for Indication Alert</td> <td> Proposed length of therapy is longer than standard practice for the identified indication or diagnosis <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEDURL <a name="v3-ActCode-DOSEDURL"> </a> </td> <td> Dose-Duration Low Alert</td> <td> Proposed length of therapy is shorter than that necessary for therapeutic effect <br/> </td> </tr> <tr> <td> 9</td> <td>                 DOSEDURLIND <a name="v3-ActCode-DOSEDURLIND"> </a> </td> <td> Dose-Duration Low for Indication Alert</td> <td> Proposed length of therapy is shorter than standard practice for the identified indication or diagnosis <br/> </td> </tr> <tr> <td> 7</td> <td>             DOSEH <a name="v3-ActCode-DOSEH"> </a> </td> <td> High Dose Alert</td> <td> Proposed dosage exceeds standard practice <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEHINDA <a name="v3-ActCode-DOSEHINDA"> </a> </td> <td> High Dose for Age Alert</td> <td> Proposed dosage exceeds standard practice for the patient's age <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEHIND <a name="v3-ActCode-DOSEHIND"> </a> </td> <td> High Dose for Indication Alert</td> <td/> </tr> <tr> <td> 8</td> <td>               DOSEHINDSA <a name="v3-ActCode-DOSEHINDSA"> </a> </td> <td> High Dose for Height/Surface Area Alert</td> <td> Proposed dosage exceeds standard practice for the patient's height or body surface area <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEHINDW <a name="v3-ActCode-DOSEHINDW"> </a> </td> <td> High Dose for Weight Alert</td> <td> Proposed dosage exceeds standard practice for the patient's weight <br/> </td> </tr> <tr> <td> 7</td> <td>             DOSEIVL <a name="v3-ActCode-DOSEIVL"> </a> </td> <td> Dose-Interval Alert</td> <td> Proposed dosage interval/timing differs from standard practice <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSEIVLIND <a name="v3-ActCode-DOSEIVLIND"> </a> </td> <td> Dose-Interval for Indication Alert</td> <td> Proposed dosage interval/timing differs from standard practice for the identified indication or diagnosis <br/> </td> </tr> <tr> <td> 7</td> <td>             DOSEL <a name="v3-ActCode-DOSEL"> </a> </td> <td> Low Dose Alert</td> <td> Proposed dosage is below suggested therapeutic levels <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSELINDA <a name="v3-ActCode-DOSELINDA"> </a> </td> <td> Low Dose for Age Alert</td> <td> Proposed dosage is below suggested therapeutic levels for the patient's age <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSELIND <a name="v3-ActCode-DOSELIND"> </a> </td> <td> Low Dose for Indication Alert</td> <td/> </tr> <tr> <td> 8</td> <td>               DOSELINDSA <a name="v3-ActCode-DOSELINDSA"> </a> </td> <td> Low Dose for Height/Surface Area Alert</td> <td> Proposed dosage is below suggested therapeutic levels for the patient's height or body surface area <br/> </td> </tr> <tr> <td> 8</td> <td>               DOSELINDW <a name="v3-ActCode-DOSELINDW"> </a> </td> <td> Low Dose for Weight Alert</td> <td> Proposed dosage is below suggested therapeutic levels for the patient's weight <br/> </td> </tr> <tr> <td> 7</td> <td>             MDOSE <a name="v3-ActCode-MDOSE"> </a> </td> <td> maximum dosage reached</td> <td> Description:The maximum quantity of this drug allowed to be administered within a particular time-range (month, year, lifetime) has been reached or exceeded. <br/> </td> </tr> <tr> <td> 6</td> <td>           OBSA <a name="v3-ActCode-OBSA"> </a> </td> <td> Observation Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient <br/> </td> </tr> <tr> <td> 7</td> <td>             AGE <a name="v3-ActCode-AGE"> </a> </td> <td> Age Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to patient age <br/> </td> </tr> <tr> <td> 8</td> <td>               ADALRT <a name="v3-ActCode-ADALRT"> </a> </td> <td> adult alert</td> <td> Proposed therapy is outside of the standard practice for an adult patient. <br/> </td> </tr> <tr> <td> 8</td> <td>               <a href="#DOSEHINDA">DOSEHINDA</a> </td> <td/> <td/> </tr> <tr> <td> 8</td> <td>               <a href="#DOSELINDA">DOSELINDA</a> </td> <td/> <td/> </tr> <tr> <td> 8</td> <td>               GEALRT <a name="v3-ActCode-GEALRT"> </a> </td> <td> geriatric alert</td> <td> Proposed therapy is outside of standard practice for a geriatric patient. <br/> </td> </tr> <tr> <td> 8</td> <td>               PEALRT <a name="v3-ActCode-PEALRT"> </a> </td> <td> pediatric alert</td> <td> Proposed therapy is outside of the standard practice for a pediatric patient. <br/> </td> </tr> <tr> <td> 7</td> <td>             COND <a name="v3-ActCode-COND"> </a> </td> <td> Condition Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis <br/> </td> </tr> <tr> <td> 8</td> <td>               HGHT <a name="v3-ActCode-HGHT"> </a> </td> <td/> <td/> </tr> <tr> <td> 8</td> <td>               LACT <a name="v3-ActCode-LACT"> </a> </td> <td> Lactation Alert</td> <td> Proposed therapy may be inappropriate or contraindicated when breast-feeding <br/> </td> </tr> <tr> <td> 8</td> <td>               PREG <a name="v3-ActCode-PREG"> </a> </td> <td> Pregnancy Alert</td> <td> Proposed therapy may be inappropriate or contraindicated during pregnancy <br/> </td> </tr> <tr> <td> 8</td> <td>               WGHT <a name="v3-ActCode-WGHT"> </a> </td> <td/> <td/> </tr> <tr> <td> 7</td> <td>             CREACT <a name="v3-ActCode-CREACT"> </a> </td> <td> common reaction alert</td> <td> Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product. <br/> Example:There is no record of a specific sensitivity for the patient, but the presence of the sensitivity is common and therefore caution is warranted. <br/> </td> </tr> <tr> <td> 7</td> <td>             GEN <a name="v3-ActCode-GEN"> </a> </td> <td> Genetic Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to patient genetic indicators. <br/> </td> </tr> <tr> <td> 7</td> <td>             GEND <a name="v3-ActCode-GEND"> </a> </td> <td> Gender Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to patient gender. <br/> </td> </tr> <tr> <td> 7</td> <td>             LAB <a name="v3-ActCode-LAB"> </a> </td> <td> Lab Alert</td> <td> Proposed therapy may be inappropriate or contraindicated due to recent lab test results <br/> </td> </tr> <tr> <td> 7</td> <td>             REACT <a name="v3-ActCode-REACT"> </a> </td> <td> Reaction Alert</td> <td> Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product <br/> </td> </tr> <tr> <td> 8</td> <td>               ALGY <a name="v3-ActCode-ALGY"> </a> </td> <td> Allergy Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to the proposed product. (Allergies are immune based reactions.) <br/> </td> </tr> <tr> <td> 8</td> <td>               INT <a name="v3-ActCode-INT"> </a> </td> <td> Intolerance Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to the proposed product. (Intolerances are non-immune based sensitivities.) <br/> </td> </tr> <tr> <td> 7</td> <td>             RREACT <a name="v3-ActCode-RREACT"> </a> </td> <td> Related Reaction Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product. <br/> </td> </tr> <tr> <td> 8</td> <td>               RALG <a name="v3-ActCode-RALG"> </a> </td> <td> Related Allergy Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to a cross-sensitivity related product. (Allergies are immune based reactions.) <br/> </td> </tr> <tr> <td> 8</td> <td>               RAR <a name="v3-ActCode-RAR"> </a> </td> <td> Related Prior Reaction Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a recorded prior adverse reaction to a cross-sensitivity related product. <br/> </td> </tr> <tr> <td> 8</td> <td>               RINT <a name="v3-ActCode-RINT"> </a> </td> <td> Related Intolerance Alert</td> <td> Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to a cross-sensitivity related product. (Intolerances are non-immune based sensitivities.) <br/> </td> </tr> <tr> <td> 6</td> <td>           BUS <a name="v3-ActCode-BUS"> </a> </td> <td> business constraint violation</td> <td> Description:A local business rule relating multiple elements has been violated. <br/> </td> </tr> <tr> <td> 6</td> <td>           CODE_INVAL <a name="v3-ActCode-CODE_INVAL"> </a> </td> <td> code is not valid</td> <td> Description:The specified code is not valid against the list of codes allowed for the element. <br/> </td> </tr> <tr> <td> 7</td> <td>             CODE_DEPREC <a name="v3-ActCode-CODE_DEPREC"> </a> </td> <td> code has been deprecated</td> <td> Description:The specified code has been deprecated and should no longer be used. Select another code from the code system. <br/> </td> </tr> <tr> <td> 6</td> <td>           FORMAT <a name="v3-ActCode-FORMAT"> </a> </td> <td> invalid format</td> <td> Description:The element does not follow the formatting or type rules defined for the field. <br/> </td> </tr> <tr> <td> 6</td> <td>           ILLEGAL <a name="v3-ActCode-ILLEGAL"> </a> </td> <td> illegal</td> <td> Description:The request is missing elements or contains elements which cause it to not meet the legal standards for actioning. <br/> </td> </tr> <tr> <td> 6</td> <td>           LEN_RANGE <a name="v3-ActCode-LEN_RANGE"> </a> </td> <td> length out of range</td> <td> Description:The length of the data specified falls out of the range defined for the element. <br/> </td> </tr> <tr> <td> 7</td> <td>             LEN_LONG <a name="v3-ActCode-LEN_LONG"> </a> </td> <td> length is too long</td> <td> Description:The length of the data specified is greater than the maximum length defined for the element. <br/> </td> </tr> <tr> <td> 7</td> <td>             LEN_SHORT <a name="v3-ActCode-LEN_SHORT"> </a> </td> <td> length is too short</td> <td> Description:The length of the data specified is less than the minimum length defined for the element. <br/> </td> </tr> <tr> <td> 6</td> <td>           MISSCOND <a name="v3-ActCode-MISSCOND"> </a> </td> <td> conditional element missing</td> <td> Description:The specified element must be specified with a non-null value under certain conditions. In this case, the conditions are true but the element is still missing or null. <br/> </td> </tr> <tr> <td> 6</td> <td>           MISSMAND <a name="v3-ActCode-MISSMAND"> </a> </td> <td> mandatory element missing</td> <td> Description:The specified element is mandatory and was not included in the instance. <br/> </td> </tr> <tr> <td> 6</td> <td>           NODUPS <a name="v3-ActCode-NODUPS"> </a> </td> <td> duplicate values are not permitted</td> <td> Description:More than one element with the same value exists in the set. Duplicates not permission in this set in a set. <br/> </td> </tr> <tr> <td> 6</td> <td>           NOPERSIST <a name="v3-ActCode-NOPERSIST"> </a> </td> <td> element will not be persisted</td> <td> Description: Element in submitted message will not persist in data storage based on detected issue. <br/> </td> </tr> <tr> <td> 6</td> <td>           REP_RANGE <a name="v3-ActCode-REP_RANGE"> </a> </td> <td> repetitions out of range</td> <td> Description:The number of repeating elements falls outside the range of the allowed number of repetitions. <br/> </td> </tr> <tr> <td> 7</td> <td>             MAXOCCURS <a name="v3-ActCode-MAXOCCURS"> </a> </td> <td> repetitions above maximum</td> <td> Description:The number of repeating elements is above the maximum number of repetitions allowed. <br/> </td> </tr> <tr> <td> 7</td> <td>             MINOCCURS <a name="v3-ActCode-MINOCCURS"> </a> </td> <td> repetitions below minimum</td> <td> Description:The number of repeating elements is below the minimum number of repetitions allowed. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_ActAdministrativeRuleDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActAdministrativeRuleDetectedIssueCode"> </a> </td> <td/> </tr> <tr> <td> 5</td> <td>         <a href="#KEY204">KEY204</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td>         <a href="#KEY205">KEY205</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td>         KEY206 <a name="v3-ActCode-KEY206"> </a> </td> <td> non-matching identification</td> <td> Description: Metadata associated with the identification (e.g. name or gender) does not match the identification being verified. <br/> </td> </tr> <tr> <td> 5</td> <td>         OBSOLETE <a name="v3-ActCode-OBSOLETE"> </a> </td> <td> obsolete record returned</td> <td> Description: One or more records in the query response have a status of 'obsolete'. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (_ActSuppliedItemDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActSuppliedItemDetectedIssueCode"> </a> </td> <td> Identifies types of detected issues regarding the administration or supply of an item to a patient. <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_AdministrationDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_AdministrationDetectedIssueCode"> </a> </td> <td> Administration of the proposed therapy may be inappropriate or contraindicated as proposed <br/> </td> </tr> <tr> <td> 5</td> <td>         <span style="color: grey"> <i> (_AppropriatenessDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_AppropriatenessDetectedIssueCode"> </a> </td> <td/> </tr> <tr> <td> 6</td> <td>           <span style="color: grey"> <i> (_InteractionDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_InteractionDetectedIssueCode"> </a> </td> <td/> </tr> <tr> <td> 7</td> <td>             FOOD <a name="v3-ActCode-FOOD"> </a> </td> <td> Food Interaction Alert</td> <td> Proposed therapy may interact with certain foods <br/> </td> </tr> <tr> <td> 7</td> <td>             TPROD <a name="v3-ActCode-TPROD"> </a> </td> <td> Therapeutic Product Alert</td> <td> Proposed therapy may interact with an existing or recent therapeutic product <br/> </td> </tr> <tr> <td> 8</td> <td>               DRG <a name="v3-ActCode-DRG"> </a> </td> <td> Drug Interaction Alert</td> <td> Proposed therapy may interact with an existing or recent drug therapy <br/> </td> </tr> <tr> <td> 8</td> <td>               NHP <a name="v3-ActCode-NHP"> </a> </td> <td> Natural Health Product Alert</td> <td> Proposed therapy may interact with existing or recent natural health product therapy <br/> </td> </tr> <tr> <td> 8</td> <td>               NONRX <a name="v3-ActCode-NONRX"> </a> </td> <td> Non-Prescription Interaction Alert</td> <td> Proposed therapy may interact with a non-prescription drug (e.g. alcohol, tobacco, Aspirin) <br/> </td> </tr> <tr> <td> 6</td> <td>           <a href="#OBSA">OBSA</a> </td> <td/> <td/> </tr> <tr> <td> 6</td> <td>           PREVINEF <a name="v3-ActCode-PREVINEF"> </a> </td> <td> previously ineffective</td> <td> Definition:The same or similar treatment has previously been attempted with the patient without achieving a positive effect. <br/> </td> </tr> <tr> <td> 5</td> <td>         <a href="#COMPLY">COMPLY</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td>         DACT <a name="v3-ActCode-DACT"> </a> </td> <td> drug action detected issue</td> <td> Description:Proposed therapy may be contraindicated or ineffective based on an existing or recent drug therapy. <br/> </td> </tr> <tr> <td> 5</td> <td>         <a href="#DOSE">DOSE</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td>         <a href="#DUPTHPY">DUPTHPY</a> </td> <td/> <td/> </tr> <tr> <td> 5</td> <td>         TIME <a name="v3-ActCode-TIME"> </a> </td> <td> timing detected issue</td> <td> Description:Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. <br/> </td> </tr> <tr> <td> 6</td> <td>           ALRTENDLATE <a name="v3-ActCode-ALRTENDLATE"> </a> </td> <td> end too late alert</td> <td> Definition:Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy. <br/> </td> </tr> <tr> <td> 6</td> <td>           ALRTSTRTLATE <a name="v3-ActCode-ALRTSTRTLATE"> </a> </td> <td> start too late alert</td> <td> Definition:Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition. <br/> </td> </tr> <tr> <td> 5</td> <td>         <span style="color: grey"> <i> (_TimingDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_TimingDetectedIssueCode"> </a> </td> <td> Proposed therapy may be inappropriate or ineffective based on the proposed start or end time. <br/> </td> </tr> <tr> <td> 6</td> <td>           ENDLATE <a name="v3-ActCode-ENDLATE"> </a> </td> <td> End Too Late Alert</td> <td> Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy <br/> </td> </tr> <tr> <td> 6</td> <td>           STRTLATE <a name="v3-ActCode-STRTLATE"> </a> </td> <td> Start Too Late Alert</td> <td> Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition <br/> </td> </tr> <tr> <td> 4</td> <td>       <span style="color: grey"> <i> (_SupplyDetectedIssueCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_SupplyDetectedIssueCode"> </a> </td> <td> Supplying the product at this time may be inappropriate or indicate compliance issues with the associated therapy <br/> </td> </tr> <tr> <td> 5</td> <td>         ALLDONE <a name="v3-ActCode-ALLDONE"> </a> </td> <td> already performed</td> <td> Definition:The requested action has already been performed and so this request has no effect <br/> </td> </tr> <tr> <td> 5</td> <td>         FULFIL <a name="v3-ActCode-FULFIL"> </a> </td> <td> fulfillment alert</td> <td> Definition:The therapy being performed is in some way out of alignment with the requested therapy. <br/> </td> </tr> <tr> <td> 6</td> <td>           NOTACTN <a name="v3-ActCode-NOTACTN"> </a> </td> <td> no longer actionable</td> <td> Definition:The status of the request being fulfilled has changed such that it is no longer actionable. This may be because the request has expired, has already been completely fulfilled or has been otherwise stopped or disabled. (Not used for 'suspended' orders.) <br/> </td> </tr> <tr> <td> 6</td> <td>           NOTEQUIV <a name="v3-ActCode-NOTEQUIV"> </a> </td> <td> not equivalent alert</td> <td> Definition:The therapy being performed is not sufficiently equivalent to the therapy which was requested. <br/> </td> </tr> <tr> <td> 7</td> <td>             NOTEQUIVGEN <a name="v3-ActCode-NOTEQUIVGEN"> </a> </td> <td> not generically equivalent alert</td> <td> Definition:The therapy being performed is not generically equivalent (having the identical biological action) to the therapy which was requested. <br/> </td> </tr> <tr> <td> 7</td> <td>             NOTEQUIVTHER <a name="v3-ActCode-NOTEQUIVTHER"> </a> </td> <td> not therapeutically equivalent alert</td> <td> Definition:The therapy being performed is not therapeutically equivalent (having the same overall patient effect) to the therapy which was requested. <br/> </td> </tr> <tr> <td> 6</td> <td>           TIMING <a name="v3-ActCode-TIMING"> </a> </td> <td> event timing incorrect alert</td> <td> Definition:The therapy is being performed at a time which diverges from the time the therapy was requested <br/> </td> </tr> <tr> <td> 7</td> <td>             INTERVAL <a name="v3-ActCode-INTERVAL"> </a> </td> <td> outside requested time</td> <td> Definition:The therapy action is being performed outside the bounds of the time period requested <br/> </td> </tr> <tr> <td> 7</td> <td>             MINFREQ <a name="v3-ActCode-MINFREQ"> </a> </td> <td> too soon within frequency based on the usage</td> <td> Definition:The therapy action is being performed too soon after the previous occurrence based on the requested frequency <br/> </td> </tr> <tr> <td> 5</td> <td>         HELD <a name="v3-ActCode-HELD"> </a> </td> <td> held/suspended alert</td> <td> Definition:There should be no actions taken in fulfillment of a request that has been held or suspended. <br/> </td> </tr> <tr> <td> 5</td> <td>         TOOLATE <a name="v3-ActCode-TOOLATE"> </a> </td> <td> Refill Too Late Alert</td> <td> The patient is receiving a subsequent fill significantly later than would be expected based on the amount previously supplied and the therapy dosage instructions <br/> </td> </tr> <tr> <td> 5</td> <td>         TOOSOON <a name="v3-ActCode-TOOSOON"> </a> </td> <td> Refill Too Soon Alert</td> <td> The patient is receiving a subsequent fill significantly earlier than would be expected based on the amount previously supplied and the therapy dosage instructions <br/> </td> </tr> <tr> <td> 4</td> <td>       HISTORIC <a name="v3-ActCode-HISTORIC"> </a> </td> <td> record recorded as historical</td> <td> Description: While the record was accepted in the repository, there is a more recent version of a record of this type. <br/> </td> </tr> <tr> <td> 4</td> <td>       PATPREF <a name="v3-ActCode-PATPREF"> </a> </td> <td> violates stated preferences</td> <td> Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. <br/> </td> </tr> <tr> <td> 5</td> <td>         PATPREFALT <a name="v3-ActCode-PATPREFALT"> </a> </td> <td> violates stated preferences, alternate available</td> <td> Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. An alternate therapy meeting those constraints is available. <br/> </td> </tr> <tr> <td> 2</td> <td>   KSUBJ <a name="v3-ActCode-KSUBJ"> </a> </td> <td> knowledge subject</td> <td> Categorization of types of observation that capture the main clinical knowledge subject which may be a medication, a laboratory test, a disease.</td> </tr> <tr> <td> 2</td> <td>   KSUBT <a name="v3-ActCode-KSUBT"> </a> </td> <td> knowledge subtopic</td> <td> Categorization of types of observation that capture a knowledge subtopic which might be treatment, etiology, or prognosis.</td> </tr> <tr> <td> 2</td> <td>   OINT <a name="v3-ActCode-OINT"> </a> </td> <td> intolerance</td> <td> Hypersensitivity resulting in an adverse reaction upon exposure to an agent. <br/> </td> </tr> <tr> <td> 3</td> <td>     ALG <a name="v3-ActCode-ALG"> </a> </td> <td> Allergy</td> <td> Hypersensitivity to an agent caused by an immunologic response to an initial exposure <br/> </td> </tr> <tr> <td> 4</td> <td>       DALG <a name="v3-ActCode-DALG"> </a> </td> <td> Drug Allergy</td> <td> An allergy to a pharmaceutical product. <br/> </td> </tr> <tr> <td> 4</td> <td>       EALG <a name="v3-ActCode-EALG"> </a> </td> <td> Environmental Allergy</td> <td> An allergy to a substance other than a drug or a food. E.g. Latex, pollen, etc. <br/> </td> </tr> <tr> <td> 4</td> <td>       FALG <a name="v3-ActCode-FALG"> </a> </td> <td> Food Allergy</td> <td> An allergy to a substance generally consumed for nutritional purposes. <br/> </td> </tr> <tr> <td> 3</td> <td>     DINT <a name="v3-ActCode-DINT"> </a> </td> <td> Drug Intolerance</td> <td> Hypersensitivity resulting in an adverse reaction upon exposure to a drug. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#DALG">DALG</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       DNAINT <a name="v3-ActCode-DNAINT"> </a> </td> <td> Drug Non-Allergy Intolerance</td> <td> Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure <br/> </td> </tr> <tr> <td> 3</td> <td>     EINT <a name="v3-ActCode-EINT"> </a> </td> <td> Environmental Intolerance</td> <td> Hypersensitivity resulting in an adverse reaction upon exposure to environmental conditions. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#EALG">EALG</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       ENAINT <a name="v3-ActCode-ENAINT"> </a> </td> <td> Environmental Non-Allergy Intolerance</td> <td> Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure <br/> </td> </tr> <tr> <td> 3</td> <td>     FINT <a name="v3-ActCode-FINT"> </a> </td> <td> Food Intolerance</td> <td> Hypersensitivity resulting in an adverse reaction upon exposure to food. <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#FALG">FALG</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       FNAINT <a name="v3-ActCode-FNAINT"> </a> </td> <td> Food Non-Allergy Intolerance</td> <td> Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure <br/> </td> </tr> <tr> <td> 3</td> <td>     NAINT <a name="v3-ActCode-NAINT"> </a> </td> <td> Non-Allergy Intolerance</td> <td> Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure <br/> </td> </tr> <tr> <td> 4</td> <td>       <a href="#DNAINT">DNAINT</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#ENAINT">ENAINT</a> </td> <td/> <td/> </tr> <tr> <td> 4</td> <td>       <a href="#FNAINT">FNAINT</a> </td> <td/> <td/> </tr> <tr> <td> 2</td> <td>   SEV <a name="v3-ActCode-SEV"> </a> </td> <td> Severity Observation</td> <td> A subjective evaluation of the seriousness or intensity associated with another observation. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_FDALabelData)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_FDALabelData"> </a> </td> <td> FDA label data <br/> </td> </tr> <tr> <td> 3</td> <td>     FDACOATING <a name="v3-ActCode-FDACOATING"> </a> </td> <td> coating</td> <td> FDA label coating <br/> </td> </tr> <tr> <td> 3</td> <td>     FDACOLOR <a name="v3-ActCode-FDACOLOR"> </a> </td> <td> color</td> <td> FDA label color <br/> </td> </tr> <tr> <td> 3</td> <td>     FDAIMPRINTCD <a name="v3-ActCode-FDAIMPRINTCD"> </a> </td> <td> imprint code</td> <td> FDA label imprint code <br/> </td> </tr> <tr> <td> 3</td> <td>     FDALOGO <a name="v3-ActCode-FDALOGO"> </a> </td> <td> logo</td> <td> FDA label logo <br/> </td> </tr> <tr> <td> 3</td> <td>     FDASCORING <a name="v3-ActCode-FDASCORING"> </a> </td> <td> scoring</td> <td> FDA label scoring <br/> </td> </tr> <tr> <td> 3</td> <td>     FDASHAPE <a name="v3-ActCode-FDASHAPE"> </a> </td> <td> shape</td> <td> FDA label shape <br/> </td> </tr> <tr> <td> 3</td> <td>     FDASIZE <a name="v3-ActCode-FDASIZE"> </a> </td> <td> size</td> <td> FDA label size <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ROIOverlayShape)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ROIOverlayShape"> </a> </td> <td> Shape of the region on the object being referenced <br/> </td> </tr> <tr> <td> 2</td> <td>   CIRCLE <a name="v3-ActCode-CIRCLE"> </a> </td> <td> circle</td> <td> A circle defined by two (column,row) pairs. The first point is the center of the circle and the second point is a point on the perimeter of the circle. <br/> </td> </tr> <tr> <td> 2</td> <td>   ELLIPSE <a name="v3-ActCode-ELLIPSE"> </a> </td> <td> ellipse</td> <td> An ellipse defined by four (column,row) pairs, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis. <br/> </td> </tr> <tr> <td> 2</td> <td>   POINT <a name="v3-ActCode-POINT"> </a> </td> <td> point</td> <td> A single point denoted by a single (column,row) pair, or multiple points each denoted by a (column,row) pair. <br/> </td> </tr> <tr> <td> 2</td> <td>   POLY <a name="v3-ActCode-POLY"> </a> </td> <td> polyline</td> <td> A series of connected line segments with ordered vertices denoted by (column,row) pairs; if the first and last vertices are the same, it is a closed polygon. <br/> </td> </tr> <tr> <td> 1</td> <td> C <a name="v3-ActCode-C"> </a> </td> <td> corrected</td> <td> Description:Indicates that result data has been corrected. <br/> </td> </tr> <tr> <td> 1</td> <td> DIET <a name="v3-ActCode-DIET"> </a> </td> <td> Diet</td> <td> Code set to define specialized/allowed diets <br/> </td> </tr> <tr> <td> 2</td> <td>   BR <a name="v3-ActCode-BR"> </a> </td> <td> breikost (GE)</td> <td> A diet exclusively composed of oatmeal, semolina, or rice, to be extremely easy to eat and digest. <br/> </td> </tr> <tr> <td> 2</td> <td>   DM <a name="v3-ActCode-DM"> </a> </td> <td> diabetes mellitus diet</td> <td> A diet that uses carbohydrates sparingly. Typically with a restriction in daily energy content (e.g. 1600-2000 kcal). <br/> </td> </tr> <tr> <td> 2</td> <td>   FAST <a name="v3-ActCode-FAST"> </a> </td> <td> fasting</td> <td> No enteral intake of foot or liquids whatsoever, no smoking. Typically 6 to 8 hours before anesthesia. <br/> </td> </tr> <tr> <td> 2</td> <td>   FORMULA <a name="v3-ActCode-FORMULA"> </a> </td> <td> formula diet</td> <td> A diet consisting of a formula feeding, either for an infant or an adult, to provide nutrition either orally or through the gastrointestinal tract via tube, catheter or stoma. <br/> </td> </tr> <tr> <td> 2</td> <td>   GF <a name="v3-ActCode-GF"> </a> </td> <td> gluten free</td> <td> Gluten free diet for celiac disease. <br/> </td> </tr> <tr> <td> 2</td> <td>   LF <a name="v3-ActCode-LF"> </a> </td> <td> low fat</td> <td> A diet low in fat, particularly to patients with hepatic diseases. <br/> </td> </tr> <tr> <td> 2</td> <td>   LP <a name="v3-ActCode-LP"> </a> </td> <td> low protein</td> <td> A low protein diet for patients with renal failure. <br/> </td> </tr> <tr> <td> 2</td> <td>   LQ <a name="v3-ActCode-LQ"> </a> </td> <td> liquid</td> <td> A strictly liquid diet, that can be fully absorbed in the intestine, and therefore may not contain fiber. Used before enteral surgeries. <br/> </td> </tr> <tr> <td> 2</td> <td>   LS <a name="v3-ActCode-LS"> </a> </td> <td> low sodium</td> <td> A diet low in sodium for patients with congestive heart failure and/or renal failure. <br/> </td> </tr> <tr> <td> 2</td> <td>   N <a name="v3-ActCode-N"> </a> </td> <td> normal diet</td> <td> A normal diet, i.e. no special preparations or restrictions for medical reasons. This is notwithstanding any preferences the patient might have regarding special foods, such as vegetarian, kosher, etc. <br/> </td> </tr> <tr> <td> 2</td> <td>   NF <a name="v3-ActCode-NF"> </a> </td> <td> no fat</td> <td> A no fat diet for acute hepatic diseases. <br/> </td> </tr> <tr> <td> 2</td> <td>   PAF <a name="v3-ActCode-PAF"> </a> </td> <td> phenylalanine free</td> <td> Phenylketonuria diet. <br/> </td> </tr> <tr> <td> 2</td> <td>   PAR <a name="v3-ActCode-PAR"> </a> </td> <td> parenteral</td> <td> Patient is supplied with parenteral nutrition, typically described in terms of i.v. medications. <br/> </td> </tr> <tr> <td> 2</td> <td>   RD <a name="v3-ActCode-RD"> </a> </td> <td> reduction diet</td> <td> A diet that seeks to reduce body fat, typically low energy content (800-1600 kcal). <br/> </td> </tr> <tr> <td> 2</td> <td>   SCH <a name="v3-ActCode-SCH"> </a> </td> <td> schonkost (GE)</td> <td> A diet that avoids ingredients that might cause digestion problems, e.g., avoid excessive fat, avoid too much fiber (cabbage, peas, beans). <br/> </td> </tr> <tr> <td> 2</td> <td>   SUPPLEMENT <a name="v3-ActCode-SUPPLEMENT"> </a> </td> <td> nutritional supplement</td> <td> A diet that is not intended to be complete but is added to other diets. <br/> </td> </tr> <tr> <td> 2</td> <td>   T <a name="v3-ActCode-T"> </a> </td> <td> tea only</td> <td> This is not really a diet, since it contains little nutritional value, but is essentially just water. Used before coloscopy examinations. <br/> </td> </tr> <tr> <td> 2</td> <td>   VLI <a name="v3-ActCode-VLI"> </a> </td> <td> low valin, leucin, isoleucin</td> <td> Diet with low content of the amino-acids valin, leucin, and isoleucin, for "maple syrup disease." <br/> </td> </tr> <tr> <td> 1</td> <td> DRUGPRG <a name="v3-ActCode-DRUGPRG"> </a> </td> <td> drug program</td> <td> Definition: A public or government health program that administers and funds coverage for prescription drugs to assist program eligible who meet financial and health status criteria. <br/> </td> </tr> <tr> <td> 1</td> <td> F <a name="v3-ActCode-F"> </a> </td> <td> final</td> <td> Description:Indicates that a result is complete. No further results are to come. This maps to the 'complete' state in the observation result status code. <br/> </td> </tr> <tr> <td> 1</td> <td> PRLMN <a name="v3-ActCode-PRLMN"> </a> </td> <td> preliminary</td> <td> Description:Indicates that a result is incomplete. There are further results to come. This maps to the 'active' state in the observation result status code. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (SECOBS)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-SECOBS"> </a> </td> <td> An observation identifying security metadata about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used to name security labels. <br/> Rationale: According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator's clearance to the target's security label. All of the following must be true for authorization to be granted: <br/> The security policy identifiers shall be identical The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and For each security category in the target label, there shall be a security category of the same type in the initiator's clearance and the initiator's classification level shall dominate that of the target. Examples: SecurityObservationType security label fields include: <br/> Confidentiality classification Compartment category Sensitivity category Security mechanisms used to ensure data integrity or to perform authorized data transformation Indicators of an IT resource completeness, veracity, reliability, trustworthiness, or provenance. Usage Note: SecurityObservationType codes designate security label field types, which are valued with an applicable SecurityObservationValue code as the "security label tag". <br/> </td> </tr> <tr> <td> 2</td> <td>   SECCATOBS <a name="v3-ActCode-SECCATOBS"> </a> </td> <td> security category observation</td> <td> Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone." <br/> Rationale: A security category observation supports requirement to specify the type of IT resource to facilitate application of appropriate levels of information security according to a range of levels of impact or consequences that might result from the unauthorized disclosure, modification, or use of the information or information system. A resource is assigned to a specific category of information (e.g., privacy, medical, proprietary, financial, investigative, contractor sensitive, security management) defined by an organization or in some instances, by a specific law, Executive Order, directive, policy, or regulation. [FIPS 199] <br/> Examples: Types of security categories include: <br/> Compartment: A division of data into isolated blocks with separate security controls for the purpose of reducing risk. (ISO 2382-8). A security label tag that "segments" an IT resource by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Classification System) Sensitivity: The characteristic of an IT resource which implies its value or importance and may include its vulnerability. (ISO 7492-2) Privacy metadata for information perceived as undesirable to share. (HL7 Healthcare Classification System) </td> </tr> <tr> <td> 2</td> <td>   SECCLASSOBS <a name="v3-ActCode-SECCLASSOBS"> </a> </td> <td> security classification observation</td> <td> Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure. <br/> Rationale: A security classification observation may indicate that the confidentiality level indicated by an Act or Role confidentiality attribute has been overridden by the entity responsible for ascribing the SecurityClassificationObservationValue. This supports the business requirement for increasing or decreasing the level of confidentiality (classification or declassification) based on parameters beyond the original assignment of an Act or Role confidentiality. <br/> Examples: Types of security classification include: HL7 Confidentiality Codes such as very restricted, unrestricted, and normal. Intelligence community examples include top secret, secret, and confidential. <br/> Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObse rvationValue code as the "security label tag". <br/> </td> </tr> <tr> <td> 2</td> <td>   SECCONOBS <a name="v3-ActCode-SECCONOBS"> </a> </td> <td> security control observation</td> <td> Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource. <br/> Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199] <br/> Examples: Types of security control metadata include: <br/> handling caveats dissemination controls obligations refrain policies purpose of use constraints </td> </tr> <tr> <td> 2</td> <td>   SECINTOBS <a name="v3-ActCode-SECINTOBS"> </a> </td> <td> security integrity observation</td> <td> Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. <br/> Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542) <br/> Examples: Types of security integrity metadata include: <br/> Integrity status, which indicates the completeness or workflow status of an IT resource (data, information object, service, or system capability) Integrity confidence, which indicates the reliability and trustworthiness of an IT resource Integrity control, which indicates pertinent handling caveats, obligations, refrain policies, and purpose of use for the resource Data integrity, which indicate the security mechanisms used to ensure that the accuracy and consistency are preserved regardless of changes made (ISO/IEC DIS 2382-8) Alteration integrity, which indicate the security mechanisms used for authorized transformations of the resource Integrity provenance, which indicates the entity responsible for a report or assertion relayed "second-hand" about an IT resource </td> </tr> <tr> <td> 3</td> <td>     SECALTINTOBS <a name="v3-ActCode-SECALTINTOBS"> </a> </td> <td> security alteration integrity observation</td> <td> Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource. <br/> Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including: <br/> translation syntactic transformation semantic mapping redaction masking pseudonymization anonymization </td> </tr> <tr> <td> 3</td> <td>     SECDATINTOBS <a name="v3-ActCode-SECDATINTOBS"> </a> </td> <td> security data integrity observation</td> <td> Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made." <br/> Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature. <br/> </td> </tr> <tr> <td> 3</td> <td>     SECINTCONOBS <a name="v3-ActCode-SECINTCONOBS"> </a> </td> <td> security integrity confidence observation</td> <td> Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. <br/> Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable. <br/> Usage Note: A security integrity confidence observation on an Act may indicate that a valued Act.uncertaintycode attribute has been overridden by the entity responsible for ascribing the SecurityIntegrityConfidenceObservationValue. This supports the business requirements for increasing or decreasing the assessment of the reliability or trustworthiness of an IT resource based on parameters beyond the original assignment of an Act statement level of uncertainty. <br/> </td> </tr> <tr> <td> 3</td> <td>     <span style="color: grey"> <i> (SECINTPRVOBS)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-SECINTPRVOBS"> </a> </td> <td> Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness of an IT resource in terms of workflow status such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness. <br/> Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: <br/> completeness or workflow status, such as authentication the entity responsible for original authoring or informing about an IT resource the entity responsible for a report or assertion about an IT resource relayed “second-handâ€? the entity responsible for excerpting, transforming, or compiling an IT resource </td> </tr> <tr> <td> 4</td> <td>       SECINTPRVABOBS <a name="v3-ActCode-SECINTPRVABOBS"> </a> </td> <td> security integrity provenance asserted by observation</td> <td> Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource. <br/> Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: <br/> assertions about an IT resource by a patient assertions about an IT resource by a clinician assertions about an IT resource by a device </td> </tr> <tr> <td> 4</td> <td>       SECINTPRVRBOBS <a name="v3-ActCode-SECINTPRVRBOBS"> </a> </td> <td> security integrity provenance reported by observation</td> <td> Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource. <br/> Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: <br/> reports about an IT resource by a patient reports about an IT resource by a clinician reports about an IT resource by a device </td> </tr> <tr> <td> 3</td> <td>     SECINTSTOBS <a name="v3-ActCode-SECINTSTOBS"> </a> </td> <td> security integrity status observation</td> <td> Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource. <br/> Examples: Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion code system such as legally authenticated, in progress, and incomplete. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (SECTRSTOBS)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-SECTRSTOBS"> </a> </td> <td> An observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a trust attribute to populate a computable trust policy, trust credential, trust assertion, or trust label field in a security label or trust policy, which are principally used for authentication, authorization, and access control decisions. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTACCRDOBS <a name="v3-ActCode-TRSTACCRDOBS"> </a> </td> <td> trust accreditation observation</td> <td> Type of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTAGREOBS <a name="v3-ActCode-TRSTAGREOBS"> </a> </td> <td> trust agreement observation</td> <td> Type of security metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1] <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTCERTOBS <a name="v3-ActCode-TRSTCERTOBS"> </a> </td> <td> trust certificate observation</td> <td> Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1] <br/> For example, <br/> A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants. A Certificate Practice Statement (CSP), which is a statement of the practices which an Authority employs in issuing and managing certificates. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.] </td> </tr> <tr> <td> 3</td> <td>     TRSTFWKOBS <a name="v3-ActCode-TRSTFWKOBS"> </a> </td> <td> trust framework observation</td> <td> Type of security metadata observation made about a complete set of contracts, regulations or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative] <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTLOAOBS <a name="v3-ActCode-TRSTLOAOBS"> </a> </td> <td> trust assurance observation</td> <td> Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol. <br/> </td> </tr> <tr> <td> 3</td> <td>     TRSTMECOBS <a name="v3-ActCode-TRSTMECOBS"> </a> </td> <td> trust mechanism observation</td> <td> Type of security metadata observation made about a security architecture system component that supports enforcement of security policies. <br/> </td> </tr> <tr> <td> 1</td> <td> SUBSIDFFS <a name="v3-ActCode-SUBSIDFFS"> </a> </td> <td> subsidized fee for service program</td> <td> Definition: A government health program that provides coverage on a fee for service basis for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. <br/> Discussion: The structure and business processes for underwriting and administering a subsidized fee for service program is further specified by the Underwriter and Payer Role.class and Role.code. <br/> </td> </tr> <tr> <td> 1</td> <td> WRKCOMP <a name="v3-ActCode-WRKCOMP"> </a> </td> <td> (workers compensation program</td> <td> Definition: Government mandated program providing coverage, disability income, and vocational rehabilitation for injuries sustained in the work place or in the course of employment. Employers may either self-fund the program, purchase commercial coverage, or pay a premium to a government entity that administers the program. Employees may be required to pay premiums toward the cost of coverage as well. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_ActProcedureCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActProcedureCode"> </a> </td> <td> An identifying code for healthcare interventions/procedures. <br/> </td> </tr> <tr> <td> 2</td> <td>   <span style="color: grey"> <i> (_ActBillableServiceCode)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_ActBillableServiceCode"> </a> </td> <td> Definition: An identifying code for billable services, as opposed to codes for similar services used to identify them for functional purposes. <br/> </td> </tr> <tr> <td> 1</td> <td> <span style="color: grey"> <i> (_HL7DefinedActCodes)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActCode-_HL7DefinedActCodes"> </a> </td> <td> Domain provides the root for HL7-defined detailed or rich codes for the Act classes. <br/> </td> </tr> <tr> <td> 1</td> <td> COPAY <a name="v3-ActCode-COPAY"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DEDUCT <a name="v3-ActCode-DEDUCT"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DOSEIND <a name="v3-ActCode-DOSEIND"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> PRA <a name="v3-ActCode-PRA"> </a> </td> <td/> <td/> </tr> <tr style="background: #EFEFEF"> <td> 1</td> <td> STORE <a name="v3-ActCode-STORE"> </a> <b> <i> Deprecated</i> </b> </td> <td> Storage</td> <td> The act of putting something away for safe keeping. The "something" ; may be physical object such as a specimen, or information, such as observations regarding a specimen. <br/> </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-ActCode"/> <version value="2019-07-31"/> <name value="v3.ActCode"/> <title value="v3 Code System ActCode"/> <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 code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted."/> <immutable value="true"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> </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.2.0 (GitHub f996518d66) generated on Tue, Dec 31, 2019 21:19+1100.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change