Release 4 5 Preview #2
This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

4.4.1.193 4.4.1.207 Value Set http://hl7.org/fhir/ValueSet/provenance-activity-type

Security Work Group   Maturity Level : 3 Trial Use Use Context : Any

This is a value set defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/ValueSet/provenance-activity-type
Version: 4.0.1 4.4.0
Name: ProvenanceActivityType
Title: Provenance activity type ProvenanceActivityType
Definition:

This value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes.

Committee: Security Work Group
OID: 2.16.840.1.113883.4.642.3.438 (for OID based terminology systems)
Copyright:

This is a value set of representative Activity Type codes.

Source Resource XML / JSON

This value set is used in the following places:


This value set includes codes from based on the following code systems: rules:

 

This expansion generated 07 Aug 2020


This value set contains 1155 concepts

Include these codes http://terminology.hl7.org/CodeSystem/v3-ActCode Display ANONY DEID PSEUD Include these codes http://terminology.hl7.org/CodeSystem/v3-DataOperation Display Include all codes defined http://terminology.hl7.org/CodeSystem/v3-ParticipationType System Display Definition
Code System Display Definition
1 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Origination / Creation LA
2 legally authenticated http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle A completion status in which Import / Copy
3 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Amendment
4 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Verification
5 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Translation
6 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Access / Use
7 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle De-identification
8 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Aggregation / summarization / derivation
9 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Report
10 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Export
11 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Disclosure
12 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Receipt of disclosure
13 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Archiving
14 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Logical deletion
15 http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle Permanent erasure / Physical destruction
access http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Access/View Record Lifecycle Event Occurs when an agent causes the system to obtain and open a document has been signed manually record entry for inspection or electronically by review.
hold http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Add Legal Hold Record Lifecycle Event Occurs when an agent causes the individual who is legally responsible for that document. This is system to tag or otherwise indicate special access management and suspension of record entry deletion/destruction, if deemed relevant to a lawsuit or which are reasonably anticipated to be relevant or to fulfill organizational policy under the most mature state legal doctrine of “duty to preserve”.
amend http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Amend (Update) Record Lifecycle Event Occurs when an agent makes any change to record entry content currently residing in storage considered permanent (persistent).
archive http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Archive Record Lifecycle Event Occurs when an agent causes the workflow progression. system to create and move archive artifacts containing record entry content, typically to long-term offline storage.
attest http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Attest Record Lifecycle Event Occurs when an agent causes the system to capture the agent’s digital signature (or equivalent indication) during formal validation of record entry content.
decrypt http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Decrypt Record Lifecycle Event Occurs when an agent causes the system to decode record entry content from a cipher.
deidentify http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle De-Identify (Anononymize) Record Lifecycle Event Occurs when an agent causes the system to scrub record entry content to reduce the association between a set of identifying data and the data subject in a way that might or might not be reversible.
deprecate http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Deprecate Record Lifecycle Event Occurs when an agent causes the system to tag record entry(ies) as defined obsolete, erroneous or untrustworthy, to warn against its future use.
destroy http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Destroy/Delete Record Lifecycle Event Occurs when an agent causes the system to permanently erase record entry content from the system.
disclose http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Disclose Record Lifecycle Event Occurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content.
encrypt http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Encrypt Record Lifecycle Event Occurs when an agent causes the system to encode record entry content in a cipher.
extract http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Extract Record Lifecycle Event Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.
Code link http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Link Record Lifecycle Event Occurs when an agent causes the system to connect related record entries.
merge http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Merge Record Lifecycle Event Occurs when an agent causes the system to combine or join content from two or more record entries, resulting in a single logical record entry.
originate http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Originate/Retain Record Lifecycle Event Occurs when an agent causes the system to: a) initiate capture of potential record content, and b) incorporate that content into the storage considered a permanent part of the health record.
pseudonymize anonymize http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Custodian Pseudonymize Record Lifecycle Event Occurs when an agent causes the system must to remove any information that could result in record entry content to reduce the association between a set of identifying data and the information subject. data subject in a way that may be reversible.
reactivate http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Re-activate Record Lifecycle Event Occurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated.
receive deidentify http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Custodian Receive/Retain Record Lifecycle Event Occurs when an agent causes the system must strip information to a) initiate capture of data content from elsewhere, and b) incorporate that would allow content into the identification storage considered a permanent part of the source of health record.
reidentify http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Re-identify Record Lifecycle Event Occurs when an agent causes the system to restore information or the to data that allows identification of information source and/or information subject.
MASK unhold mask http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Custodian Remove Legal Hold Record Lifecycle Event Occurs when an agent causes the system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license remove a tag or "shared secret". other cues for special access management had required to fulfill organizational policy under the legal doctrine of “duty to preserve”.
LABEL report assign security label http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Custodian security Report (Output) Record Lifecycle Event Occurs when an agent causes the system must assign to produce and bind security labels deliver record entry content in order a particular form and manner.
restore http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Restore Record Lifecycle Event Occurs when an agent causes the system to classify information recreate record entries and their content from a previous created in archive artefact.
transform http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Transform/Translate Record Lifecycle Event Occurs when an agent causes the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with system to change the target information. The form, language or code system must retain used to represent record entry content.
transmit http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Transmit Record Lifecycle Event Occurs when an immutable agent causes the system to send record of entry content from one (EHR/PHR/other) system to another.
unlink http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Unlink Record Lifecycle Event Occurs when an agent causes the assignment and binding. Usage Note: In security systems, security policy label assignments do system to disconnect two or more record entries previously connected, rendering them separate (disconnected) again.
unmerge http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Unmerge Record Lifecycle Event Occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again.
verify http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle Verify Record Lifecycle Event Occurs when an agent causes the system to confirm compliance of data or data objects with regulations, requirements, specifications, or other imposed conditions based on organizational policy.
preparation http://hl7.org/fhir/event-status Preparation The core event has not change, they started yet, but some staging activities have begun (e.g. surgical suite preparation). Preparation stages may supersede prior assignments, and such reassignments are always be tracked for auditing and other billing purposes.
in-progress http://hl7.org/fhir/event-status In Progress The event is currently occurring.
not-done pseudonymize http://hl7.org/fhir/event-status Custodian system must strip information Not Done The event was terminated prior to any activity beyond preparation. I.e. The 'main' activity has not yet begun. The boundary between preparatory and the 'main' activity is context-specific.
on-hold http://hl7.org/fhir/event-status On Hold The event has been temporarily stopped but is expected to resume in the future.
stopped http://hl7.org/fhir/event-status Stopped The event was terminated prior to the full completion of data the intended activity but after at least some of the 'main' activity (beyond preparation) has occurred.
completed http://hl7.org/fhir/event-status Completed The event has now concluded.
entered-in-error http://hl7.org/fhir/event-status Entered in Error This electronic record should never have existed, though it is possible that would allow real-world decisions were based on it. (If real-world activity has occurred, the identification status should be "stopped" rather than "entered-in-error".).
unknown http://hl7.org/fhir/event-status Unknown The authoring/source system does not know which of the source status values currently applies for this event. Note: This concept is not to be used for "other" - one of the information or listed statuses is presumed to apply, but the information subject. Custodian may retain authoring/source system does not know which.
AU http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion authenticated A completion status in which a key document has been signed manually or electronically by one or more individuals who attest to relink data necessary its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to reidentify have a single instance of authentication, usually by the assigned individual.
DI http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion dictated A completion status in which information subject. has been orally recorded but not yet transcribed.
DO http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion documented A completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as defined voice to text.
IN http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion incomplete A completion status in which information is known to be missing from a transcribed document.
IP http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion in progress A workflow status where the material has been assigned to personnel to perform the task of transcription. The document remains in this state until the document is transcribed.
Code LA http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion legally authenticated A completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression.
NU http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion nullified document A completion status in which a document was created in error or was placed in the wrong chart. The document is no longer available.
PA http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion pre-authenticated A completion status in which a document is transcribed but not authenticated.
UC http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion unsigned completed document A completion status where the document is complete and there is no expectation that the document will be signed.
OPERATE http://terminology.hl7.org/CodeSystem/v3-DataOperation operate Description:Act on an object or objects.
CREATE http://terminology.hl7.org/CodeSystem/v3-DataOperation create Description:Fundamental operation in an Information System (IS) that results only in the act of bringing an object into existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
DELETE http://terminology.hl7.org/CodeSystem/v3-DataOperation delete Description:Fundamental operation in an Information System (IS) that results only in the removal of information about an object from memory or storage. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.
EXECUTE http://terminology.hl7.org/CodeSystem/v3-DataOperation execute Description:Fundamental operation in an IS that results only in initiating performance of a single or set of programs (i.e., software objects). Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.
READ http://terminology.hl7.org/CodeSystem/v3-DataOperation read Description:Fundamental operation in an Information System (IS) that results only in the flow of information about an object to a subject. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.
UPDATE http://terminology.hl7.org/CodeSystem/v3-DataOperation revise Definition:Fundamental operation in an Information System (IS) that results only in the revision or alteration of an object. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.
APPEND http://terminology.hl7.org/CodeSystem/v3-DataOperation append Description:Fundamental operation in an Information System (IS) that results only in the addition of information to an object already in existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.
MODIFYSTATUS http://terminology.hl7.org/CodeSystem/v3-DataOperation modify status Description:Change the status of an object representing an Act.
ABORT http://terminology.hl7.org/CodeSystem/v3-DataOperation abort Description:Change the status of an object representing an Act to "aborted", i.e., terminated prior to the originally intended completion. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
ACTIVATE http://terminology.hl7.org/CodeSystem/v3-DataOperation activate Description:Change the status of an object representing an Act to "active", i.e., so it can be performed or is being performed, for the first time. (Contrast with REACTIVATE.) For an HL7 Act, the state transitions per the HL7 Reference Information Model.
CANCEL http://terminology.hl7.org/CodeSystem/v3-DataOperation cancel Description:Change the status of an object representing an Act to "cancelled", i.e., abandoned before activation. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
COMPLETE http://terminology.hl7.org/CodeSystem/v3-DataOperation complete Description:Change the status of an object representing an Act to "completed", i.e., terminated normally after all of its constituents have been performed. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
HOLD http://terminology.hl7.org/CodeSystem/v3-DataOperation hold Description:Change the status of an object representing an Act to "held", i.e., put aside an Act that is still in preparatory stages. No action can occur until the Act is released. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
JUMP http://terminology.hl7.org/CodeSystem/v3-DataOperation jump Description:Change the status of an object representing an Act to a normal state. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
NULLIFY http://terminology.hl7.org/CodeSystem/v3-DataOperation nullify Description:Change the status of an object representing an Act to "nullified", i.e., treat as though it never existed. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
OBSOLETE http://terminology.hl7.org/CodeSystem/v3-DataOperation obsolete Description:Change the status of an object representing an Act to "obsolete" when it has been replaced by a new instance. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
REACTIVATE http://terminology.hl7.org/CodeSystem/v3-DataOperation reactivate Description:Change the status of a formerly active object representing an Act to "active", i.e., so it can again be performed or is being performed. (Contrast with ACTIVATE.) For an HL7 Act, the state transitions per the HL7 Reference Information Model.
RELEASE http://terminology.hl7.org/CodeSystem/v3-DataOperation release Description:Change the status of an object representing an Act so it is no longer "held", i.e., allow action to occur. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
RESUME http://terminology.hl7.org/CodeSystem/v3-DataOperation resume Description:Change the status of a suspended object representing an Act to "active", i.e., so it can be performed or is being performed. For an HL7 Act, the state transitions per the HL7 Reference Information Model.
SUSPEND http://terminology.hl7.org/CodeSystem/v3-DataOperation suspend Definition:Change the status of an object representing an Act to suspended, i.e., so it is temporarily not in service.
normal   http://terminology.hl7.org/CodeSystem/v3-ActStatus normal Encompasses the expected states of an Act, but excludes "nullified" and "obsolete" which represent unusual terminal states for the life-cycle.
4.4.1.193.2 Expansion aborted http://terminology.hl7.org/CodeSystem/v3-ActStatus aborted The Act has been terminated prior to the originally intended completion.
active http://terminology.hl7.org/CodeSystem/v3-ActStatus active The Act can be performed or is being performed
cancelled http://terminology.hl7.org/CodeSystem/v3-ActStatus cancelled The Act has been abandoned before activation.
completed http://terminology.hl7.org/CodeSystem/v3-ActStatus completed An Act that has terminated normally after all of its constituents have been performed.
held http://terminology.hl7.org/CodeSystem/v3-ActStatus held An Act that is still in the preparatory stages has been put aside. No action can occur until the Act is released.
new http://terminology.hl7.org/CodeSystem/v3-ActStatus new An Act that is in the preparatory stages and may not yet be acted upon
suspended http://terminology.hl7.org/CodeSystem/v3-ActStatus suspended An Act that has been activated (actions could or have been performed against it), but has been temporarily disabled. No further action should be taken against it until it is released
nullified http://terminology.hl7.org/CodeSystem/v3-ActStatus nullified This expansion generated 01 Nov 2019 Act instance was created in error and has been 'removed' and is treated as though it never existed. A record is retained for audit purposes only.
obsolete http://terminology.hl7.org/CodeSystem/v3-ActStatus obsolete This value set contains 70 concepts Expansion based Act instance has been replaced by a new instance.
_ActAccountCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAccountCode 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.
ACCTRECEIVABLE http://terminology.hl7.org/CodeSystem/v3-ActCode account receivable 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.
CASH http://terminology.hl7.org/CodeSystem/v3-ActCode Cash Cash
CC http://terminology.hl7.org/CodeSystem/v3-ActCode credit card Description: Types of advance payment to be made on http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion version 2018-08-12, http://terminology.hl7.org/CodeSystem/v3-DataOperation version 2018-08-12, a plastic card usually issued by a financial institution used of purchasing services and/or products.
AE http://terminology.hl7.org/CodeSystem/v3-ActCode version 2018-08-12, http://terminology.hl7.org/CodeSystem/v3-ParticipationType version 2018-08-12 American Express American Express
DN http://terminology.hl7.org/CodeSystem/v3-ActCode Diner's Club Diner's Club
Code DV http://terminology.hl7.org/CodeSystem/v3-ActCode Discover Card Discover Card
MC http://terminology.hl7.org/CodeSystem/v3-ActCode Master Card Master Card
V http://terminology.hl7.org/CodeSystem/v3-ActCode Visa Visa
PBILLACCT http://terminology.hl7.org/CodeSystem/v3-ActCode patient billing account An account representing charges and credits (financial transactions) for a patient's encounter.
LA _ActAdjudicationCode http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion http://terminology.hl7.org/CodeSystem/v3-ActCode legally authenticated ActAdjudicationCode A completion status in which Includes coded responses that will occur as a document result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results.
_ActAdjudicationGroupCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdjudicationGroupCode Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals).
CONT http://terminology.hl7.org/CodeSystem/v3-ActCode contract Transaction counts and value totals by Contract Identifier.
DAY http://terminology.hl7.org/CodeSystem/v3-ActCode day Transaction counts and value totals for each calendar day within the date range specified.
LOC http://terminology.hl7.org/CodeSystem/v3-ActCode location Transaction counts and value totals by service location (e.g clinic).
MONTH http://terminology.hl7.org/CodeSystem/v3-ActCode month Transaction counts and value totals for each calendar month within the date range specified.
PERIOD http://terminology.hl7.org/CodeSystem/v3-ActCode period Transaction counts and value totals for the date range specified.
PROV http://terminology.hl7.org/CodeSystem/v3-ActCode provider Transaction counts and value totals by Provider Identifier.
WEEK http://terminology.hl7.org/CodeSystem/v3-ActCode week Transaction counts and value totals for each calendar week within the date range specified.
YEAR http://terminology.hl7.org/CodeSystem/v3-ActCode year Transaction counts and value totals for each calendar year within the date range specified.
AA http://terminology.hl7.org/CodeSystem/v3-ActCode adjudicated with adjustments The invoice element has been signed manually accepted for payment but one or electronically by more adjustment(s) have been made to one or more invoice element line items (component charges). Also includes the individual who concept 'Adjudicate as zero' and items not covered under a particular Policy. Invoice element can be reversed (nullified). Recommend that the invoice element is legally responsible saved for DUR (Drug Utilization Reporting).
ANF http://terminology.hl7.org/CodeSystem/v3-ActCode adjudicated with adjustments and no financial impact 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. Invoice element can be reversed (nullified). Recommend that document. This the invoice element is saved for DUR (Drug Utilization Reporting).
AR http://terminology.hl7.org/CodeSystem/v3-ActCode adjudicated as refused The invoice element has passed through the most mature state adjudication process but payment is refused due to one or more reasons. Includes items such as patient not covered, or invoice element is not constructed according to payer rules (e.g. 'invoice submitted too late'). If one invoice element line item in the workflow progression. invoice element structure is rejected, the remaining line items may not be adjudicated and the complete group is treated as rejected. A refused invoice element can be forwarded to the next payer (for Coordination of Benefits) or modified and resubmitted to refusing payer. Invoice element cannot be reversed (nullified) as there is nothing to reverse. Recommend that the invoice element is not saved for DUR (Drug Utilization Reporting).
ANONY AS http://terminology.hl7.org/CodeSystem/v3-ActCode anonymize adjudicated as submitted Custodian system must remove any The invoice element was/will be paid exactly as submitted, without financial adjustment(s). 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". If information items are included in the adjudication results that could do not affect the monetary amounts paid, then this is still Adjudicated as Submitted (e.g. 'reached Plan Maximum on this Claim'). Invoice element can be reversed (nullified). Recommend that the invoice element is saved for DUR (Drug Utilization Reporting).
_ActAdjudicationResultActionCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdjudicationResultActionCode Actions to be carried out by the recipient of the Adjudication Result information.
DISPLAY http://terminology.hl7.org/CodeSystem/v3-ActCode Display The adjudication result in associated is to be displayed to the receiver of the adjudication result.
FORM http://terminology.hl7.org/CodeSystem/v3-ActCode Print on Form The adjudication result associated is to be printed on the specified form, which is then provided to the covered party.
_ActBillableModifierCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActBillableModifierCode Definition:An identifying modifier code for healthcare interventions or procedures.
CPTM http://terminology.hl7.org/CodeSystem/v3-ActCode CPT modifier codes Description:CPT modifier codes are found in Appendix A of CPT 2000 Standard Edition.
HCPCSA http://terminology.hl7.org/CodeSystem/v3-ActCode HCPCS Level II and Carrier-assigned 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 information subject. Medicare Bulletin.
DEID _ActBillingArrangementCode http://terminology.hl7.org/CodeSystem/v3-ActCode deidentify ActBillingArrangementCode Custodian system must strip information The type of data that provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period.
BLK http://terminology.hl7.org/CodeSystem/v3-ActCode block funding 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. This billing arrangement is also known as Program of Care for some specific Payors and Program Fees for other Payors.
CAP http://terminology.hl7.org/CodeSystem/v3-ActCode capitation funding 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).
CONTF http://terminology.hl7.org/CodeSystem/v3-ActCode contract funding 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.
FINBILL http://terminology.hl7.org/CodeSystem/v3-ActCode financial 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.
ROST http://terminology.hl7.org/CodeSystem/v3-ActCode roster funding A billing arrangement where funding is based on a list of individuals registered as patients of the Provider.
SESS http://terminology.hl7.org/CodeSystem/v3-ActCode sessional funding 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.
FFS http://terminology.hl7.org/CodeSystem/v3-ActCode fee for service A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product. 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.
FFPS http://terminology.hl7.org/CodeSystem/v3-ActCode first fill, part fill, partial strength 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)
FFCS http://terminology.hl7.org/CodeSystem/v3-ActCode first fill complete, partial strength 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).
TFS http://terminology.hl7.org/CodeSystem/v3-ActCode trial fill partial strength A fill where a small portion is provided to allow for determination of the identification 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).
_ActBoundedROICode http://terminology.hl7.org/CodeSystem/v3-ActCode ActBoundedROICode Type of bounded ROI.
ROIFS http://terminology.hl7.org/CodeSystem/v3-ActCode fully specified ROI 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 source EKG leads V2, V3, and V4 would include 4 boundaries, one each for time, V2, V3, and V4.
ROIPS http://terminology.hl7.org/CodeSystem/v3-ActCode partially specified ROI A partially specified bounded Region of Interest (ROI) specifies a ROI in which at least all values in the information 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.
_ActCareProvisionCode http://terminology.hl7.org/CodeSystem/v3-ActCode act care provision Description:The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care.
_ActCredentialedCareCode http://terminology.hl7.org/CodeSystem/v3-ActCode act credentialed care 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 information subject. person or organization who participates as performer of the Act. Excludes employment agreements. Example:Hospital license; physician license; clinic accreditation.
MASK _ActCredentialedCareProvisionPersonCode http://terminology.hl7.org/CodeSystem/v3-ActCode mask act credentialed care provision peron Custodian system must render information unreadable Description:The type and unusable scope of legal and/or professional responsibility taken-on by algorithmically transforming plaintext the performer of the Act for a specific subject of care as described by an agency for credentialing individuals.
CACC http://terminology.hl7.org/CodeSystem/v3-ActCode certified anatomic pathology and clinical pathology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CAIC http://terminology.hl7.org/CodeSystem/v3-ActCode certified allergy and immunology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CAMC http://terminology.hl7.org/CodeSystem/v3-ActCode certified aerospace medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CANC http://terminology.hl7.org/CodeSystem/v3-ActCode certified anesthesiology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CAPC http://terminology.hl7.org/CodeSystem/v3-ActCode certified anatomic pathology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CBGC http://terminology.hl7.org/CodeSystem/v3-ActCode certified clinical biochemical genetics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CCCC http://terminology.hl7.org/CodeSystem/v3-ActCode certified clinical cytogenetics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CCGC http://terminology.hl7.org/CodeSystem/v3-ActCode certified clinical genetics (M.D.) care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CCPC http://terminology.hl7.org/CodeSystem/v3-ActCode certified clinical pathology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CCSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified colon and rectal surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CDEC http://terminology.hl7.org/CodeSystem/v3-ActCode certified dermatology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CDRC http://terminology.hl7.org/CodeSystem/v3-ActCode certified diagnostic radiology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CEMC http://terminology.hl7.org/CodeSystem/v3-ActCode certified emergency medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CFPC http://terminology.hl7.org/CodeSystem/v3-ActCode certified family practice care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CIMC http://terminology.hl7.org/CodeSystem/v3-ActCode certified internal medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CMGC http://terminology.hl7.org/CodeSystem/v3-ActCode certified clinical molecular genetics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CNEC http://terminology.hl7.org/CodeSystem/v3-ActCode certified neurology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board
CNMC http://terminology.hl7.org/CodeSystem/v3-ActCode certified nuclear medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CNQC http://terminology.hl7.org/CodeSystem/v3-ActCode certified neurology with special qualifications in child neurology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CNSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified neurological surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
COGC http://terminology.hl7.org/CodeSystem/v3-ActCode certified obstetrics and gynecology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
COMC http://terminology.hl7.org/CodeSystem/v3-ActCode certified occupational medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
COPC http://terminology.hl7.org/CodeSystem/v3-ActCode certified ophthalmology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
COSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified orthopaedic surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
COTC http://terminology.hl7.org/CodeSystem/v3-ActCode certified otolaryngology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPEC http://terminology.hl7.org/CodeSystem/v3-ActCode certified pediatrics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPGC http://terminology.hl7.org/CodeSystem/v3-ActCode certified Ph.D. medical genetics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPHC http://terminology.hl7.org/CodeSystem/v3-ActCode certified public health and general preventive medicine care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPRC http://terminology.hl7.org/CodeSystem/v3-ActCode certified physical medicine and rehabilitation care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified plastic surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CPYC http://terminology.hl7.org/CodeSystem/v3-ActCode certified psychiatry care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CROC http://terminology.hl7.org/CodeSystem/v3-ActCode certified radiation oncology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CRPC http://terminology.hl7.org/CodeSystem/v3-ActCode certified radiological physics care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CSUC http://terminology.hl7.org/CodeSystem/v3-ActCode certified surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CTSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified thoracic surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CURC http://terminology.hl7.org/CodeSystem/v3-ActCode certified urology care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
CVSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified vascular surgery care Description:Scope of responsibility taken on for specialty care as defined by the respective Specialty Board.
LGPC http://terminology.hl7.org/CodeSystem/v3-ActCode licensed general physician care Description:Scope of responsibility taken-on for physician care of a patient as defined by a governmental licensing agency.
_ActCredentialedCareProvisionProgramCode http://terminology.hl7.org/CodeSystem/v3-ActCode act credentialed care provision program 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.
AALC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited assisted living care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
AAMC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited ambulatory care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
ABHC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited behavioral health care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
ACAC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited critical access hospital care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
ACHC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited hospital care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
AHOC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited home care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
ALTC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited long term care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
AOSC http://terminology.hl7.org/CodeSystem/v3-ActCode accredited office-based surgery care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the respective accreditation agency.
CACS http://terminology.hl7.org/CodeSystem/v3-ActCode certified acute coronary syndrome care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CAMI http://terminology.hl7.org/CodeSystem/v3-ActCode certified acute myocardial infarction care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CAST http://terminology.hl7.org/CodeSystem/v3-ActCode certified asthma care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CBAR http://terminology.hl7.org/CodeSystem/v3-ActCode certified bariatric surgery care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CCAD http://terminology.hl7.org/CodeSystem/v3-ActCode certified coronary artery disease care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CCAR http://terminology.hl7.org/CodeSystem/v3-ActCode certified cardiac care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CDEP http://terminology.hl7.org/CodeSystem/v3-ActCode certified depression care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CDGD http://terminology.hl7.org/CodeSystem/v3-ActCode certified digestive/gastrointestinal disorders care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CDIA http://terminology.hl7.org/CodeSystem/v3-ActCode certified diabetes care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CEPI http://terminology.hl7.org/CodeSystem/v3-ActCode certified epilepsy care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CFEL http://terminology.hl7.org/CodeSystem/v3-ActCode certified frail elderly care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CHFC http://terminology.hl7.org/CodeSystem/v3-ActCode certified heart failure care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CHRO http://terminology.hl7.org/CodeSystem/v3-ActCode certified high risk obstetrics care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CHYP http://terminology.hl7.org/CodeSystem/v3-ActCode certified hyperlipidemia care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CMIH http://terminology.hl7.org/CodeSystem/v3-ActCode certified migraine headache care Description:.
CMSC http://terminology.hl7.org/CodeSystem/v3-ActCode certified multiple sclerosis care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
COJR http://terminology.hl7.org/CodeSystem/v3-ActCode certified orthopedic joint replacement care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CONC http://terminology.hl7.org/CodeSystem/v3-ActCode certified oncology care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
COPD http://terminology.hl7.org/CodeSystem/v3-ActCode certified chronic obstructive pulmonary disease care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CORT http://terminology.hl7.org/CodeSystem/v3-ActCode certified organ transplant care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CPAD http://terminology.hl7.org/CodeSystem/v3-ActCode certified parkinsons disease care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CPND http://terminology.hl7.org/CodeSystem/v3-ActCode certified pneumonia disease care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CPST http://terminology.hl7.org/CodeSystem/v3-ActCode certified primary stroke center care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CSDM http://terminology.hl7.org/CodeSystem/v3-ActCode certified stroke disease management care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CSIC http://terminology.hl7.org/CodeSystem/v3-ActCode certified sickle cell care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CSLD http://terminology.hl7.org/CodeSystem/v3-ActCode certified sleep disorders care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CSPT http://terminology.hl7.org/CodeSystem/v3-ActCode certified spine treatment care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CTBU http://terminology.hl7.org/CodeSystem/v3-ActCode certified trauma/burn center care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CVDC http://terminology.hl7.org/CodeSystem/v3-ActCode certified vascular diseases care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CWMA http://terminology.hl7.org/CodeSystem/v3-ActCode certified wound management care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
CWOH http://terminology.hl7.org/CodeSystem/v3-ActCode certified women's health care Description:Scope of responsibility taken on by an organization for care of a patient as defined by the disease management certification agency.
_ActEncounterCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActEncounterCode Domain provides codes that qualify the ActEncounterClass (ENC)
AMB http://terminology.hl7.org/CodeSystem/v3-ActCode ambulatory 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.
EMER http://terminology.hl7.org/CodeSystem/v3-ActCode emergency 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.)
FLD http://terminology.hl7.org/CodeSystem/v3-ActCode field 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.
HH http://terminology.hl7.org/CodeSystem/v3-ActCode home health Healthcare encounter that takes place in the residence of the patient or a designee
IMP http://terminology.hl7.org/CodeSystem/v3-ActCode inpatient encounter 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.
ACUTE http://terminology.hl7.org/CodeSystem/v3-ActCode inpatient acute An acute inpatient encounter.
NONAC http://terminology.hl7.org/CodeSystem/v3-ActCode inpatient non-acute Any category of inpatient encounter except 'acute'
OBSENC http://terminology.hl7.org/CodeSystem/v3-ActCode observation encounter 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.
PRENC http://terminology.hl7.org/CodeSystem/v3-ActCode pre-admission 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 ciphertext. User may the service registration, and a new account number is generated. Usage Note: This is intended to be used in advance of encounter types such as ambulatory, inpatient encounter, virtual, etc.
SS http://terminology.hl7.org/CodeSystem/v3-ActCode short stay An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours.
VR http://terminology.hl7.org/CodeSystem/v3-ActCode virtual 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.
_ActMedicalServiceCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActMedicalServiceCode General category of medical service provided to the patient during their encounter.
ALC http://terminology.hl7.org/CodeSystem/v3-ActCode Alternative Level of Care Provision of Alternate Level of Care to a key patient in an acute bed. Patient is waiting for placement in a long-term care facility and is unable to decrypt per license return home.
CARD http://terminology.hl7.org/CodeSystem/v3-ActCode Cardiology Provision of diagnosis and treatment of diseases and disorders affecting the heart
CHR http://terminology.hl7.org/CodeSystem/v3-ActCode Chronic Provision of recurring care for chronic illness.
DNTL http://terminology.hl7.org/CodeSystem/v3-ActCode Dental Provision of treatment for oral health and/or dental surgery.
DRGRHB http://terminology.hl7.org/CodeSystem/v3-ActCode Drug Rehab Provision of treatment for drug abuse.
GENRL http://terminology.hl7.org/CodeSystem/v3-ActCode General General care performed by a general practitioner or "shared secret". family doctor as a responsible provider for a patient.
LABEL MED http://terminology.hl7.org/CodeSystem/v3-ActCode assign security label Medical Custodian security system must assign Provision of diagnostic and/or therapeutic treatment.
OBS http://terminology.hl7.org/CodeSystem/v3-ActCode Obstetrics Provision of care of women during pregnancy, childbirth and bind security labels immediate postpartum period. Also known as Maternity.
ONC http://terminology.hl7.org/CodeSystem/v3-ActCode Oncology Provision of treatment and/or diagnosis related to tumors and/or cancer.
PALL http://terminology.hl7.org/CodeSystem/v3-ActCode Palliative Provision of care for patients who are living or dying from an advanced illness.
PED http://terminology.hl7.org/CodeSystem/v3-ActCode Pediatrics Provision of diagnosis and treatment of diseases and disorders affecting children.
PHAR http://terminology.hl7.org/CodeSystem/v3-ActCode Pharmaceutical Pharmaceutical care performed by a pharmacist.
PHYRHB http://terminology.hl7.org/CodeSystem/v3-ActCode Physical Rehab Provision of treatment for physical injury.
PSYCH http://terminology.hl7.org/CodeSystem/v3-ActCode Psychiatric Provision of treatment of psychiatric disorder relating to mental illness.
SURG http://terminology.hl7.org/CodeSystem/v3-ActCode Surgical Provision of surgical treatment.
_ActClaimAttachmentCategoryCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActClaimAttachmentCategoryCode Description: Coded types of attachments included to support a healthcare claim.
AUTOATTCH http://terminology.hl7.org/CodeSystem/v3-ActCode auto attachment Description: Automobile Information Attachment
DOCUMENT http://terminology.hl7.org/CodeSystem/v3-ActCode document Description: Document Attachment
HEALTHREC http://terminology.hl7.org/CodeSystem/v3-ActCode health record Description: Health Record Attachment
IMG http://terminology.hl7.org/CodeSystem/v3-ActCode image attachment Description: Image Attachment
LABRESULTS http://terminology.hl7.org/CodeSystem/v3-ActCode lab results Description: Lab Results Attachment
MODEL http://terminology.hl7.org/CodeSystem/v3-ActCode model Description: Digital Model Attachment
WIATTCH http://terminology.hl7.org/CodeSystem/v3-ActCode work injury report attachment Description: Work Injury related additional Information Attachment
XRAY http://terminology.hl7.org/CodeSystem/v3-ActCode x-ray Description: Digital X-Ray Attachment
_ActConsentType http://terminology.hl7.org/CodeSystem/v3-ActCode ActConsentType Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in order specific ways within an EHRS or for health information exchange; or to classify disclose health information created for purposes such as research.
ICOL http://terminology.hl7.org/CodeSystem/v3-ActCode information collection Definition: Consent to have healthcare information collected in an electronic health record. This entails that the information may be used in analysis, modified, updated.
IDSCL http://terminology.hl7.org/CodeSystem/v3-ActCode information disclosure Definition: Consent to have collected healthcare information disclosed.
INFA http://terminology.hl7.org/CodeSystem/v3-ActCode information access Definition: Consent to access healthcare information.
INFAO http://terminology.hl7.org/CodeSystem/v3-ActCode access only 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. Example: Opened and then emailed or screen printed for use outside of the consent directive purpose.
INFASO http://terminology.hl7.org/CodeSystem/v3-ActCode access and save only Definition: Consent to access and save only, which entails that access to the saved copy will remain locked.
IRDSCL http://terminology.hl7.org/CodeSystem/v3-ActCode information redisclosure Definition: Information re-disclosed without the patient's consent.
RESEARCH http://terminology.hl7.org/CodeSystem/v3-ActCode research information access Definition: Consent to have healthcare information in an electronic health record accessed for research purposes.
RSDID http://terminology.hl7.org/CodeSystem/v3-ActCode de-identified information access 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 systems under any circumstance.
RSREID http://terminology.hl7.org/CodeSystem/v3-ActCode re-identifiable information access 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. Example:: Where there is a need to inform the subject of potential health issues.
_ActContainerRegistrationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActContainerRegistrationCode Constrains the ActCode to the domain of Container Registration
ID http://terminology.hl7.org/CodeSystem/v3-ActCode Identified Used by one system to inform another that it has received a container.
IP http://terminology.hl7.org/CodeSystem/v3-ActCode In Position Used by one system to inform another that the container is in position for specimen transfer (e.g., container removal from track, pipetting, etc.).
L http://terminology.hl7.org/CodeSystem/v3-ActCode Left Equipment Used by one system to inform another that the container has been released from that system.
M http://terminology.hl7.org/CodeSystem/v3-ActCode Missing Used by one system to inform another that the container did not arrive at its next expected location.
O http://terminology.hl7.org/CodeSystem/v3-ActCode In Process 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.
R http://terminology.hl7.org/CodeSystem/v3-ActCode Process Completed 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.
X http://terminology.hl7.org/CodeSystem/v3-ActCode Container Unavailable 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).
_ActControlVariable http://terminology.hl7.org/CodeSystem/v3-ActCode ActControlVariable 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. 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 for collection, access, 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).
AUTO http://terminology.hl7.org/CodeSystem/v3-ActCode auto-repeat permission Specifies whether or not automatic repeat testing is to be initiated on specimens.
ENDC http://terminology.hl7.org/CodeSystem/v3-ActCode endogenous content 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.
REFLEX http://terminology.hl7.org/CodeSystem/v3-ActCode reflex permission Specifies whether or not further testing may be automatically or manually initiated on specimens.
_ActCoverageConfirmationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageConfirmationCode Response to an insurance coverage eligibility query or authorization request.
_ActCoverageAuthorizationConfirmationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageAuthorizationConfirmationCode Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside.
AUTH http://terminology.hl7.org/CodeSystem/v3-ActCode Authorized Authorization approved and disclosure funds have been set aside to pay for specified healthcare service(s) and/or product(s) within defined criteria for the authorization.
NAUTH http://terminology.hl7.org/CodeSystem/v3-ActCode Not Authorized Authorization for specified healthcare service(s) and/or product(s) denied.
_ActCoverageEligibilityConfirmationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageEligibilityConfirmationCode Indication of eligibility coverage for healthcare service(s) and/or product(s).
ELG http://terminology.hl7.org/CodeSystem/v3-ActCode Eligible Insurance coverage is in accordance with effect for healthcare service(s) and/or product(s).
NELG http://terminology.hl7.org/CodeSystem/v3-ActCode Not Eligible Insurance coverage is not in effect for healthcare service(s) and/or product(s). May optionally include reasons for the ineligibility.
_ActCoverageLimitCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageLimitCode Criteria that are applicable jurisdictional privacy policies associated with to the target information. authorized coverage.
_ActCoverageQuantityLimitCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageQuantityLimitCode 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.
COVPRD http://terminology.hl7.org/CodeSystem/v3-ActCode coverage period Codes representing the time period during which coverage is available; or financial participation requirements are in effect.
LFEMX http://terminology.hl7.org/CodeSystem/v3-ActCode life time maximum 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.
NETAMT http://terminology.hl7.org/CodeSystem/v3-ActCode Net Amount Maximum net amount that will be covered for the product or service specified.
PRDMX http://terminology.hl7.org/CodeSystem/v3-ActCode period maximum 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.
UNITPRICE http://terminology.hl7.org/CodeSystem/v3-ActCode Unit Price Maximum unit price that will be covered for the authorized product or service.
UNITQTY http://terminology.hl7.org/CodeSystem/v3-ActCode Unit Quantity Maximum number of items that will be covered of the product or service specified.
COVMX http://terminology.hl7.org/CodeSystem/v3-ActCode coverage maximum Definition: Codes representing the maximum coverate or financial participation requirements.
_ActCoveredPartyLimitCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoveredPartyLimitCode Codes representing the types of covered parties that may receive covered benefits under a policy or program.
_ActCoverageTypeCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.
_ActInsurancePolicyCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInsurancePolicyCode Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs.
EHCPOL http://terminology.hl7.org/CodeSystem/v3-ActCode extended healthcare Private insurance policy that provides coverage in addition to other policies (e.g. in addition to a Public Healthcare insurance policy).
HSAPOL http://terminology.hl7.org/CodeSystem/v3-ActCode health spending account 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.
AUTOPOL http://terminology.hl7.org/CodeSystem/v3-ActCode automobile Insurance policy for injuries sustained in an automobile accident. Will also typically covered non-named parties to the policy, such as pedestrians and passengers.
COL http://terminology.hl7.org/CodeSystem/v3-ActCode collision coverage policy 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.
UNINSMOT http://terminology.hl7.org/CodeSystem/v3-ActCode uninsured motorist policy 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.
PUBLICPOL http://terminology.hl7.org/CodeSystem/v3-ActCode public healthcare Insurance policy funded by a public health system must retain 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).
DENTPRG http://terminology.hl7.org/CodeSystem/v3-ActCode dental program 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.
DISEASEPRG http://terminology.hl7.org/CodeSystem/v3-ActCode public health program 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. Example: Reproductive health, sexually transmitted disease, and end renal disease programs.
CANPRG http://terminology.hl7.org/CodeSystem/v3-ActCode women's cancer detection program 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. 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 immutable record 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.
ENDRENAL http://terminology.hl7.org/CodeSystem/v3-ActCode end renal program Definition: A public or government program that administers publicly funded coverage of kidney dialysis and kidney transplant services. Example: In the assignment U.S., the Medicare End-stage Renal Disease program (ESRD), the National Kidney Foundation (NKF) American Kidney Fund (AKF) The Organ Transplant Fund.
HIVAIDS http://terminology.hl7.org/CodeSystem/v3-ActCode HIV-AIDS program Definition: Government administered and binding. Usage Note: 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. Example: In security systems, security policy label assignments do not change, they the U.S., the Ryan White program, which is administered by the Health Resources and Services Administration.
MANDPOL http://terminology.hl7.org/CodeSystem/v3-ActCode mandatory health program mandatory health program
MENTPRG http://terminology.hl7.org/CodeSystem/v3-ActCode mental health program 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 supersede prior assignments, be delegated to contractors. Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA).
SAFNET http://terminology.hl7.org/CodeSystem/v3-ActCode safety net clinic program Definition: Government administered and funded program to support provision of care to underserved populations through safety net clinics. Example: In the U.S., safety net providers such reassignments are always tracked as federally qualified health centers (FQHC) receive funding under PHSA Section 330 grants administered by the Health Resources and Services Administration.
SUBPRG http://terminology.hl7.org/CodeSystem/v3-ActCode substance use program Definition: Government administered and funded substance use program for auditing 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. Example: In the U.S., states receive funding for substance use programs from the Substance Abuse Mental Health Administration (SAMHSA).
SUBSIDIZ http://terminology.hl7.org/CodeSystem/v3-ActCode subsidized health program 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 purposes. coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
PSEUD SUBSIDMC http://terminology.hl7.org/CodeSystem/v3-ActCode pseudonymize subsidized managed care program Custodian system must strip information 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 data residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds. 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.
SUBSUPP http://terminology.hl7.org/CodeSystem/v3-ActCode subsidized supplemental health program Definition: A government health program that would allow 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 identification cost of which is to some extent subsidized by public funds. Example: Supplemental health coverage program may cover the source cost of a health program or policy financial participations, such as the information copays and the premiums, and may provide coverage for services in addition to those covered under the supplemented health program or policy. In the information subject. Custodian U.S., Medicaid programs may retain pay the premium for a key to relink data necessary to reidentify covered party who is also covered under the information subject. Medicare program or a private health policy. 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.
CREATE WCBPOL http://terminology.hl7.org/CodeSystem/v3-DataOperation http://terminology.hl7.org/CodeSystem/v3-ActCode create worker's compensation Description:Fundamental operation Insurance policy for injuries sustained in an Information System (IS) that results only the work place or in the act course of bringing employment.
_ActInsuranceTypeCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInsuranceTypeCode 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 object individual or an organization enters into existence. Note: The preceding definition 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 taken guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the HL7 RBAC specification. There is no restriction on how risk of loss, makes a decision as to whether the operation risk is invoked, 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., via whether the covered parties are jointly or severably insured. 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 user interface. For relative of the covered party, a partnership, or a corporation, e.g., an HL7 Act, 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 state transitions per policy holder is the HL7 Reference Information Model. employer. See CoveredRoleType.
DELETE _ActHealthInsuranceTypeCode http://terminology.hl7.org/CodeSystem/v3-DataOperation http://terminology.hl7.org/CodeSystem/v3-ActCode delete ActHealthInsuranceTypeCode Description:Fundamental operation 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 an Information System (IS) accordance with a plan, which specifies (1) the type of health services and health conditions that results only 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 removal type and affiliation of information about providers (e.g., only allopathic physicians, only in network, only providers employed by an object 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).
DENTAL http://terminology.hl7.org/CodeSystem/v3-ActCode dental care policy Definition: A health insurance policy that that covers benefits for dental services.
DISEASE http://terminology.hl7.org/CodeSystem/v3-ActCode disease specific policy 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.
DRUGPOL http://terminology.hl7.org/CodeSystem/v3-ActCode drug policy Definition: A health insurance policy that covers benefits for prescription drugs, pharmaceuticals, and supplies.
HIP http://terminology.hl7.org/CodeSystem/v3-ActCode health insurance plan policy Definition: A health insurance policy that covers healthcare benefits by protecting covered parties from memory medical expenses arising from health conditions, sickness, or storage. Note: The preceding definition 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. 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 taken from the HL7 RBAC specification. There 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.
LTC http://terminology.hl7.org/CodeSystem/v3-ActCode long term care policy Definition: An insurance policy that covers benefits for long-term care services people need when they no restriction 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: Help at home with day-to-day activities, such as cooking, cleaning, bathing and dressing Care in the community, such as in an adult day care facility Supervised care provided in an assisted living facility Skilled care provided in a nursing home
MCPOL http://terminology.hl7.org/CodeSystem/v3-ActCode managed care policy 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. 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. 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 how by the operation is invoked, e.g., via medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a user interface. 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.
UPDATE POS http://terminology.hl7.org/CodeSystem/v3-DataOperation http://terminology.hl7.org/CodeSystem/v3-ActCode revise point of service policy Definition:Fundamental operation 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 Information System (IS) FFS plan.
HMO http://terminology.hl7.org/CodeSystem/v3-ActCode health maintenance organization policy Definition: A policy for a health plan that results provides coverage for health care only through contracted or employed physicians and hospitals located in the revision particular geographic or alteration service areas. HMOs emphasize prevention and early detection of illness. Eligibility to enroll in an object. Note: The preceding definition HMO is taken determined by where a covered party lives or works.
PPO http://terminology.hl7.org/CodeSystem/v3-ActCode preferred provider organization policy 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.
MENTPOL http://terminology.hl7.org/CodeSystem/v3-ActCode mental health policy Definition: A health insurance policy that covers benefits for mental health services and prescriptions.
SUBPOL http://terminology.hl7.org/CodeSystem/v3-ActCode substance use policy Definition: A health insurance policy that covers benefits for substance use services.
VISPOL http://terminology.hl7.org/CodeSystem/v3-ActCode vision care policy Definition: Set of codes for a policy that provides coverage for health care expenses arising from vision services. A health insurance policy that covers benefits for vision care services, prescriptions, and products.
DIS http://terminology.hl7.org/CodeSystem/v3-ActCode disability insurance policy Definition: An insurance policy that provides a regular payment to compensate for income lost due to the HL7 RBAC specification. There covered party's inability to work because of illness or injury.
EWB http://terminology.hl7.org/CodeSystem/v3-ActCode employee welfare benefit plan policy 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.
FLEXP http://terminology.hl7.org/CodeSystem/v3-ActCode flexible benefit plan policy 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. Discussion: See UnderwriterRoleTypeCode flexible benefit plan which is no restriction 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.
LIFE http://terminology.hl7.org/CodeSystem/v3-ActCode life insurance policy 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 how another person. Specific exclusions are often written into the operation contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion. 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 invoked, e.g., via the sale of a user interface. 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).
APPEND ANNU http://terminology.hl7.org/CodeSystem/v3-DataOperation http://terminology.hl7.org/CodeSystem/v3-ActCode append annuity policy Description:Fundamental operation Definition: A policy that, after an initial premium or premiums, pays out a sum at pre-determined intervals. 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.
TLIFE http://terminology.hl7.org/CodeSystem/v3-ActCode term life insurance policy Definition: Life insurance under which the benefit is payable only if the insured dies during a specified period. If an Information System (IS) insured dies during that results only in period, the addition beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing.
ULIFE http://terminology.hl7.org/CodeSystem/v3-ActCode universal life insurance policy Definition: Life insurance under which the benefit is payable upon the insuredaTMs death or diagnosis of information to a terminal illness. If an object already in existence. Note: insured dies during that period, the beneficiary receives the death payments. If the insured survives, the policy ends and the beneficiary receives nothing
PNC http://terminology.hl7.org/CodeSystem/v3-ActCode property and casualty insurance policy 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 preceding definition 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.
REI http://terminology.hl7.org/CodeSystem/v3-ActCode reinsurance policy Definition: An agreement between two or more insurance companies by which the risk of loss is taken from proportioned. Thus the HL7 RBAC specification. There risk of loss is no restriction spread and a disproportionately large loss under a single policy does not fall on how one insurance company. Acceptance by an insurer, called a reinsurer, of all or part of the operation risk of loss of another insurance company. Discussion: Reinsurance is invoked, e.g., via a user interface. 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. 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.
NULLIFY SURPL http://terminology.hl7.org/CodeSystem/v3-DataOperation http://terminology.hl7.org/CodeSystem/v3-ActCode nullify surplus line insurance policy Description:Change Definition: A risk or part of a risk for which there is no normal insurance market available. Insurance written by unauthorized insurance companies. Surplus lines insurance is insurance placed with unauthorized insurance companies through licensed surplus lines agents or brokers.
UMBRL http://terminology.hl7.org/CodeSystem/v3-ActCode umbrella liability insurance policy Definition: A form of insurance protection that provides additional liability coverage after the status 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.
_ActProgramTypeCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActProgramTypeCode Definition: A set of codes used to indicate coverage under a program. A program is an object representing an Act organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to "nullified", i.e., treat as though 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 never existed. For 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 HL7 Act, underwriter would consider an insurable risk, i.e., the state transitions per risk is not random in nature, not financially measurable, and likely requires subsidization with government funds. 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 HL7 Reference Information Model. 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.
PART CHAR http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode Participation charity program Indicates Definition: A program that covers the target cost of services provided directly to a beneficiary who typically has no other source of coverage without charge.
CRIME http://terminology.hl7.org/CodeSystem/v3-ActCode crime victim program Definition: A program that covers the participation cost of services provided to crime victims for injuries or losses related to the occurrence of a crime.
EAP http://terminology.hl7.org/CodeSystem/v3-ActCode employee assistance program Definition: An employee assistance program is involved 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 some 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.
GOVEMP http://terminology.hl7.org/CodeSystem/v3-ActCode government employee health program 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 act, but does not qualify how. program in accordance to the regulation Example: Federal employee health benefit program in the U.S.
ADM HIRISK http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode admitter high risk pool program 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 practitioner 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.
IND http://terminology.hl7.org/CodeSystem/v3-ActCode indigenous peoples health program Definition: Services provided directly and through contracted and operated indigenous peoples health programs. Example: Indian Health Service in the U.S.
MILITARY http://terminology.hl7.org/CodeSystem/v3-ActCode military health program Definition: A government program that provides coverage for health services to military personnel, retirees, and dependents. A covered party who is responsible for admitting 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. Example: In the U.S., TRICARE, CHAMPUS.
RETIRE http://terminology.hl7.org/CodeSystem/v3-ActCode retiree health program 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.
SOCIAL http://terminology.hl7.org/CodeSystem/v3-ActCode social service program Definition: A social service program funded by a public or governmental entity. 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.
VET http://terminology.hl7.org/CodeSystem/v3-ActCode veteran health program Definition: Services provided directly and through contracted and operated veteran health programs.
_ActDetectedIssueManagementCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActDetectedIssueManagementCode Codes dealing with the management of Detected Issue observations
_ActAdministrativeDetectedIssueManagementCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdministrativeDetectedIssueManagementCode Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains.
_AuthorizationIssueManagementCode http://terminology.hl7.org/CodeSystem/v3-ActCode Authorization Issue Management Code Authorization Issue Management Code
EMAUTH http://terminology.hl7.org/CodeSystem/v3-ActCode emergency authorization override Used to temporarily override normal authorization rules to gain access to data in a patient encounter. 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.
ATND 21 http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode attender authorization confirmed Description: Indicates that the permissions have been externally verified and the request should be processed.
1 http://terminology.hl7.org/CodeSystem/v3-ActCode Therapy Appropriate Confirmed drug therapy appropriate
19 http://terminology.hl7.org/CodeSystem/v3-ActCode Consulted Supplier Consulted other supplier/pharmacy, therapy confirmed
2 http://terminology.hl7.org/CodeSystem/v3-ActCode Assessed Patient Assessed patient, therapy is appropriate
22 http://terminology.hl7.org/CodeSystem/v3-ActCode appropriate indication or diagnosis Description: The practitioner patient has the appropriate indication or diagnosis for the action to be taken.
23 http://terminology.hl7.org/CodeSystem/v3-ActCode prior therapy documented Description: It has been confirmed that the appropriate pre-requisite therapy has responsibility been tried.
3 http://terminology.hl7.org/CodeSystem/v3-ActCode Patient Explanation Patient gave adequate explanation
4 http://terminology.hl7.org/CodeSystem/v3-ActCode Consulted Other Source Consulted other supply source, therapy still appropriate
5 http://terminology.hl7.org/CodeSystem/v3-ActCode Consulted Prescriber Consulted prescriber, therapy confirmed
6 http://terminology.hl7.org/CodeSystem/v3-ActCode Prescriber Declined Change Consulted prescriber and recommended change, prescriber declined
7 http://terminology.hl7.org/CodeSystem/v3-ActCode Interacting Therapy No Longer Active/Planned Concurrent therapy triggering alert is no longer on-going or planned
14 http://terminology.hl7.org/CodeSystem/v3-ActCode Supply Appropriate Confirmed supply action appropriate
15 http://terminology.hl7.org/CodeSystem/v3-ActCode Replacement Patient's existing supply was lost/wasted
16 http://terminology.hl7.org/CodeSystem/v3-ActCode Vacation Supply Supply date is due to patient vacation
17 http://terminology.hl7.org/CodeSystem/v3-ActCode Weekend Supply Supply date is intended to carry patient over weekend
18 http://terminology.hl7.org/CodeSystem/v3-ActCode Leave of Absence Supply is intended for overseeing use during a leave of absence from an institution.
20 http://terminology.hl7.org/CodeSystem/v3-ActCode additional quantity on separate dispense Description: Supply is different than expected as an additional quantity has been supplied in a separate dispense.
8 http://terminology.hl7.org/CodeSystem/v3-ActCode Other Action Taken Order is performed as issued, but other action taken to mitigate potential adverse effects
10 http://terminology.hl7.org/CodeSystem/v3-ActCode Provided Patient Education Provided education or training to the patient on appropriate therapy use
11 http://terminology.hl7.org/CodeSystem/v3-ActCode Added Concurrent Therapy Instituted an additional therapy to mitigate potential negative effects
12 http://terminology.hl7.org/CodeSystem/v3-ActCode Temporarily Suspended Concurrent Therapy Suspended existing therapy that triggered interaction for the duration of this therapy
13 http://terminology.hl7.org/CodeSystem/v3-ActCode Stopped Concurrent Therapy Aborted existing therapy that triggered interaction.
9 http://terminology.hl7.org/CodeSystem/v3-ActCode Instituted Ongoing Monitoring Program Arranged to monitor patient for adverse effects
_ActExposureCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActExposureCode 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.
CHLDCARE http://terminology.hl7.org/CodeSystem/v3-ActCode Day care - Child care Interaction Description: Exposure participants' interaction occurred in a child care setting
CONVEYNC http://terminology.hl7.org/CodeSystem/v3-ActCode Common Conveyance Interaction 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).
HLTHCARE http://terminology.hl7.org/CodeSystem/v3-ActCode Health Care Interaction - Not Patient Care 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).
HOMECARE http://terminology.hl7.org/CodeSystem/v3-ActCode Care Giver Interaction 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.
HOSPPTNT http://terminology.hl7.org/CodeSystem/v3-ActCode Hospital Patient Interaction Description: Exposure participants' interaction occurred when both were patients being treated in the same (acute) health care delivery facility.
HOSPVSTR http://terminology.hl7.org/CodeSystem/v3-ActCode Hospital Visitor Interaction Description: Exposure participants' interaction occurred when one visited the other who was a patient being treated in a health care delivery facility.
HOUSEHLD http://terminology.hl7.org/CodeSystem/v3-ActCode Household Interaction Description: Exposure interaction occurred in context of domestic interaction, i.e. both participants reside in the same household.
INMATE http://terminology.hl7.org/CodeSystem/v3-ActCode Inmate Interaction Description: Exposure participants' interaction occurred in the course of one or both participants being incarcerated at a correctional facility
INTIMATE http://terminology.hl7.org/CodeSystem/v3-ActCode Intimate Interaction Description: Exposure interaction was intimate, i.e. participants are intimate companions (e.g. spouses, domestic partners).
LTRMCARE http://terminology.hl7.org/CodeSystem/v3-ActCode Long Term Care Facility Interaction 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).
PLACE http://terminology.hl7.org/CodeSystem/v3-ActCode Common Space Interaction Description: An interaction where the exposure participants were both present in the same location/place/space.
PTNTCARE http://terminology.hl7.org/CodeSystem/v3-ActCode Health Care Interaction - Patient Care Description: Exposure participants' interaction occurred during the course of health care delivery by a provider (e.g. a physician treating a patient encounter. in her office).
CALLBCK SCHOOL2 http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode callback contact School Interaction Description: Exposure participants' interaction occurred in an academic setting (e.g., participants are fellow students, or student and teacher).
SOCIAL2 http://terminology.hl7.org/CodeSystem/v3-ActCode Social/Extended Family Interaction Description: An interaction where the exposure participants are social associates or members of the same extended family
SUBSTNCE http://terminology.hl7.org/CodeSystem/v3-ActCode Common Substance Interaction Description: An interaction where the exposure participants shared or co-used a common substance (e.g. drugs, needles, or common food item).
TRAVINT http://terminology.hl7.org/CodeSystem/v3-ActCode Common Travel Interaction Description: An interaction where the exposure participants traveled together in/on the same vehicle/trip (e.g. concurrent co-passengers).
WORK2 http://terminology.hl7.org/CodeSystem/v3-ActCode Work Interaction Description: Exposure interaction occurred in a work setting, i.e. participants are co-workers.
_ActFinancialTransactionCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActFinancialTransactionCode ActFinancialTransactionCode
CHRG http://terminology.hl7.org/CodeSystem/v3-ActCode Standard Charge A type of transaction that represents a charge for a service or product. Expressed in monetary terms.
REV http://terminology.hl7.org/CodeSystem/v3-ActCode Standard Charge Reversal 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.
_ActIncidentCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActIncidentCode Set of codes indicating the type of incident or accident.
MVA http://terminology.hl7.org/CodeSystem/v3-ActCode Motor vehicle accident Incident or accident as the result of a motor vehicle accident
SCHOOL http://terminology.hl7.org/CodeSystem/v3-ActCode School Accident Incident or accident is the result of a school place accident.
SPT http://terminology.hl7.org/CodeSystem/v3-ActCode Sporting Accident Incident or accident is the result of a sporting accident.
WPA http://terminology.hl7.org/CodeSystem/v3-ActCode Workplace accident Incident or accident is the result of a work place accident
_ActInformationAccessCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInformationAccessCode Description: The type of health information to which the subject of the information or the subject's delegate consents or dissents.
ACADR http://terminology.hl7.org/CodeSystem/v3-ActCode adverse drug reaction access Description: Provide consent to collect, use, disclose, or access adverse drug reaction information for a patient.
ACALL http://terminology.hl7.org/CodeSystem/v3-ActCode all access Description: Provide consent to collect, use, disclose, or access all information for a patient.
ACALLG http://terminology.hl7.org/CodeSystem/v3-ActCode allergy access Description: Provide consent to collect, use, disclose, or access allergy information for a patient.
ACCONS http://terminology.hl7.org/CodeSystem/v3-ActCode informational consent access Description: Provide consent to collect, use, disclose, or access informational consent information for a patient.
ACDEMO http://terminology.hl7.org/CodeSystem/v3-ActCode demographics access Description: Provide consent to collect, use, disclose, or access demographics information for a patient.
ACDI http://terminology.hl7.org/CodeSystem/v3-ActCode diagnostic imaging access Description: Provide consent to collect, use, disclose, or access diagnostic imaging information for a patient.
ACIMMUN http://terminology.hl7.org/CodeSystem/v3-ActCode immunization access Description: Provide consent to collect, use, disclose, or access immunization information for a patient.
ACLAB http://terminology.hl7.org/CodeSystem/v3-ActCode lab test result access Description: Provide consent to collect, use, disclose, or access lab test result information for a patient.
ACMED http://terminology.hl7.org/CodeSystem/v3-ActCode medication access Description: Provide consent to collect, use, disclose, or access medical condition information for a patient.
ACMEDC http://terminology.hl7.org/CodeSystem/v3-ActCode medical condition access Definition: Provide consent to view or access medical condition information for a patient.
ACMEN http://terminology.hl7.org/CodeSystem/v3-ActCode mental health access Description:Provide consent to collect, use, disclose, or access mental health information for a patient.
ACOBS http://terminology.hl7.org/CodeSystem/v3-ActCode common observations access Description: Provide consent to collect, use, disclose, or access common observation information for a patient.
ACPOLPRG http://terminology.hl7.org/CodeSystem/v3-ActCode policy or program information access Description: Provide consent to collect, use, disclose, or access coverage policy or program for a patient.
ACPROV http://terminology.hl7.org/CodeSystem/v3-ActCode provider information access Description: Provide consent to collect, use, disclose, or access provider information for a patient.
ACPSERV http://terminology.hl7.org/CodeSystem/v3-ActCode professional service access Description: Provide consent to collect, use, disclose, or access professional service information for a patient.
ACSUBSTAB http://terminology.hl7.org/CodeSystem/v3-ActCode substance abuse access Description:Provide consent to collect, use, disclose, or access substance abuse information for a patient.
_ActInformationAccessContextCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInformationAccessContextCode 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.
INFAUT http://terminology.hl7.org/CodeSystem/v3-ActCode authorized information transfer 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.
INFCON http://terminology.hl7.org/CodeSystem/v3-ActCode after explicit consent 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.
INFCRT http://terminology.hl7.org/CodeSystem/v3-ActCode only on court order 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.
INFDNG http://terminology.hl7.org/CodeSystem/v3-ActCode only if danger to others 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.
INFEMER http://terminology.hl7.org/CodeSystem/v3-ActCode only in an emergency Authorization to collect, access, use, or disclose specified patient health information in accordance with emergency information transfer protocol dictated by jurisdictional law, organization who should be contacted policy, or standards of practice. For example, sharing of health information during disaster response.
INFPWR http://terminology.hl7.org/CodeSystem/v3-ActCode only if public welfare risk 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.
INFREG http://terminology.hl7.org/CodeSystem/v3-ActCode regulatory information transfer Authorization to collect, access, use, or disclose specified patient health information for follow-up questions about 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.
_ActInformationCategoryCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInformationCategoryCode Definition:Indicates the act set of information types which may be manipulated or referenced, such as for recommending access restrictions.
ALLCAT http://terminology.hl7.org/CodeSystem/v3-ActCode all categories Description: All patient information.
ALLGCAT http://terminology.hl7.org/CodeSystem/v3-ActCode allergy category Definition:All information pertaining to a patient's allergy and intolerance records.
ARCAT http://terminology.hl7.org/CodeSystem/v3-ActCode adverse drug reaction category Description: All information pertaining to a patient's adverse drug reactions.
COBSCAT http://terminology.hl7.org/CodeSystem/v3-ActCode common observation category Definition:All information pertaining to a patient's common observation records (height, weight, blood pressure, temperature, etc.).
DEMOCAT http://terminology.hl7.org/CodeSystem/v3-ActCode demographics category Definition:All information pertaining to a patient's demographics (such as name, date of birth, gender, address, etc).
DICAT http://terminology.hl7.org/CodeSystem/v3-ActCode diagnostic image category Definition:All information pertaining to a patient's diagnostic image records (orders & results).
IMMUCAT http://terminology.hl7.org/CodeSystem/v3-ActCode immunization category Definition:All information pertaining to a patient's vaccination records.
LABCAT http://terminology.hl7.org/CodeSystem/v3-ActCode lab test category Description: All information pertaining to a patient's lab test records (orders & results)
MEDCCAT http://terminology.hl7.org/CodeSystem/v3-ActCode medical condition category Definition:All information pertaining to a patient's medical condition records.
MENCAT http://terminology.hl7.org/CodeSystem/v3-ActCode mental health category Description: All information pertaining to a patient's mental health records.
PSVCCAT http://terminology.hl7.org/CodeSystem/v3-ActCode professional service category Definition:All information pertaining to a patient's professional service records (such as smoking cessation, counseling, medication review, mental health).
RXCAT http://terminology.hl7.org/CodeSystem/v3-ActCode medication category Definition:All information pertaining to a patient's medication records (orders, dispenses and other active medications).
_ActInvoiceElementCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceElementCode Type of invoice element that is used to assist in place describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results.
_ActInvoiceAdjudicationPaymentCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceAdjudicationPaymentCode 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.
_ActInvoiceAdjudicationPaymentGroupCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceAdjudicationPaymentGroupCode Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc.
ALEC http://terminology.hl7.org/CodeSystem/v3-ActCode alternate electronic Payment initiated by the author. 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).
CON BONUS http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode consultant bonus Bonus payments based on performance, volume, etc. as agreed to by the payor.
CFWD http://terminology.hl7.org/CodeSystem/v3-ActCode carry forward adjusment An advisor participating amount still owing to the payor but the payment is 0$ and this cannot be settled until a future payment is made.
EDU http://terminology.hl7.org/CodeSystem/v3-ActCode education fees Fees deducted on behalf of a payee for tuition and continuing education.
EPYMT http://terminology.hl7.org/CodeSystem/v3-ActCode early payment fee Fees deducted on behalf of a payee for charges based on a shorter payment frequency (i.e. next day versus biweekly payments.
GARN http://terminology.hl7.org/CodeSystem/v3-ActCode garnishee Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee.
INVOICE http://terminology.hl7.org/CodeSystem/v3-ActCode submitted invoice Payment is based on a payment intent for a previously submitted Invoice, based on formal adjudication results..
PINV http://terminology.hl7.org/CodeSystem/v3-ActCode paper invoice Payment initiated by the payor as the result of adjudicating a paper (original, may have been faxed) invoice.
PPRD http://terminology.hl7.org/CodeSystem/v3-ActCode prior period adjustment An amount that was owed to the payor as indicated, by a carry forward adjusment, in a previous payment advice
PROA http://terminology.hl7.org/CodeSystem/v3-ActCode professional association deduction Professional association fee that is collected by the service payor from the practitioner/provider on behalf of the association
RECOV http://terminology.hl7.org/CodeSystem/v3-ActCode recovery Retroactive adjustment such as fee rate adjustment due to contract negotiations.
RETRO http://terminology.hl7.org/CodeSystem/v3-ActCode retro adjustment Bonus payments based on performance, volume, etc. as agreed to by performing evaluations the payor.
TRAN http://terminology.hl7.org/CodeSystem/v3-ActCode transaction fee Fees deducted on behalf of a payee for charges based on a per-transaction or time-period (e.g. monthly) fee.
_ActInvoiceAdjudicationPaymentSummaryCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceAdjudicationPaymentSummaryCode 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.
INVTYPE http://terminology.hl7.org/CodeSystem/v3-ActCode invoice type Transaction counts and making recommendations. value totals by invoice type (e.g. RXDINV - Pharmacy Dispense)
DIS PAYEE http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode discharger payee Transaction counts and value totals by each instance of an invoice payee.
PAYOR http://terminology.hl7.org/CodeSystem/v3-ActCode payor Transaction counts and value totals by each instance of an invoice payor.
SENDAPP http://terminology.hl7.org/CodeSystem/v3-ActCode sending application 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.
_ActInvoiceDetailCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailCode Codes representing a service or product that is being invoiced (billed). The practitioner who code can represent such concepts as "office visit", "drug X", "wheelchair" and other billable items such as taxes, service charges and discounts.
_ActInvoiceDetailClinicalProductCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailClinicalProductCode An identifying data string for healthcare products.
UNSPSC http://terminology.hl7.org/CodeSystem/v3-ActCode United Nations Standard Products and Services Classification Description:United Nations Standard Products and Services Classification, managed by Uniform Code Council (UCC): www.unspsc.org
_ActInvoiceDetailDrugProductCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailDrugProductCode An identifying data string for A substance used as a medication or in the preparation of medication.
GTIN http://terminology.hl7.org/CodeSystem/v3-ActCode Global Trade Item Number Description:Global Trade Item Number is responsible an identifier for trade items developed by GS1 (comprising the discharge former EAN International and Uniform Code Council).
UPC http://terminology.hl7.org/CodeSystem/v3-ActCode Universal Product Code 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.
_ActInvoiceDetailGenericCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailGenericCode The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments.
_ActInvoiceDetailGenericAdjudicatorCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailGenericAdjudicatorCode The billable item codes to identify adjudicator specified components to the total billing of a claim.
COIN http://terminology.hl7.org/CodeSystem/v3-ActCode coinsurance 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.
COPAYMENT http://terminology.hl7.org/CodeSystem/v3-ActCode patient from co-pay 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.
DEDUCTIBLE http://terminology.hl7.org/CodeSystem/v3-ActCode deductible 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.
PAY http://terminology.hl7.org/CodeSystem/v3-ActCode payment 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 encounter. 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.
ESC SPEND http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode escort spend down Only with Transportation 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
COINS http://terminology.hl7.org/CodeSystem/v3-ActCode co-insurance The covered party pays a percentage of the cost of covered services.
_ActInvoiceDetailGenericModifierCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailGenericModifierCode The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee.
AFTHRS http://terminology.hl7.org/CodeSystem/v3-ActCode non-normal hours Premium paid on service fees in compensation for practicing outside of normal working hours.
ISOL http://terminology.hl7.org/CodeSystem/v3-ActCode isolation allowance Premium paid on service fees in compensation for practicing in a remote location.
OOO http://terminology.hl7.org/CodeSystem/v3-ActCode out of office Premium paid on service fees in compensation for practicing at a location other than normal working location.
_ActInvoiceDetailGenericProviderCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailGenericProviderCode The billable item codes to identify provider supplied charges or changes to the total billing of a claim.
CANCAPT http://terminology.hl7.org/CodeSystem/v3-ActCode cancelled appointment A person who escorts charge to compensate the provider when a patient cancels an appointment with insufficient time for the provider to make another appointment with another patient.
REF DSC http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode referrer discount A person having referred reduction in the subject amount charged as a percentage of the amount. For example a 5% discount for volume purchase.
ESA http://terminology.hl7.org/CodeSystem/v3-ActCode extraordinary service assessment A premium on a service fee is requested because, due to extenuating circumstances, the performer (referring physician). Typically, service took an extraordinary amount of time or supplies.
FFSTOP http://terminology.hl7.org/CodeSystem/v3-ActCode fee for service top off Under agreement between the parties (payor and provider), a referring physician will receive guaranteed level of income is established for the provider over a report. 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.
AUT FNLFEE http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode author (originator) final fee Anticipated or actual final fee associated with treating a patient.
FRSTFEE http://terminology.hl7.org/CodeSystem/v3-ActCode first fee Anticipated or actual initial fee associated with treating a patient.
MARKUP http://terminology.hl7.org/CodeSystem/v3-ActCode markup or up-charge An increase in the amount charged as a percentage of the amount. For example, 12% markup on product cost.
MISSAPT http://terminology.hl7.org/CodeSystem/v3-ActCode missed appointment Definition: A party charge to compensate the provider when a patient does not show for an appointment.
PERFEE http://terminology.hl7.org/CodeSystem/v3-ActCode periodic fee 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.
PERMBNS http://terminology.hl7.org/CodeSystem/v3-ActCode performance bonus The amount for a performance bonus that originates is being requested from a payor for the Act 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 therefore has responsibility a code is submitted indicating the percentage achieved and the dollar amount claimed.
RESTOCK http://terminology.hl7.org/CodeSystem/v3-ActCode restocking fee 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.
TRAVEL http://terminology.hl7.org/CodeSystem/v3-ActCode travel A charge to cover the information given 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 Act effective agreement.
URGENT http://terminology.hl7.org/CodeSystem/v3-ActCode urgent Premium paid on service fees in compensation for providing an expedited response to an urgent situation.
_ActInvoiceDetailTaxCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailTaxCode 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.
FST http://terminology.hl7.org/CodeSystem/v3-ActCode federal sales tax Federal tax on transactions such as the Goods and ownership of this Act. Example: Services Tax (GST)
HST http://terminology.hl7.org/CodeSystem/v3-ActCode harmonized sales Tax Joint Federal/Provincial Sales Tax
PST http://terminology.hl7.org/CodeSystem/v3-ActCode provincial/state sales tax Tax levied by the report writer, provincial or state jurisdiction such as Provincial Sales Tax
_ActInvoiceDetailPreferredAccommodationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailPreferredAccommodationCode An identifying data string for medical facility accommodations.
_ActEncounterAccommodationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActEncounterAccommodationCode Accommodation type. In Intent mood, represents the person writing accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the act definition, available accommodation type.
_HL7AccommodationCode http://terminology.hl7.org/CodeSystem/v3-ActCode HL7AccommodationCode Description:Accommodation type. In Intent mood, represents the guideline author, accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the placer available accommodation type.
I http://terminology.hl7.org/CodeSystem/v3-ActCode Isolation Accommodations used in the care of diseases that are transmitted through casual contact or respiratory transmission.
P http://terminology.hl7.org/CodeSystem/v3-ActCode Private Accommodations in which there is only 1 bed.
S http://terminology.hl7.org/CodeSystem/v3-ActCode Suite Uniquely designed and elegantly decorated accommodations with many amenities available for an order, the EKG cart (device) creating additional charge.
SP http://terminology.hl7.org/CodeSystem/v3-ActCode Semi-private Accommodations in which there are 2 beds.
W http://terminology.hl7.org/CodeSystem/v3-ActCode Ward Accommodations in which there are 3 or more beds.
_ActInvoiceDetailClinicalServiceCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceDetailClinicalServiceCode An identifying data string for healthcare procedures.
_ActInvoiceGroupCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceGroupCode 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. Invoice elements of this type signify a report etc. Every Act should 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.
_ActInvoiceInterGroupCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceInterGroupCode Type of invoice element that is used to assist in describing an author. Authorship Invoice that is regardless either submitted for adjudication or for which is returned on adjudication results. Invoice elements of mood always actual authorship. Examples this type signify a grouping of such policies might include: 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. The author domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice.
CPNDDRGING http://terminology.hl7.org/CodeSystem/v3-ActCode compound drug invoice group A grouping of invoice element groups and anyone they explicitly delegate details including the ones specifying the compound ingredients being invoiced. It may update also contain generic detail items such as markup.
CPNDINDING http://terminology.hl7.org/CodeSystem/v3-ActCode compound ingredient invoice group A grouping of invoice element details including the report; All administrators within one specifying an ingredient drug being invoiced. It may also contain generic detail items such as tax or markup.
CPNDSUPING http://terminology.hl7.org/CodeSystem/v3-ActCode compound supply invoice group A grouping of invoice element groups and details including the same clinic ones specifying the compound supplies being invoiced. It may cancel also contain generic detail items such as markup.
DRUGING http://terminology.hl7.org/CodeSystem/v3-ActCode drug invoice group A grouping of invoice element details including the one specifying the drug being invoiced. It may also contain generic detail items such as markup.
FRAMEING http://terminology.hl7.org/CodeSystem/v3-ActCode frame invoice group A grouping of invoice element details including the ones specifying the frame fee and reschedule appointments created by other administrators within the frame dispensing cost that clinic; are being invoiced.
LENSING http://terminology.hl7.org/CodeSystem/v3-ActCode lens invoice group A party grouping of invoice element details including the ones specifying the lens fee and the lens dispensing cost that are being invoiced.
PRDING http://terminology.hl7.org/CodeSystem/v3-ActCode product invoice group 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.
_ActInvoiceRootGroupCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceRootGroupCode Type of invoice element that is neither used to assist in describing an author nor Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a party who 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. Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, specified for the root (top level) invoice element group for an Invoice.
CPINV http://terminology.hl7.org/CodeSystem/v3-ActCode clinical product invoice Clinical product invoice where the Invoice Grouping contains one or follow more billable item and is supported by clinical product(s). For example, a crutch or a wheelchair.
CSINV http://terminology.hl7.org/CodeSystem/v3-ActCode clinical service invoice Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. [1] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). [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. For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. [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. 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).
CSPINV http://terminology.hl7.org/CodeSystem/v3-ActCode clinical service and product 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). All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. For example , a brace (product) invoiced together with the fitting (service).
FININV http://terminology.hl7.org/CodeSystem/v3-ActCode financial invoice Invoice Grouping without clinical justification. These will not require identification of participants and associations from a clinical context such as patient and provider. Examples are interest charges and mileage.
OHSINV http://terminology.hl7.org/CodeSystem/v3-ActCode oral health service 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). All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator.
PAINV http://terminology.hl7.org/CodeSystem/v3-ActCode preferred accommodation invoice HealthCare facility preferred accommodation invoice.
RXCINV http://terminology.hl7.org/CodeSystem/v3-ActCode Rx compound invoice Pharmacy dispense invoice for a compound.
RXDINV http://terminology.hl7.org/CodeSystem/v3-ActCode Rx dispense invoice Pharmacy dispense invoice not involving a compound
SBFINV http://terminology.hl7.org/CodeSystem/v3-ActCode sessional or block fee invoice Clinical services invoice where the Invoice Group contains one billable item for multiple clinical services in one or more sessions.
VRXINV http://terminology.hl7.org/CodeSystem/v3-ActCode vision dispense invoice Vision dispense invoice for up to 2 lens (left and right), frame and optional discount. Eye exams are invoiced as a clinical service invoice.
_ActInvoiceElementSummaryCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceElementSummaryCode 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.
_InvoiceElementAdjudicated http://terminology.hl7.org/CodeSystem/v3-ActCode InvoiceElementAdjudicated 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.
ADNFPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified prior-period electronic amount 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 other ways the specified period and submitted electronically.
ADNFPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified prior-period electronic count Identifies the total number of all Invoice Groupings that were adjudicated as payable prior to the specified time period (based on this Act, whereby adjudication date), subsequently cancelled in the Act remains intact specified period and submitted electronically.
ADNFPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified prior-period manual amount 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.
ADNFPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified prior-period manual count 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.
ADNFSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified same-period electronic amount 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.
ADNFSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified same-period electronic count 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.
ADNFSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified same-period manual amount 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.
ADNFSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. nullified same-period manual count 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.
ADNPPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable prior-period electronic amount 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.
ADNPPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable prior-period electronic count 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.
ADNPPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable prior-period manual amount 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.
ADNPPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable prior-period manual count 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.
ADNPSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable same-period electronic amount 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.
ADNPSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable same-period electronic count 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.
ADNPSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable same-period manual amount 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.
ADNPSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. non-payee payable same-period manual count 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.
ADPPPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable prior-period electronic amount 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.
ADPPPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable prior-period electronic count 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.
ADPPPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable prior-period manual amout 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.
ADPPPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable prior-period manual count 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.
ADPPSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable same-period electronic amount 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.
ADPPSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable same-period electronic count 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.
ADPPSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable same-period manual amount 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.
ADPPSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. payee payable same-period manual count 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.
ADRFPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused prior-period electronic amount 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.
ADRFPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused prior-period electronic count 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.
ADRFPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused prior-period manual amount 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.
ADRFPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused prior-period manual count 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.
ADRFSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused same-period electronic amount 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.
ADRFSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused same-period electronic count 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.
ADRFSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused same-period manual amount 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.
ADRFSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode adjud. refused same-period manual count 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.
_InvoiceElementPaid http://terminology.hl7.org/CodeSystem/v3-ActCode InvoiceElementPaid Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date.
PDNFPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified prior-period electronic amount 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.
PDNFPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified prior-period electronic count 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.
PDNFPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified prior-period manual amount 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.
PDNFPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified prior-period manual count 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.
PDNFSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified same-period electronic amount 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.
PDNFSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified same-period electronic count 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.
PDNFSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified same-period manual amount 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.
PDNFSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid nullified same-period manual count 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.
PDNPPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable prior-period electronic amount 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.
PDNPPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable prior-period electronic count 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.
PDNPPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable prior-period manual amount 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.
PDNPPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable prior-period manual count 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.
PDNPSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable same-period electronic amount 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.
PDNPSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable same-period electronic count 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.
PDNPSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable same-period manual amount 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.
PDNPSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid non-payee payable same-period manual count 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.
PDPPPPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable prior-period electronic amount 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.
PDPPPPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable prior-period electronic count 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.
PDPPPPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable prior-period manual amount 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.
PDPPPPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable prior-period manual count 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.
PDPPSPELAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable same-period electronic amount 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.
PDPPSPELCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable same-period electronic count 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.
PDPPSPMNAT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable same-period manual amount 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.
PDPPSPMNCT http://terminology.hl7.org/CodeSystem/v3-ActCode paid payee payable same-period manual count 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.
_InvoiceElementSubmitted http://terminology.hl7.org/CodeSystem/v3-ActCode InvoiceElementSubmitted Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included.
SBBLELAT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted billed electronic amount Identifies the total net amount billed for all submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included.
SBBLELCT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted billed electronic count Identifies the total number of submitted Invoice Groupings within a time period and submitted electronically. Adjudicated invoice elements are included.
SBNFELAT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted nullified electronic amount 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.
SBNFELCT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted cancelled electronic count Identifies the total number of submitted Invoice Groupings that were nullified within a time period and submitted electronically. Adjudicated invoice elements are included.
SBPDELAT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted pending electronic amount 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.
SBPDELCT http://terminology.hl7.org/CodeSystem/v3-ActCode submitted pending electronic count 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.
_ActInvoiceOverrideCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActInvoiceOverrideCode 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.
COVGE http://terminology.hl7.org/CodeSystem/v3-ActCode coverage problem Insurance coverage problems have been encountered. Additional explanation information to be supplied.
EFORM http://terminology.hl7.org/CodeSystem/v3-ActCode electronic form to follow Electronic form with supporting or additional information to follow.
FAX http://terminology.hl7.org/CodeSystem/v3-ActCode fax to follow Fax with supporting or additional information to follow.
GFTH http://terminology.hl7.org/CodeSystem/v3-ActCode good faith indicator 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.
LATE http://terminology.hl7.org/CodeSystem/v3-ActCode late invoice 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.
MANUAL http://terminology.hl7.org/CodeSystem/v3-ActCode manual review Manual review of the invoice is linked requested. Additional information to be supplied. This may be used in the case of an appeal.
OOJ http://terminology.hl7.org/CodeSystem/v3-ActCode out of jurisdiction The medical service and/or product was provided to a patient that has coverage in another Act authored jurisdiction.
ORTHO http://terminology.hl7.org/CodeSystem/v3-ActCode orthodontic service The service provided is required for orthodontic purposes. If the covered party has orthodontic coverage, then the service may be paid.
PAPER http://terminology.hl7.org/CodeSystem/v3-ActCode paper documentation to follow Paper documentation (or other physical format) with supporting or additional information to follow.
PIE http://terminology.hl7.org/CodeSystem/v3-ActCode public insurance exhausted 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.
PYRDELAY http://terminology.hl7.org/CodeSystem/v3-ActCode delayed by a previous payor Allows provider to explain lateness of invoice to a subsequent payor.
REFNR http://terminology.hl7.org/CodeSystem/v3-ActCode referral not required Rules of practice do not require a physician's referral for the provider to perform a billable service.
REPSERV http://terminology.hl7.org/CodeSystem/v3-ActCode repeated service The same service was delivered within a time period that other party. would usually indicate a duplicate billing. However, the repeated service is a medical necessity and therefore not a duplicate.
INF UNRELAT http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode informant unrelated service A 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.
VERBAUTH http://terminology.hl7.org/CodeSystem/v3-ActCode verbal authorization The provider has received a verbal permission from an authoritative source to perform the service or supply the item being invoiced.
_ActListCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActListCode Provides codes associated with ActClass value of reported information (e.g., LIST (working list)
_ActObservationList http://terminology.hl7.org/CodeSystem/v3-ActCode ActObservationList ActObservationList
CARELIST http://terminology.hl7.org/CodeSystem/v3-ActCode care plan List of acts representing a next 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 kin who answers questions about the patient's history). For history questions, care plan.
CONDLIST http://terminology.hl7.org/CodeSystem/v3-ActCode condition list List of condition observations.
INTOLIST http://terminology.hl7.org/CodeSystem/v3-ActCode intolerance list List of intolerance observations.
PROBLIST http://terminology.hl7.org/CodeSystem/v3-ActCode problem list List of problem observations.
RISKLIST http://terminology.hl7.org/CodeSystem/v3-ActCode risk factors List of risk factor observations.
GOALLIST http://terminology.hl7.org/CodeSystem/v3-ActCode goal list List of observations in goal mood.
_ActTherapyDurationWorkingListCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActTherapyDurationWorkingListCode Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed".
_ActMedicationTherapyDurationWorkingListCode http://terminology.hl7.org/CodeSystem/v3-ActCode act medication therapy duration working list Definition:A collection of concepts that identifies different types of 'duration-based' mediation working lists. Examples:"Continuous/Chronic" "Short-Term" and "As Needed"
ACU http://terminology.hl7.org/CodeSystem/v3-ActCode short term/acute Definition:A list of medications which the patient is logically an informant, yet only expected to consume for the informant duration of the current order or limited set of orders and which is not expected to be renewed.
CHRON http://terminology.hl7.org/CodeSystem/v3-ActCode continuous/chronic 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.
ONET http://terminology.hl7.org/CodeSystem/v3-ActCode one time Definition:A list of medications which the patient is intended to be administered only once.
PRN http://terminology.hl7.org/CodeSystem/v3-ActCode as needed Definition:A list of medications which the patient will consume intermittently based on the behavior of the condition for which the medication is indicated.
MEDLIST http://terminology.hl7.org/CodeSystem/v3-ActCode medication list List of medications.
CURMEDLIST http://terminology.hl7.org/CodeSystem/v3-ActCode current medication list List of current medications.
DISCMEDLIST http://terminology.hl7.org/CodeSystem/v3-ActCode discharge medication list List of discharge medications.
HISTMEDLIST http://terminology.hl7.org/CodeSystem/v3-ActCode medication history questions Historical list of medications.
_ActMonitoringProtocolCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActMonitoringProtocolCode Identifies types of monitoring programs
CTLSUB http://terminology.hl7.org/CodeSystem/v3-ActCode Controlled Substance A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction.
INV http://terminology.hl7.org/CodeSystem/v3-ActCode investigational Definition:A monitoring program that focuses on a drug which is implicitly under investigation and has not received regulatory approval for the subject. condition being investigated
TRANS LU http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode Transcriber limited use An Description:A drug that can be prescribed (and reimbursed) only if it meets certain criteria.
OTC http://terminology.hl7.org/CodeSystem/v3-ActCode non prescription medicine Medicines designated in this way may be supplied for patient use without a prescription. The exact form of categorisation will vary in different realms.
RX http://terminology.hl7.org/CodeSystem/v3-ActCode prescription only medicine 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.
SA http://terminology.hl7.org/CodeSystem/v3-ActCode special authorization Definition:A drug that requires prior approval (to be reimbursed) before being dispensed
SAC http://terminology.hl7.org/CodeSystem/v3-ActCode special access Description:A drug that requires special access permission to be prescribed and dispensed.
_ActNonObservationIndicationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActNonObservationIndicationCode Description:Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms.
IND01 http://terminology.hl7.org/CodeSystem/v3-ActCode imaging study requiring contrast Description:Contrast agent required for imaging study.
IND02 http://terminology.hl7.org/CodeSystem/v3-ActCode colonoscopy prep Description:Provision of prescription or direction to consume a product for purposes of bowel clearance in preparation for a colonoscopy.
IND03 http://terminology.hl7.org/CodeSystem/v3-ActCode prophylaxis Description:Provision of medication as a preventative measure during a treatment or other period of increased risk.
IND04 http://terminology.hl7.org/CodeSystem/v3-ActCode surgical prophylaxis Description:Provision of medication during pre-operative phase; e.g., antibiotics before dental surgery or bowel prep before colon surgery.
IND05 http://terminology.hl7.org/CodeSystem/v3-ActCode pregnancy prophylaxis Description:Provision of medication for pregnancy --e.g., vitamins, antibiotic treatments for vaginal tract colonization, etc.
_ActObservationVerificationType http://terminology.hl7.org/CodeSystem/v3-ActCode act observation verification Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity. Examples: Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program Verification of record - e.g., person has record in an immunization registry Verification of enumeration - e.g. NPI Verification of Board Certification - provider specific Verification of Certification - e.g. JAHCO, NCQA, URAC Verification of Conformance - e.g. entity entering use with HIPAA, conformant to the CCHIT EHR system criteria Verification of Provider Credentials Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB)
VFPAPER http://terminology.hl7.org/CodeSystem/v3-ActCode verify paper Definition:Indicates that the paper version of the record has, should be or is being verified against the electronic version.
_ActPaymentCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActPaymentCode Code identifying the method or the movement of payment instructions. Codes are drawn from X12 data element 591 (PaymentMethodCode)
ACH http://terminology.hl7.org/CodeSystem/v3-ActCode Automated Clearing House Automated Clearing House (ACH).
CHK http://terminology.hl7.org/CodeSystem/v3-ActCode Cheque A written order to a bank to pay the amount specified from funds on deposit.
DDP http://terminology.hl7.org/CodeSystem/v3-ActCode Direct Deposit Electronic Funds Transfer (EFT) deposit into the originating system. The data entry entity payee's bank account
NON http://terminology.hl7.org/CodeSystem/v3-ActCode Non-Payment Data Non-Payment Data.
_ActPharmacySupplyType http://terminology.hl7.org/CodeSystem/v3-ActCode ActPharmacySupplyType Identifies types of dispensing events
DF http://terminology.hl7.org/CodeSystem/v3-ActCode Daily Fill A fill providing sufficient supply for one day
EM http://terminology.hl7.org/CodeSystem/v3-ActCode Emergency Supply A supply action where there is collected optionally no 'valid' order for internal quality control purposes. This the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription)
SO http://terminology.hl7.org/CodeSystem/v3-ActCode Script Owing An emergency supply where the expectation is that a formal order authorizing the supply will be provided at a later date.
FF http://terminology.hl7.org/CodeSystem/v3-ActCode First Fill The initial fill against an order. (This includes initial fills against refill orders.)
FFC http://terminology.hl7.org/CodeSystem/v3-ActCode First Fill - Complete A first fill where the transcriptionist 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 dictated text transcribed into electronic form. the full 90 tablets).
ENT FFP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode data entry person First Fill - Part Fill A person entering first fill where the data into quantity supplied is less than one full repetition of the originating system. ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.)
FFSS http://terminology.hl7.org/CodeSystem/v3-ActCode first fill, partial strength 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).
TF http://terminology.hl7.org/CodeSystem/v3-ActCode Trial Fill A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance.
FS http://terminology.hl7.org/CodeSystem/v3-ActCode Floor stock A supply action to restock a smaller more local dispensary.
MS http://terminology.hl7.org/CodeSystem/v3-ActCode Manufacturer Sample A supply of a manufacturer sample
RF http://terminology.hl7.org/CodeSystem/v3-ActCode Refill A fill against an order that has already been filled (or partially filled) at least once.
UD http://terminology.hl7.org/CodeSystem/v3-ActCode Unit Dose A supply action that provides sufficient material for a single dose.
RFC http://terminology.hl7.org/CodeSystem/v3-ActCode Refill - Complete 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.)
RFCS http://terminology.hl7.org/CodeSystem/v3-ActCode refill complete partial strength 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).
RFF http://terminology.hl7.org/CodeSystem/v3-ActCode Refill (First fill this facility) The data entry person first fill against an order that has already been filled at least once at another facility.
RFFS http://terminology.hl7.org/CodeSystem/v3-ActCode refill partial strength (first fill this facility) The first fill against an order that has already been filled at least once at another facility and where the strength supplied is collected optionally less than the ordered strength (e.g. 10mg for internal quality control purposes. This includes an order of 50mg where a subsequent fill will dispense 40mg tablets).
RFP http://terminology.hl7.org/CodeSystem/v3-ActCode Refill - Part Fill A refill where the transcriptionist 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.)
RFPS http://terminology.hl7.org/CodeSystem/v3-ActCode refill part fill partial strength 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).
RFS http://terminology.hl7.org/CodeSystem/v3-ActCode refill partial strength 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).
TB http://terminology.hl7.org/CodeSystem/v3-ActCode Trial Balance A fill where the remainder of a 'complete' fill is provided after a trial fill has been provided.
TBS http://terminology.hl7.org/CodeSystem/v3-ActCode trial balance partial strength 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).
UDE http://terminology.hl7.org/CodeSystem/v3-ActCode unit dose equivalent A supply action that provides sufficient material for a single dose via multiple products. E.g. 2 50mg tablets for a 100mg unit dose.
_ActPolicyType http://terminology.hl7.org/CodeSystem/v3-ActCode ActPolicyType 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 text. and enforced by an authority of competent jurisdiction.
WIT _ActConsent http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode witness _ActConsent Only 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. Usage Note: Types or actual definitions of a contractually binding agreement or a non-binding representation of that agreement include: _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.
_ActDecision http://terminology.hl7.org/CodeSystem/v3-ActCode _ActDecision 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. 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. Examples: 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 events. 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.
GRANTORCHOICE http://terminology.hl7.org/CodeSystem/v3-ActCode grantor choice 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. 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. 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". Examples: 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.
IMPLIED http://terminology.hl7.org/CodeSystem/v3-ActCode implied consent 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. Comment: Implied or "implicit" consent occurs when the behavior of the grantor is understood by a reasonable person witnessing to signal agreement to the action happening grantee's terms. Usage Note: Implied consent with no opportunity to assent or dissent to certain terms is considered "basic consent". Examples: 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 doing anything. explicitly consenting to undergoing field sobriety tests. A witness 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.
IMPLIEDD http://terminology.hl7.org/CodeSystem/v3-ActCode implied consent with opportunity to dissent 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. Comment: A grantor assenting to the grantee's terms of agreement may or may not necessarily aware, much less exercise a right to dissent to grantor selected terms or to grantee's selected terms to which a grantor may dissent. 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". Examples: Healthcare Examples: A healthcare provider deems a patient's assent to disclosure of anything stated 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.
NOCONSENT http://terminology.hl7.org/CodeSystem/v3-ActCode no consent No notification or opportunity is provided for a grantor to assent or dissent to a grantee's terms of agreement. 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. 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. Examples: 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 service event. Example 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 witness 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.
OPTIN http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is students watching considered "basic consent". Examples: 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 operation employer's [grantee's] non-disclosure and non-compete agreement.
OPTINR http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in with restrictions 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. 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. Usage Note: Opt-in with restrictions is considered "granular consent" because the grantor has an advanced opportunity to narrow the permissions sought by the grantee. Examples: Healthcare: A patient assent to grantee's consent directive witness. 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.
CST OPTOUT http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode custodian op-out A grantor's dissent to the terms of agreement offered by a grantee without an opportunity for to assent to any terms. 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. Usage Note: Opt-out with no opportunity for a grantor to permit certain permissions sought by the grantee is considered "basic consent". Examples: 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 entity (person, organization employee [grantor] refuses to sign an employer's [grantee's] agreement not to join unions or device) 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.
OPTOUTE http://terminology.hl7.org/CodeSystem/v3-ActCode opt-out with exceptions A grantor's dissent to the grantee's terms of agreement except for certain grantor or grantee selected terms. 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. 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. Examples: 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.
_ActPrivacyConsentDirective http://terminology.hl7.org/CodeSystem/v3-ActCode _ActPrivacyConsentDirective 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.
_ActGDPRConsentDirective http://terminology.hl7.org/CodeSystem/v3-ActCode _ActGDPRConsentDirective European Union General Data Protection Regulation (GDPR) consent directives.
GDPRCD http://terminology.hl7.org/CodeSystem/v3-ActCode GDPR Consent Directive 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. 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 charge the context of maintaining a written declaration which also concerns other matters, the information 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 (e.g., who maintains establishing a freely given, specific, informed and unambiguous indication of the report 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 master service catalog item, etc.). for which it is provided. 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 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
DIR GDPRResearchCD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode direct target GDPR Research Consent Directive Target participant 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. GDPR research consent directive has the additional caveat that it is substantially present 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 act opportunity to give their consent only to certain areas of research or parts of research projects to the extent allowed by the intended purpose. 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/
_ActGenericConsentDirective http://terminology.hl7.org/CodeSystem/v3-ActCode _ActGenericConsentDirective 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. 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. 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.
OIC http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in to personal information or effect collection in a registry or repository 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. Usage Note: Useful when a more specific jurisdictional or organizational consent directive policy or form is directly involved 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. 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�.
OIS http://terminology.hl7.org/CodeSystem/v3-ActCode opt-in to personal information or effect sharing via a registry or repository 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. 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 action (includes consumed individual’s information by multiple registries and repositories. 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�.
OOC http://terminology.hl7.org/CodeSystem/v3-ActCode opt-out of personal information or effect collection in a registry or repository 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, devices, etc.). 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. 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. 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�.
ALY OOS http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode analyte opt-out of personal information or effect sharing via a registry or repository The target 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 Observation action. Links individual in a registry or repository for purposes such as treatment, payment, operations, research, information exchange, public health, data analytics, marketing, and profiling. 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 observation individual wishes to opt-out of access, use, or disclosure of some or all of the individual’s information by multiple registries and repositories. 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�.
_ActUSPrivacyConsentDirective http://terminology.hl7.org/CodeSystem/v3-ActCode _ActUSPrivacyConsentDirective Specific US privacy consent directives in accordance with US federal, state, regional, organizational, or personal privacy policies.
42CFRPart2CD http://terminology.hl7.org/CodeSystem/v3-ActCode 42 CFR Part 2 consent directive 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-title42-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 Role whose player disclosure under the regulations in Part 2. (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 most specific component (ii)Entities with a treating provider relationship with the patient. If the recipient entity (material, micro-organism, etc.) has a treating provider relationship with the patient whose information is being measured within disclosed, such as a hospital, a health care clinic, or a private practice, the subject. Examples: 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 "plasma porcelain substance concentration" general designation of an individual or entity participant(s) or class of participants that must be limited to a participant(s) who has analyte a Role treating provider relationship with player substance Entity "porcelain". UsageNotes: The Role 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 participation connects part, they must be provided a list of entities to may 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 any Role whose player limited to that information which is necessary to carry out the stated purpose. (6) A statement that substance measured. Very often, the scoper may indicate consent is subject to revocation at any time except to the system 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 component 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 being measured. E.g., provided. (8) The signature of the patient and, when required for "plasma porcelain" a patient who is a minor, the scoper could be "Plasma". 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. 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. 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-vol1/pdf/CFR-2017-title45-vol1-sec164-506.pdf, assign the HL7 Confidentiality code “R� (restricted).
BBY CompoundResearchCD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode baby Compound HIPAA Research Authorization and Informed Consent for Research 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. 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. 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 obstetric service, individual’s right of access directive under 45 CFR Section 164.508 use “CompoundResearchCD� as the baby. 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). 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
CAT HIPAAAuthCD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode catalyst HIPAA Authorization Consent Directive 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. 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. 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-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html 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 catalyst 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 chemical reaction, 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 as 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 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 enzyme individual’s HIPAA Authorization for Disclosure, use “HIPAAAuthCD� as the security label policy code. 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.gov/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).
HIPAAConsentCD http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Consent Directive 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 platinum surface. 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." Usage Note: Used to indicate the legal authority for assigning security labels to governed information. In biochemical reactions, connects 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 enzyme security label policy code. 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-vol1-sec164-506.pdf, assign the HL7 Confidentiality code “R� (restricted).
HIPAAResearchAuthCD http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Authorization for Disclosure for Research Consent Directive 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 molecular interaction policy elements of a valid authorization under this Section specific to disclosures for purposes of research. 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. 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). 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
CSM HIPAAROAD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode consumable HIPAA Right of Access Directive Participant material 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-title45-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. 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/CFR-2017-title45-vol1-sec164-524.pdf This right applies to PHI in a designated record set, which is taken up, diminished, altered, defined as “Designated record set means: (1) A group of records maintained by or disappears 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 act. 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#maximumflatfee]. 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. 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.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.
TPA MDHHS-5515 http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode therapeutic agent Michigan Consent to Share Behavioral Health Information for Care Coordination Purposes Something incorporated 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. 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
_ActInformationActionPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode _ActInformationActionPolicy The type of action permitted on information by jurisdictional, organizational, or personal policy.
INFOACCESS http://terminology.hl7.org/CodeSystem/v3-ActCode access information Authorization to obtain information with no further permission to collect and store it.
INFOCOLLECT http://terminology.hl7.org/CodeSystem/v3-ActCode collect information Authorization to gather and store information.
INFODEIDENTIFIY http://terminology.hl7.org/CodeSystem/v3-ActCode deidentify information Authorization to alter or remove identifying characteristics of an entity or individual that is a subject of the information.
INFODISCLOSE http://terminology.hl7.org/CodeSystem/v3-ActCode disclose information Authorization to make information known to another party.
INFOMASK http://terminology.hl7.org/CodeSystem/v3-ActCode mask information Authorization to alter information in order to conceal it from unauthorized recipients.
INFOREADONLY http://terminology.hl7.org/CodeSystem/v3-ActCode read only information Authorization to access information within a specific context for communication purposes only. Storing, manipulating, and further disclosure are prohibited and may be technically disabled.
INFOREDACT http://terminology.hl7.org/CodeSystem/v3-ActCode redact information Authorization to remove information that a recipient is not authorized to access.
INFOREDISCLOSE http://terminology.hl7.org/CodeSystem/v3-ActCode redisclose information Authorization to make disclosed information known to another party.
INFOREIDENTIFY http://terminology.hl7.org/CodeSystem/v3-ActCode reidentify information Authorization to alter or relink deidentified information so that an entity or individual that is the subject of that information identifiable.
INFOUSE http://terminology.hl7.org/CodeSystem/v3-ActCode use information Authorization to employ or alter information.
_ActInformationPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode _ActInformationPolicy 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 therapy community of interest; or terms of license, participation, or service to achieve as implemented in jurisdictional, organizational, or personal policies.
JurisIP http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional information policy Jurisdictional policy on collection, access, use, or disclosure of information as defined by applicable jurisdictional law.
JurisCUI http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional controlled unclassified information policy Jurisdictional policy on collection, access, use, or disclosure of controlled unclassified information as defined by applicable jurisdictional law.
JurisDEID http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional de-identified information policy Jurisdictional policy on collection, access, use, or disclosure of de-identified information as defined by applicable jurisdictional law.
JurisLDS http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional limited data set Jurisdictional policy on collection, access, use, or disclosure of information in a physiologic effect (e.g., heal, relieve, provoke limited data set as defined by applicable jurisdictional law.
JurisNSI http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional non-sensitive information policy Jurisdictional policy on collection, access, use, or disclosure of information deemed non-sensitive by applicable jurisdiction law.
JurisPI http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional public information policy Jurisdictional policy on collection, access, use, or disclosure of information deemed public by applicable jurisdiction law.
JurisSP-CUI http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional specified controlled unclassified information policy Jurisdictional policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by applicable jurisdictional policy.
JurisUUI http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdictional uncontrolled unclassified information policy Jurisdictional policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by applicable jurisdictional policy.
OrgIP http://terminology.hl7.org/CodeSystem/v3-ActCode organizational information policy Organizational policy on collection, access, use, or disclosure of information, which does not conflict with jurisdictional law.
OrgCUI http://terminology.hl7.org/CodeSystem/v3-ActCode organizational basic controlled unclassified information policy Organizational policy on collection, access, use, or disclosure of basic controlled unclassified information as defined by the organization or by applicable jurisdictional law.
OrgDEID http://terminology.hl7.org/CodeSystem/v3-ActCode organizational de-identified informati)on policy Organizational policy on collection, access, use, or disclosure of de-identified information as defined by the organization or by applicable jurisdictional law.
OrgLDS http://terminology.hl7.org/CodeSystem/v3-ActCode organizational limited data set information policy Organizational policy on collection, access, use, or disclosure of information in a condition, etc.) limited data set as defined by the organization or by applicable jurisdictional law.
OrgNSI http://terminology.hl7.org/CodeSystem/v3-ActCode organizational non-sensitive information policy Organizational policy on collection, access, use, or disclosure of information deemed non-sensitive by the organization or by applicable jurisdictional law.
OrgPI http://terminology.hl7.org/CodeSystem/v3-ActCode organizational public information policy Organizational policy on collection, access, use, or disclosure of public information as defined by the organization or by applicable jurisdictional law.
OrgSP-CUI http://terminology.hl7.org/CodeSystem/v3-ActCode organizational specified controlled unclassified information policy Organizational policy on collection, access, use, or disclosure of specified controlled unclassified information as defined by the organization or by applicable jurisdictional law.
OrgUUI http://terminology.hl7.org/CodeSystem/v3-ActCode organizational uncontrolled unclassified information policy Organizational policy on collection, access, use, or disclosure of uncontrolled unclassified information as defined by the organization or governing jurisdiction.
PersIP http://terminology.hl7.org/CodeSystem/v3-ActCode personal information policy Personal policy on collection, access, use, or disclosure of information.
PersDEID http://terminology.hl7.org/CodeSystem/v3-ActCode personal de-identified information policy Personal policy on collection, access, use, or disclosure of de-identified information as defined by the information subject or by applicable jurisdictional law.
PersLDS http://terminology.hl7.org/CodeSystem/v3-ActCode personal limited data set information policy Personal policy personal policy on collection, access, use, or disclosure of information in a limited data set by the information subject. In
PersNSI http://terminology.hl7.org/CodeSystem/v3-ActCode personal non-sensitive information policy Personal policy on collection, access, use, or disclosure of information deemed non-sensitive by the information subject.
PersPI http://terminology.hl7.org/CodeSystem/v3-ActCode personal public information policy Personal policy on collection, access, use, or disclosure of information deemed public by the information subject.
_ActPrivacyPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode ActPrivacyPolicy A policy deeming certain information to be private to an administration service individual or organization. Definition: A mandate, obligation, requirement, rule, or expectation relating to privacy. Discussion: ActPrivacyPolicyType codes support the therapeutic agent is designation of the 1..* policies that are applicable to an Act such as a consumable, in Consent Directive, a preparation Role such as a VIP Patient, or dispense service, it an Entity such as a patient who is a product. Thus, consumable minor. 1..* ActPrivacyPolicyType values may be associated with an Act or product 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. Usage Note: Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced.
EMRGONLY http://terminology.hl7.org/CodeSystem/v3-ActCode emergency only 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. 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 accordance with the kind ActReason code system OID: 2.16.840.1.113883.5.8. ETREAT (Emergency Treatment): To perform one or more operations on information for provision of service. 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
DEV NOPP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode device notice of privacy practices Participant 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 performing a registry or repository. The notification specifies the act without being substantially affected 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. 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".
_ActPrivacyLaw http://terminology.hl7.org/CodeSystem/v3-ActCode ActPrivacyLaw A jurisdictional mandate, regulation, obligation, requirement, rule, or expectation deeming certain information to be private to an individual or organization, which is imposed on: The activity of a governed party The behavior of a governed party The manner in which an act (i.e. durable is executed by a governed party
_ActGDPRPrivacyLaw http://terminology.hl7.org/CodeSystem/v3-ActCode General Data Protection Regulation 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. GDPR privacy policies specifying types of lawful personal data processing based on a controller meeting one or inert more processing condition such as specified by law, compliance with respect data controller legal obligations, protection of data subject’s vital interests, perform tasks in the public interest, related to that particular service). Examples: monitoring equipment, tools, but also access/drainage lines, prostheses, pace maker, etc. 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. 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/ Usage Note: 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-info.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/ Authorities 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-reform-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/
NRD GDPRCONSENT http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode non-reuseable device GDPR Consent A device 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 changes ownership due the prohibition to use the service, e.g., data may not be lifted by the data subject; and for personal data which are manifestly made public by the data subject. 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 pacemaker, natural person, data concerning health or data concerning a prosthesis, an insulin injection equipment (pen), etc. Such material 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 need not be lifted by the data subject; and (e) processing relates to personal data which are manifestly made public by the data subject.
_ActUSPrivacyLaw http://terminology.hl7.org/CodeSystem/v3-ActCode _ActUSPrivacyLaw Definition: A jurisdictional mandate in the U.S. relating to privacy. Usage Note: ActPrivacyLaw codes may be restocked after he service. 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.
RDV 42CFRPart2 http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode reusable device 42 CFR Part2 A device 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-part2.pdf 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. 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).
a) HIPAAConsent http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Consent 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 change ownership due 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-difference-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-sec164-522.pdf. Usage Note: Used to indicate the service, i.e., 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. Since information governed by a surgical instrument 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 tool 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).
CommonRule http://terminology.hl7.org/CodeSystem/v3-ActCode Common Rule 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. 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).
HIPAAAuth http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Authorization for Disclosure 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 endoscope. The distinction between reuseable authorization is required https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-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". An “authorization� is required by the Privacy Rule for uses and non-reuseable 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. An authorization must specify a number of elements, including a description of the protected health information to be made 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 order 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-professionals/faq/264/what-is-the-difference-between-consent-and-authorization/index.html Usage Note: Used to know whether material must 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. 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 re-stocked. protected under other laws such as the Federal Trade Commission privacy and security regulations.
DON HIPAANOPP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode donor HIPAA notice of privacy practices 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 Usage Note: Used to indicate the legal authority for assigning security labels to HIPAA governed information. In some organ transplantation services 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. 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 rarely in transfusion services 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 , which is considered the “norm�, assign the HL7 Confidentiality code “N� (normal).
HIPAAPsyNotes http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA psychotherapy notes 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. Definition of Psychotherapy notes 45 CFR Section 164.501 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-501.pdf: Psychotherapy notes means notes recorded (in any medium) by a donor will be health care provider who is a target participant 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. 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-title45-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 service. However, 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 most cases transplantation 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 decomposed 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). 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-title45-vol1-sec164-506.pdf , use “HIPAAPsyNotes� as the security label policy code. 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).
HIPAAROA http://terminology.hl7.org/CodeSystem/v3-ActCode HIPAA Right of Access 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-title45-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 three services: explantation, transport, 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 implantation. information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding. 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 identity 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. 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.html 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 Usage Note: Used to indicate the donor (recipient) is often irrelevant 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 explantation (implantation) service. security label policy code. 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.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.
EXPAGNT HIPAASelfPay http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode ExposureAgent HIPAA self-pay Description: 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. See 45 CFR 164.522 https://www.gpo.gov/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-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 playing in full. Usage Note: Used to indicate the associated role 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/fdsys/pkg/CFR-2017-title45-vol1/pdf/CFR-2017-title45-vol1-sec164-522.pdf use “HIPAASelfPay� as the physical (including energy), chemical security label policy code. 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 biological 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).
Title38Section7332 http://terminology.hl7.org/CodeSystem/v3-ActCode Title 38 Section 7332 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. https://www.gpo.gov/fdsys/granule/USCODE-2011-title38/USCODE-2011-title38-partV-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 participating 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 exposure. For example Secretary in communicable diseases, accordance with the associated playing 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 disease causing pathogen. 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'). 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-sec7332/content-detail.html use "Title38Section7332" as the security label policy code. 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-vol1-sec164-506.pdf, assign the HL7 Confidentiality code "R" (restricted).
EXPART _InformationSensitivityPolicy http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode ExposureParticipation InformationSensitivityPolicy Description:Direct participation 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 exposure 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 where it 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 unknown 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 participant sender intends, accomplishing interoperability without point to point negotiations. 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.
_ActInformationSensitivityPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode ActInformationSensitivityPolicy Types of sensitivity policies that apply to Acts. Act.confidentialityCode is defined in the source or subject RIM as "constraints around appropriate disclosure of information about this Act, regardless of mood." 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 exposure. access control system on how end users in that policy domain are able to use information tagged with these sensitivity values.
ETH http://terminology.hl7.org/CodeSystem/v3-ActCode substance abuse information sensitivity 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. Usage Note: If there is a jurisdictional mandate, then use the participant applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
GDIS http://terminology.hl7.org/CodeSystem/v3-ActCode genetic disease information sensitivity 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 known deemed sensitive. 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.
HIV http://terminology.hl7.org/CodeSystem/v3-ActCode HIV/AIDS information sensitivity 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. Usage Note: If there is a jurisdictional mandate, then use the contact applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
MST http://terminology.hl7.org/CodeSystem/v3-ActCode military sexual trauma information sensitivity 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. 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. 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.
PREGNANT http://terminology.hl7.org/CodeSystem/v3-ActCode pregnancy information sensitivity Policy for handling information about an exposure individual's current or past pregnancy status, deemed sensitive by the individual or by policy, which may be afforded heightened confidentiality. Usage Note: 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.
SCA http://terminology.hl7.org/CodeSystem/v3-ActCode sickle cell anemia information sensitivity 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. Usage Note: If there is a jurisdictional mandate, then the SBJ participation type Act valued with this ActCode should be used. If associated with an Act valued with any applicable laws from the participant ActPrivacyLaw code system.
SDV http://terminology.hl7.org/CodeSystem/v3-ActCode sexual assault, abuse, or domestic violence information sensitivity 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 known deemed sensitive. 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 source patient, or may try to manipulate care givers into allowing the perpetrator to make contact with the patient. The definition needs to be clarified. Usage Note: If there is a jurisdictional mandate, then use the EXSRC participation type should applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
SEX http://terminology.hl7.org/CodeSystem/v3-ActCode sexuality and reproductive health information sensitivity 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. 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.
SPI http://terminology.hl7.org/CodeSystem/v3-ActCode specially protected information sensitivity 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. 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.
BH http://terminology.hl7.org/CodeSystem/v3-ActCode behavioral health information sensitivity Policy for handling information related to behavioral and emotional disturbances affecting social adjustment and physical health, which is afforded heightened confidentiality. 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.
COGN http://terminology.hl7.org/CodeSystem/v3-ActCode cognitive disability information sensitivity Policy for handling information related to cognitive disability disorders and conditions caused by these disorders, which are afforded heightened confidentiality. 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. 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.
EXPTRGT DVD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode ExposureTarget developmental disability information sensitivity Description: The entity playing Policy for handling information related to developmental disability disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the associated role applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. 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.
EMOTDIS http://terminology.hl7.org/CodeSystem/v3-ActCode emotional disturbance information sensitivity Policy for handling information related to emotional disturbance disorders and conditions caused by these disorders, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the target (contact) applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. Typical used to characterize behavioral and mental health issues of exposure. adolescents where the disorder may be temporarily diagnosed in order to avoid the potential and unnecessary stigmatizing diagnoses of disorder long term.
EXSRC MH http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode ExposureSource mental health information sensitivity Description:The entity playing 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. Usage Note: If there is a jurisdictional mandate, then use the associated role applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code.
PSY http://terminology.hl7.org/CodeSystem/v3-ActCode psychiatry disorder information sensitivity Policy for handling psychiatry psychiatric disorder information, which is afforded heightened confidentiality. Usage Note: If there is a jurisdictional mandate, then use the source applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
PSYTHPN http://terminology.hl7.org/CodeSystem/v3-ActCode psychotherapy note information sensitivity Policy for handling psychotherapy note information, which is afforded heightened confidentiality. Usage Note: In some jurisdiction, disclosure of exposure. psychotherapy notes requires patient consent. 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.
PRD SUD http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode product substance use disorder information sensitivity Participant material Policy for handling information related to alcohol or drug use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. 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.
ETHUD http://terminology.hl7.org/CodeSystem/v3-ActCode alcohol use disorder information sensitivity Policy for handling information related to alcohol use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. 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.
OPIOIDUD http://terminology.hl7.org/CodeSystem/v3-ActCode opioid use disorder information sensitivity Policy for handling information related to opioid use disorders and conditions caused by these disorders, which is afforded heightened confidentiality. 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.
STD http://terminology.hl7.org/CodeSystem/v3-ActCode sexually transmitted disease information sensitivity 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 brought forth (produced) deemed sensitive. 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.
TBOO http://terminology.hl7.org/CodeSystem/v3-ActCode taboo 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 act (e.g., specimen patient by an attending physician before being disclosed to the patient. 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. Open Issue: This definition conflates a specimen collection, rule and a characteristic, and there may be a similar issue with ts sibling codes.
VIO http://terminology.hl7.org/CodeSystem/v3-ActCode violence information sensitivity Policy for handling information related to harm by violence, which is afforded heightened confidentiality. Harm by violence is perpetrated by an unrelated person. 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 drainage locate the patient, but the perpetrator will likely not have established abusive psychological control over the patient. 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.
SICKLE http://terminology.hl7.org/CodeSystem/v3-ActCode sickle cell 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." 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 placement service, medication package 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.
_EntitySensitivityPolicyType http://terminology.hl7.org/CodeSystem/v3-ActCode EntityInformationSensitivityPolicy Types of sensitivity policies that may apply to a dispense service). It does not matter whether sensitive attribute on an Entity. 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 material produced had existence prior RIM as "an indication of the appropriate disclosure of information about this Role with respect to the service, playing Entity."
DEMO http://terminology.hl7.org/CodeSystem/v3-ActCode all demographic information sensitivity 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 whether it safety of that subject. Usage Note: If there is created a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
DOB http://terminology.hl7.org/CodeSystem/v3-ActCode date of birth information sensitivity 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 service (e.g., disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in supply services addition to this more generic code.
GENDER http://terminology.hl7.org/CodeSystem/v3-ActCode gender and sexual orientation information sensitivity 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 product disclosure of which could impact the privacy, well-being, or safety of that subject. Usage Note: If there is taken from a stock). jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
SBJ LIVARG http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode subject living arrangement information sensitivity The principle target on 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 action happens. Examples: The patient privacy, well-being, or safety of that subject. Usage Note: If there is a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in physical examination, addition to this more generic code.
MARST http://terminology.hl7.org/CodeSystem/v3-ActCode marital status information sensitivity 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. Usage Note: If there is a specimen jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
PATLOC http://terminology.hl7.org/CodeSystem/v3-ActCode patient location 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. Usage Note: If there is a lab observation. May also 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.
RACE http://terminology.hl7.org/CodeSystem/v3-ActCode race information sensitivity 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. Usage Note: If there is a patient's family member (teaching) jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
REL http://terminology.hl7.org/CodeSystem/v3-ActCode religion information sensitivity 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. Usage Notes: If there is a device jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or room (cleaning, disinfecting, housekeeping). UsageNotes: Not all direct targets in addition to this more generic code.
_RoleInformationSensitivityPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode RoleInformationSensitivityPolicy Types of sensitivity policies that apply to Roles. Usage Notes: RoleSensitivity codes are subjects. Consumables and devices used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as tools "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity."
B http://terminology.hl7.org/CodeSystem/v3-ActCode business information sensitivity Policy for an act are not subjects. However, 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 device trade or business secret, there is sometimes (though rarely) the need to flag those items as of business level confidentiality. 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.
EMPL http://terminology.hl7.org/CodeSystem/v3-ActCode employer information sensitivity 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. 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.
LOCIS http://terminology.hl7.org/CodeSystem/v3-ActCode location information sensitivity 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. Usage Notes: If there is a maintenance action. jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
SPC SSP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode specimen sensitive service provider information sensitivity The subject Policy for handling information related to a provider of non-clinical (e.g. laboratory) observation 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. Usage Notes: If there is a specimen. jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
IND ADOL http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode indirect target adolescent information sensitivity Target 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 is not substantially present 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. Usage Note: For use within an enterprise in which an adolescent is the act 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.
CEL http://terminology.hl7.org/CodeSystem/v3-ActCode celebrity information sensitivity 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. Usage Note: For use within an enterprise in which the information subject is not directly affected 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.
DIA http://terminology.hl7.org/CodeSystem/v3-ActCode diagnosis information sensitivity 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. 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 act, but applicable ActPrivacyLaw code system, and specify the law rather than or in addition to this more generic code.
DRGIS http://terminology.hl7.org/CodeSystem/v3-ActCode drug information sensitivity 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. Usage Note: For use within an enterprise that provides heightened confidentiality to drug information deemed sensitive. If there is a focus of jurisdictional mandate, then use the record applicable ActPrivacyLaw code system, and specify the law rather than or documentation in addition to this more generic code.
EMP http://terminology.hl7.org/CodeSystem/v3-ActCode employee information sensitivity 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 the act. kin, and location. 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.
BEN PDS http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode beneficiary patient default information sensitivity Target on behalf Policy for specially protecting information reported by or about a patient, which is deemed sensitive within the enterprise (i.e., by default regardless of whom whether the service happens, but 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. Usage Note: If there is not necessarily present a jurisdictional mandate, then use the applicable ActPrivacyLaw code system, and specify the law in addition to this more generic code. 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.
PHY http://terminology.hl7.org/CodeSystem/v3-ActCode physician requested information sensitivity Policy for handling information about a patient, which a physician or other licensed healthcare provider deems sensitive. Once tagged by the service. Can occur together with direct target provider, this may trigger alerts for follow up actions according to indicate organizational policy or jurisdictional law. Usage Note: For use within an enterprise that provides heightened confidentiality to certain types of information designated by a target is both, 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. Use cases in which this code could be used are, e.g., in systems that lack the case 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.
PRS http://terminology.hl7.org/CodeSystem/v3-ActCode patient requested information sensitivity Policy for specially protecting information reported by or about a patient, which the patient is deems sensitive, and the indirect beneficiary patient requests that collection, access, use, or disclosure of that information be restricted. For example, a service rendered minor patient may request that information about reproductive health not be disclosed to a the patient's family member, e.g. counseling or given home care instructions. to particular providers and payers. 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.
COMPT http://terminology.hl7.org/CodeSystem/v3-ActCode compartment This is the healthcare analog to the US Intelligence Community's concept includes of a participant, such Special Access Program. Compartment codes may be used in as a covered party, 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. 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."
ACOCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode accountable care organization compartment A group of health care entities, which may include health care providers, care givers, hospitals, facilities, health plans, and other health care constituents who derives benefits from 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. Security Compartment Labels assigned to a service act covered consumer's information use in accountable care workflows should be met or exceeded by the Security Compartment attribute claimed by a coverage act. Note participant in a an accountable care workflow who is requesting access to that information
CTCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode care team compartment 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. Security Compartment Labels assigned to a consumer's information use in care coordination workflows should be met or exceeded by the semantic role Security Compartment attribute claimed by a participant in a care team member workflow who is requesting access to that information
FMCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode financial management compartment Financial management department members who have access to healthcare consumer information as part of a patient account, billing and claims workflows. Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the intended recipient Security Compartment attribute claimed by a participant in a financial management workflow who benefits from is requesting access to that information.
HRCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode human resource compartment 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.
LRCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode legitimate relationship compartment 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 happening denoted 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. Security Compartment Labels assigned to a consumer's information use in legitimate relationship workflows should be met or exceeded by the verb Security Compartment attribute claimed by a participant in a legitimate relationship workflow who is requesting access to that information.
PACOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode patient administration compartment Patient administration members who have access to healthcare consumer information as part of a patient administration workflows. Security Compartment Labels assigned to consumer information used in these workflows should be met or exceeded by the clause. Thus, Security Compartment attribute claimed by a participant in a patient administration workflow who has no coverage under is requesting access to that information.
RESCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode research project compartment A security category label field value, which indicates that access and use of an IT resource is restricted to members of a research project.
RMGTCOMPT http://terminology.hl7.org/CodeSystem/v3-ActCode records management compartment 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.
ActTrustPolicyType http://terminology.hl7.org/CodeSystem/v3-ActCode trust policy A mandate, obligation, requirement, rule, or program expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions. Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). 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] For example, identity proofing , level of assurance, and Trust Framework.
TRSTACCRD http://terminology.hl7.org/CodeSystem/v3-ActCode trust accreditation 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 beneficiary security domain or trust framework.
TRSTAGRE http://terminology.hl7.org/CodeSystem/v3-ActCode trust agreement Type of security metadata about privacy and security requirements with which a health service while not being security domain must comply. [ISO IEC 10181-1]
TRSTASSUR http://terminology.hl7.org/CodeSystem/v3-ActCode trust assurance Type of security metadata about the beneficiary digital quality or reliability of coverage a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.
TRSTCERT http://terminology.hl7.org/CodeSystem/v3-ActCode trust certificate 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]
TRSTFWK http://terminology.hl7.org/CodeSystem/v3-ActCode trust framework 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]
TRSTMEC http://terminology.hl7.org/CodeSystem/v3-ActCode trust mechanism Type of security metadata about a security architecture system component that supports enforcement of security policies.
COVPOL http://terminology.hl7.org/CodeSystem/v3-ActCode benefit policy 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: The activity of another party The behavior of another party The manner in which an act is executed 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.
CAGNT SecurityPolicy http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode causative agent security policy Definition: Types of security policies that further specify the ActClassPolicy value set. Examples: obligation to encrypt refrain from redisclosure without consent
AUTHPOL http://terminology.hl7.org/CodeSystem/v3-ActCode authorization policy Authorisation policies are essentially security policies related to access-control and specify what activities a subject is permitted or forbidden to do, to a set of target objects. They are designed to protect target objects so are interpreted by access control agents or the run-time systems at the target system. A factor, such positive authorisation policy defines the actions that a subject is permitted to perform on a target. A negative authorisation policy specifies the actions that a subject is forbidden to perform on a target. Positive authorisation policies may also include filters to transform the parameters associated with their actions. (Based on PONDERS)
ACCESSCONSCHEME http://terminology.hl7.org/CodeSystem/v3-ActCode access control scheme An access control policy specific to the type of access control scheme, which is used to enforce one or more authorization policies. Usage Note: Access control schemes are the type of access control policy, which is comprised of access control policy rules concerning the provision of the access control service. There are two categories of access control policies, rule-based and identity-based, which are identified in CCITT Rec. X.800 aka ISO 7498-2. Rule-based access control policies are intended to apply to all access requests by any initiator on any target in a security domain. Identity-based access control policies are based on rules specific to an individual initiator, a group of initiators, entities acting on behalf of initiators, or originators acting in a specific role. Context can modify rule-based or identity-based access control policies. Context rules may define the entire policy in effect. Real systems will usually employ a combination of these policy types; if a rule-based policy is used, then an identity-based policy is usually in effect also. An access control scheme may be based on access control lists, capabilities, labels, and context or a combination of these. An access control scheme is a component of an access control mechanism or "service") along with the supporting mechanisms required by that scheme to provide access control decision information (ADI) supplied by the scheme to the access decision facility (ADF also known as a microorganism, chemical substance, PDP). (Based on ISO/IEC 10181-3:1996) Examples: Attribute Based Access Control (ABAC) Discretionary Access Control (DAC) History Based Access Control (HBAC) Identity Based Access Control (IBAC) Mandatory Access Control (MAC) Organization Based Access Control (OrBAC) Relationship Based Access Control (RelBac) Responsibility Based Access Control (RespBAC) Risk Adaptable Access Control (RAdAC) >
DELEPOL http://terminology.hl7.org/CodeSystem/v3-ActCode delegation policy Delegation policies specify which actions subjects are allowed to delegate to others. A delegation policy thus specifies an authorisation to delegate. Subjects must already possess the access rights to be delegated. Delegation policies are aimed at subjects delegating rights to servers or form third parties to perform actions on their behalf and are not meant to be the means by which security administrators would assign rights to subjects. A negative delegation policy identifies what delegations are forbidden. A Delegation policy specifies the authorisation policy from which delegated rights are derived, the grantors, which are the entities which can delegate these access rights, and the grantees, which are the entities to which the access rights can be delegated. There are two types of radiation, whose presence, excessive presence, delegation policy, positive and negative. (Based on PONDERS)
ObligationPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode obligation policy Conveys the mandated workflow action that an information custodian, receiver, or (in deficiency diseases) relative absence user must perform. Usage Notes: Per ISO 22600-2, ObligationPolicy instances 'are event-triggered and define actions to be performed by manager agent'. Per HL7 Composite Security and Privacy Domain Analysis Model: This value set refers to the action required to receive the permission specified in the privacy rule. Per OASIS XACML, an obligation is essential, an operation specified in whole a policy or policy that is performed in part, conjunction with the enforcement of an access control decision.
ANONY http://terminology.hl7.org/CodeSystem/v3-ActCode anonymize Custodian system must remove any information that could result in identifying the information subject.
AOD http://terminology.hl7.org/CodeSystem/v3-ActCode accounting of disclosure Custodian system must make available to an information subject upon request an accounting of certain disclosures of the individual’s protected health information over a period of time. Policy may dictate that the accounting include information about the information disclosed, the date of disclosure, the identification of the receiver, the purpose of the disclosure, the time in which the disclosing entity must provide a response and the time period for which accountings of disclosure can be requested.
AUDIT http://terminology.hl7.org/CodeSystem/v3-ActCode audit Custodian system must monitor systems to ensure that all users are authorized to operate on information objects.
AUDTR http://terminology.hl7.org/CodeSystem/v3-ActCode audit trail Custodian system must monitor and maintain retrievable log for each user and operation on information.
CPLYCC http://terminology.hl7.org/CodeSystem/v3-ActCode comply with confidentiality code Custodian security system must retrieve, evaluate, and comply with the occurrence information handling directions of the Confidentiality Code associated with an information target.
CPLYCD http://terminology.hl7.org/CodeSystem/v3-ActCode comply with consent directive Custodian security system must retrieve, evaluate, and comply with applicable information subject consent directives.
CPLYJPP http://terminology.hl7.org/CodeSystem/v3-ActCode comply with jurisdictional privacy policy Custodian security system must retrieve, evaluate, and comply with applicable jurisdictional privacy policies associated with the target information.
CPLYOPP http://terminology.hl7.org/CodeSystem/v3-ActCode comply with organizational privacy policy Custodian security system must retrieve, evaluate, and comply with applicable organizational privacy policies associated with the target information.
CPLYOSP http://terminology.hl7.org/CodeSystem/v3-ActCode comply with organizational security policy Custodian security system must retrieve, evaluate, and comply with the organizational security policies associated with the target information.
CPLYPOL http://terminology.hl7.org/CodeSystem/v3-ActCode comply with policy Custodian security system must retrieve, evaluate, and comply with applicable policies associated with the target information.
DECLASSIFYLABEL http://terminology.hl7.org/CodeSystem/v3-ActCode declassify security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a condition. Constraint: new security label that marks the information as unclassified in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
DEID http://terminology.hl7.org/CodeSystem/v3-ActCode deidentify Custodian system must strip information of data that would allow the identification of the source of the information or the information subject.
DELAU http://terminology.hl7.org/CodeSystem/v3-ActCode delete after use Custodian system must remove target information from access after use.
DOWNGRDLABEL http://terminology.hl7.org/CodeSystem/v3-ActCode downgrade security label Custodian security system must downgrade information assigned security labels by instantiating a new version of this participation the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a less protected level in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
DRIVLABEL http://terminology.hl7.org/CodeSystem/v3-ActCode derive security label Custodian security system must assign and bind security labels derived from compilations of information by aggregation or disaggregation in order to classify information compiled in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target information. The system must retain an immutable record of the previous assignment and binding.
ENCRYPT http://terminology.hl7.org/CodeSystem/v3-ActCode encrypt Custodian system must render information unreadable by algorithmically transforming plaintext into ciphertext. Usage Notes: A mathematical transposition of a file or data stream so that it cannot be deciphered at the receiving end without the proper key. Encryption is limited a security feature that assures that only the parties who are supposed to observations. 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.)
COV ENCRYPTR http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode coverage encrypt at rest Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext when "at rest" or in storage.
ENCRYPTT http://terminology.hl7.org/CodeSystem/v3-ActCode encrypt in transit Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while "in transit" or being transported by any means.
ENCRYPTU http://terminology.hl7.org/CodeSystem/v3-ActCode encrypt in use Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext while in use such that operations permitted on the target information are limited by the license granted to the end user.
HUAPRV The http://terminology.hl7.org/CodeSystem/v3-ActCode human approval Custodian system must require human review and approval for permission requested.
LABEL http://terminology.hl7.org/CodeSystem/v3-ActCode assign security label Custodian security system must assign and bind security labels in order to classify information created in the information systems under its control for collection, access, use and disclosure in accordance with applicable jurisdictional privacy policies associated with the target participation information. The system must retain an immutable record of the assignment and binding. Usage Note: In security systems, security policy label assignments do not change, they may supersede prior assignments, and such reassignments are always tracked for auditing and other purposes.
MASK http://terminology.hl7.org/CodeSystem/v3-ActCode mask Custodian system must render information unreadable and unusable by algorithmically transforming plaintext into ciphertext. User may be provided a key to decrypt per license or "shared secret".
MINEC http://terminology.hl7.org/CodeSystem/v3-ActCode minimum necessary Custodian must limit access and disclosure to the minimum information required to support an individual authorized user's purpose of use. Usage Note: Limiting the information available for access and disclosure to that an authorized user or receiver "needs to know" in a health care coverage act order to perform permitted workflow or purpose of use.
PERSISTLABEL http://terminology.hl7.org/CodeSystem/v3-ActCode persist security label Custodian security system must persist the binding of security labels to classify information received or imported by information systems under its control for collection, access, use and disclosure in which accordance with applicable jurisdictional privacy policies associated with the target role information. The system must retain an immutable record of the assignment and binding.
PRIVMARK http://terminology.hl7.org/CodeSystem/v3-ActCode privacy mark Custodian must create and/or maintain human readable security label tags as required by policy. Map: Aligns with ISO 22600-3 Section A.3.4.3 description of privacy mark: "If present, the privacy-mark is either not used for access control. The content of the privacy-mark may be defined by the security policy holder in force (identified by the security-policy-identifier) which may define a list of values to be used. Alternately, the coverage, value may be determined by the originator of the security-label."
PSEUD http://terminology.hl7.org/CodeSystem/v3-ActCode pseudonymize Custodian system must strip information of data that would allow the identification of the source of the information or the information subject. Custodian may retain a covered party under key to relink data necessary to reidentify the coverage. information subject.
GUAR REDACT http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode guarantor party redact The Custodian system must remove information, which is not authorized to be access, used, or disclosed from records made available to otherwise authorized users.
UPGRDLABEL http://terminology.hl7.org/CodeSystem/v3-ActCode upgrade security label Custodian security system must declassify information assigned security labels by instantiating a new version of the classified information so as to break the binding of the classifying security label when assigning a new security label that marks the information as classified at a more protected level in accordance with applicable jurisdictional privacy policies associated with the target person information. The system must retain an immutable record of the previous assignment and binding.
PrivacyMark http://terminology.hl7.org/CodeSystem/v3-ActCode privacy mark An abstract code for human readable marks indicating, e.g., the level of confidentiality protection, an authorized compartment, the integrity, or organization contractually recognized 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. Examples of protocols for marking displays on electronic or hardcopy rendered content: Across the issuer top or "banner" of each page ; as a participant who has assumed fiscal responsibility 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. 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. Foundational standard definitions: ISO 22600-3 Section A.3.4.3 - If present, the privacy-mark is not used for another personaTMs financial obligations access control. The content of the privacy-mark may be defined by guaranteeing the security policy in force (identified by the security-policy-identifier) which may define a list of values to pay for amounts owed 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 particular account Example:The subscriber document so marked. NOTE: A machine readable representation of a marking. 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 patientaTMs health insurance European Union. For this reason, this code system is likely to evolve with the inclusion of multiple policy signs domains needing to communicate encoded policies in a contract standard, interoperable manner.
ControlledUnclassifiedInformation http://terminology.hl7.org/CodeSystem/v3-ActCode ControlledUnclassifiedInformation 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 provider authority does not specify. Based on CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html . 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.
CONTROLLED http://terminology.hl7.org/CodeSystem/v3-ActCode CONTROLLED A displayed mark, required to be fiscally responsible rendered as "CONTROLLED", indicating that the electronic or hardcopy information is protected at the level of the subset of CUI for which the patient billing account balance amount owed. 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. 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.
HLD CUI http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode holder CUI Participant who posses an instrument such A displayed mark, required to be rendered as a financial contract (insurance policy) usually based "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.archives.gov/cui/registry/cui-glossary.html. Usage Note: Mandatory control marking, which must be displayed on some agreement with the author. 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.
RCT CUIHLTH http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode record target CUI//HLTH The record target indicates whose medical record holds A displayed mark, required to be rendered as "CUI//HLTH", indicating that the documentation 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 act. 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. 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-title38-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
CUIHLTHP http://terminology.hl7.org/CodeSystem/v3-ActCode (CUI//HLTH) A displayed mark, required to be rendered as "(CUI//HLTH)", indicating that a portion of an electronic or hardcopy information is especially important when protected at the subject 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. 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-title38-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
CUIP http://terminology.hl7.org/CodeSystem/v3-ActCode (CUI) A displayed mark, required to be rendered as "(CUI)", indicating that a service 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 patient himself. involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. 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-title38-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
RCV CUIPRVCY http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode receiver CUI//PRVCY The person (or organization) who receives A displayed mark, required to be rendered as "CUI//PRVCY", indicating that the product electronic or hardcopy controlled unclassified basic privacy information is private and must be protected at the level of an Act. 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. 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-sec401-100.pdf.
IRCP CUIPRVCYP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode (CUI//PRVCY) A displayed mark, required to be rendered as "(CUI//PRVCY)", indicating that a portion of an electronic or hardcopy information recipient 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. 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-sec401-100.pdf.
CUISP-HLTH http://terminology.hl7.org/CodeSystem/v3-ActCode CUI//SP-HLTH A party, who 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 should receive 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. 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/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf.
CUISP-HLTHP http://terminology.hl7.org/CodeSystem/v3-ActCode (CUI//SP-HLTH) A displayed mark, required to be rendered as "(CUI//SP-HLTH)", indicating that a portion of an electronic or who has recieved hardcopy information is protected at the Act level of the subset of CUI for which the authorizing law, regulation, or subsequent Government-wide policy does not set out specific handling or derivative information 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. Usage Note: Examples of healthcare regulation governing CUI Specified marking include HIPAA Transaction and Code Sets and references the Congressional requirement that Act. Information recipient HHS promulgate Privacy, and Security rules https://www.govinfo.gov/content/pkg/USCODE-2016-title42/pdf/USCODE-2016-title42-chap7-subchapXI-partC-sec1320d-2.pdf
CUISP-PRVCY http://terminology.hl7.org/CodeSystem/v3-ActCode CUI//SP-PRVCY A displayed mark, required to be rendered as "CUI//SP-PRVCY", indicating that the electronic or hardcopy information is inert, i.e., independent protected at the level of mood." Rationale: 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. 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 generalization breach of personally identifiable information (PII). It includes a too diverse family 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.
CUISP-PRVCYP http://terminology.hl7.org/CodeSystem/v3-ActCode (CUI//SP-PRVCY) 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 can't be any more specific, for CUI Specified), and CUI Basic controls apply whenever CUI Specified ones do not cover the concept involved CUI. From CUI Glossary https://www.archives.gov/cui/registry/cui-glossary.html. Usage Note: Examples of privacy regulation governing CUI Specified marking is abstract so one 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 specializations 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.
UUI http://terminology.hl7.org/CodeSystem/v3-ActCode (U) 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 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. CUI Marking Handbook https://www.archives.gov/files/cui/20161206-cui-marking-handbook-v1-1.pdf 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) CUI Portion Markings are placed at the beginning of the portion to which they apply and must be used. 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)
NOT SecurityLabelMark http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode ugent notification contact Security Label Mark An abstract code for displayed Security Label tags. 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.
ConfidentialMark http://terminology.hl7.org/CodeSystem/v3-ActCode confidential mark A displayed mark rendered as "Confidential", which indicates to end users that the electronic or hardcopy information recipient they are viewing must be protected at a level of protection as dictated by applicable policy. May be used to notify indicate proprietary or classified information that is, for urgent matters about this Act. (e.g., example, business, intelligence, or project related, e.g., secret ingredients in a laboratory order, critical results 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 being called by phone right away, this viewing additionally protected proprietary and business confidential information deemed proprietary under an applicable jurisdictional or organizational policy. Usage Note: The ConfidentialMark (confidential mark) description is based on the contact HL7 Confidentiality Concept Domain: Types of privacy metadata classifying an IT resource (data, information object, service, or system capability) according to call; its level of sensitivity, which is based on an analysis of applicable privacy policies and the risk of financial, reputational, or for other harm to an inpatient encounter, 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 next 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 kin initiators requesting access to notify when protected resources. Map: Definition aligns with ISO 7498-2:1989 - Confidentiality is the patient becomes critically ill). property that information is not made available or disclosed to unauthorized individuals, entities, or processes.
PRCP COPYMark http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode primary copy of original mark A displayed mark indicating that the electronic or hardcopy information recipient is a copy of an authoritative source for the information. The copy is not considered authoritative but is a duplicate of the authoritative content. 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.
DeliverToAddresseeOnlyMark Information http://terminology.hl7.org/CodeSystem/v3-ActCode deliver only to addressee mark 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. Usage Note: Required by US 32 CRF Part 2002 for container storing or transmitting CUI.
RedisclosureProhibitionMark http://terminology.hl7.org/CodeSystem/v3-ActCode prohibition against redisclosure mark 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 whom 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.cornell.edu/cfr/text/42/2.32 Usage Note: Example of marking requirement from SAMHSA FAQ Response to question 13: Would a logon or splash page notification on an act 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? No. Part 2 requires each disclosure made with written patient consent to be accompanied by a written statement that the information disclosed is primarily directed. E.g., 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 primary care provider receiving user logs onto a discharge letter from computer system; a hospitalist, 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-faqs
RestrictedConfidentialityMark http://terminology.hl7.org/CodeSystem/v3-ActCode restricted confidentiality mark A displayed mark rendered to end users as "Restricted Confidentiality", 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 department receiving information deemed sensitive by an applicable jurisdictional, organizational, or personal privacy policy. Usage Note: The definition is based on HL7 Confidentiality code "R" (restricted), which is described as: Privacy metadata indicating highly sensitive, potentially stigmatizing information, which presents a suspected case 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 infectious disease. Multiple Confidentiality: From HL7 Confidentiality Concept Domain: Types of these participations 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 from HL7 Confidentiality code "R": Confidentiality codes may exist be used in security labels and privacy markings to classify IT resources based on sensitivity to indicate the same act 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. This metadata indicates that the receiver may be obligated to comply with applicable, prevailing (default) jurisdictional privacy law or disclosure authorization. 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.
RefrainPolicy http://terminology.hl7.org/CodeSystem/v3-ActCode refrain policy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Usage Notes: ISO 22600-2 species that a Refrain Policy "defines 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.
NOAUTH http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without requiring subject authorization Prohibition on disclosure without information subject's authorization.
NOCOLLECT http://terminology.hl7.org/CodeSystem/v3-ActCode no collection Prohibition on collection or storage of the information.
NODSCLCD http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without consent directive Prohibition on disclosure without organizational approved patient restriction.
NODSCLCDS http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without information subject's consent directive Prohibition on disclosure without a consent directive from the information subject.
NOINTEGRATE http://terminology.hl7.org/CodeSystem/v3-ActCode no integration Prohibition on Integration into other records.
NOLIST http://terminology.hl7.org/CodeSystem/v3-ActCode no unlisted entity disclosure Prohibition on disclosure except to entities on specific access list.
NOMOU http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without MOU Prohibition on disclosure without an interagency service agreement or memorandum of understanding (MOU).
NOORGPOL http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without organizational authorization Prohibition on disclosure without organizational authorization.
NOPAT http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure to patient, family or caregivers without attending provider's authorization Prohibition on disclosing information to patient, family or caregivers without attending provider's authorization. Usage Note: The information may be labeled with the ActInformationSensitivity TBOO code, triggering application of this RefrainPolicy code as a handling caveat controlling access. Maps to FHIR NOPAT: Typically, this is used on an Alert resource, when the alert records information on patient abuse or non-compliance. FHIR print name is "keep information from patient". Maps to the French realm - code: INVISIBLE_PATIENT. displayName: Document non visible par le patient codingScheme: 1.2.250.1.213.1.1.4.13 French use case: A label for documents that recipients the author chose to hide from the patient until the content can be ranked disclose to the patient in a face to face meeting between a healthcare professional and the patient (in French law some results like cancer diagnosis or AIDS diagnosis must be announced to the patient by a healthcare professional and should not be find out by the patient alone).
NOPERSISTP http://terminology.hl7.org/CodeSystem/v3-ActCode no collection beyond purpose of use Prohibition on collection of the information beyond time necessary to accomplish authorized purpose of use is prohibited.
NORDSCLCD http://terminology.hl7.org/CodeSystem/v3-ActCode no redisclosure without consent directive Prohibition on redisclosure without patient consent directive.
NORDSCLCDS http://terminology.hl7.org/CodeSystem/v3-ActCode no redisclosure without information subject's consent directive Prohibition on redisclosure without a consent directive from the information subject.
NORDSCLW http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without jurisdictional authorization Prohibition on disclosure without authorization under jurisdictional law.
NORELINK http://terminology.hl7.org/CodeSystem/v3-ActCode no relinking Prohibition on associating de-identified or pseudonymized information with other information in a manner that could or does result in disclosing information intended to be masked.
NOREUSE http://terminology.hl7.org/CodeSystem/v3-ActCode no reuse beyond purpose of use Prohibition on use of the information beyond the purpose of use initially authorized.
NOVIP http://terminology.hl7.org/CodeSystem/v3-ActCode no unauthorized VIP disclosure Prohibition on disclosure except to principals with access permission to specific VIP information.
ORCON http://terminology.hl7.org/CodeSystem/v3-ActCode no disclosure without originator authorization Prohibition on disclosure except as primary vs. secondary. permitted by the information originator.
REFB _ActProductAcquisitionCode http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode Referred By ActProductAcquisitionCode A participant (e.g. provider) who has referred The method that a product is obtained for use by the subject of an the supply act (e.g. patient). Typically, Product examples are consumable or durable goods.
LOAN http://terminology.hl7.org/CodeSystem/v3-ActCode Loan Temporary supply of a referred product without transfer of ownership for the product.
RENT http://terminology.hl7.org/CodeSystem/v3-ActCode Rent Temporary supply of a product with financial compensation, without transfer of ownership for the product.
TRANSFER http://terminology.hl7.org/CodeSystem/v3-ActCode Transfer Transfer of ownership for a product.
SALE http://terminology.hl7.org/CodeSystem/v3-ActCode Sale Transfer of ownership for a product for financial compensation.
_ActSpecimenTransportCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecimenTransportCode Transportation of a specimen.
SREC http://terminology.hl7.org/CodeSystem/v3-ActCode specimen received Description:Specimen has been received by participant will provide the participating organization/department.
SSTOR http://terminology.hl7.org/CodeSystem/v3-ActCode specimen in storage Description:Specimen has been placed into storage at a report (e.g. referral). participating location.
REFT STRAN http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode Referred specimen in transit Description:Specimen has been put in transit to a participating receiver.
_ActSpecimenTreatmentCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecimenTreatmentCode Set of codes related to specimen treatments
ACID http://terminology.hl7.org/CodeSystem/v3-ActCode Acidification The person who receives lowering of specimen pH through the patient addition of an acid
TRC ALK http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode tracker Alkalization A secondary information recipient, who receives copies (e.g., The act rendering alkaline by impregnating with an alkali; a primary care provider receiving copies conferring of results as ordered alkaline qualities.
DEFB http://terminology.hl7.org/CodeSystem/v3-ActCode Defibrination The removal of fibrin from whole blood or plasma through physical or chemical means
FILT http://terminology.hl7.org/CodeSystem/v3-ActCode Filtration The passage of a liquid through a filter, accomplished by specialist). gravity, pressure or vacuum (suction).
LOC LDLP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode location LDL Precipitation LDL Precipitation
NEUT http://terminology.hl7.org/CodeSystem/v3-ActCode Neutralization The facility where act or process by which an acid and a base are combined in such proportions that the service resulting compound is done. May neutral.
RECA http://terminology.hl7.org/CodeSystem/v3-ActCode Recalcification The addition of calcium back to a specimen after it was removed by chelating agents
UFIL http://terminology.hl7.org/CodeSystem/v3-ActCode Ultrafiltration The filtration of a colloidal substance through a semipermeable medium that allows only the passage of small molecules.
_ActSubstanceAdministrationCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActSubstanceAdministrationCode 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.
DRUG http://terminology.hl7.org/CodeSystem/v3-ActCode Drug therapy The introduction of a static building (or room therein) drug into a subject with the intention of altering its biologic state with the intent of improving its health status.
FD http://terminology.hl7.org/CodeSystem/v3-ActCode food Description: The introduction of material into a subject with the intent of providing nutrition or other dietary supplements (e.g. minerals or vitamins).
IMMUNIZ http://terminology.hl7.org/CodeSystem/v3-ActCode Immunization The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents.
BOOSTER http://terminology.hl7.org/CodeSystem/v3-ActCode Booster Immunization An additional immunization administration within a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.) series intended to bolster or enhance immunity.
DST INITIMMUNIZ http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode destination Initial Immunization The destination first immunization administration in a series intended to produce immunity
_ActTaskCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActTaskCode 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).
OE http://terminology.hl7.org/CodeSystem/v3-ActCode order entry task A clinician creates a request for services. May a service to be performed for a static building (or room therein) given patient.
LABOE http://terminology.hl7.org/CodeSystem/v3-ActCode laboratory test order entry task A clinician creates a request for a laboratory test to be done for a given patient.
MEDOE http://terminology.hl7.org/CodeSystem/v3-ActCode medication order entry task A clinician creates a request for the administration of one or more medications to a movable facility (e.g., ship). given patient.
ELOC PATDOC http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode patient documentation task A person enters documentation about a given patient.
ALLERLREV http://terminology.hl7.org/CodeSystem/v3-ActCode allergy list review Description: A person reviews a list of known allergies of a given patient.
CLINNOTEE http://terminology.hl7.org/CodeSystem/v3-ActCode clinical note entry location task A location where data clinician enters a clinical note about a given patient
DIAGLISTE http://terminology.hl7.org/CodeSystem/v3-ActCode diagnosis list entry task A clinician enters a diagnosis for a given patient.
DISCHINSTE http://terminology.hl7.org/CodeSystem/v3-ActCode discharge instruction entry A person provides a discharge instruction to a patient.
DISCHSUME http://terminology.hl7.org/CodeSystem/v3-ActCode discharge summary entry task A clinician enters a discharge summary for a given patient.
PATEDUE http://terminology.hl7.org/CodeSystem/v3-ActCode patient education entry A person provides a patient-specific education handout to a patient.
PATREPE http://terminology.hl7.org/CodeSystem/v3-ActCode pathology report entry task A pathologist enters a report for a given patient.
PROBLISTE http://terminology.hl7.org/CodeSystem/v3-ActCode problem list entry task A clinician enters a problem for a given patient.
RADREPE http://terminology.hl7.org/CodeSystem/v3-ActCode radiology report entry task A radiologist enters a report for a given patient.
IMMLREV http://terminology.hl7.org/CodeSystem/v3-ActCode immunization list review Description: A person reviews a list of immunizations due or received for a given patient.
REMLREV http://terminology.hl7.org/CodeSystem/v3-ActCode reminder list review Description: A person reviews a list of health care reminders for a given patient.
WELLREMLREV http://terminology.hl7.org/CodeSystem/v3-ActCode wellness reminder list review Description: A person reviews a list of wellness or preventive care reminders for a given patient.
PATINFO http://terminology.hl7.org/CodeSystem/v3-ActCode patient information review task A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record.
ALLERLE http://terminology.hl7.org/CodeSystem/v3-ActCode allergy list entry Description: A person enters a known allergy for a given patient.
CDSREV http://terminology.hl7.org/CodeSystem/v3-ActCode clinical decision support intervention review A person reviews a recommendation/assessment provided automatically by a clinical decision support application for a given patient.
CLINNOTEREV http://terminology.hl7.org/CodeSystem/v3-ActCode clinical note review task A person reviews a clinical note of a given patient.
DISCHSUMREV http://terminology.hl7.org/CodeSystem/v3-ActCode discharge summary review task A person reviews a discharge summary of a given patient.
DIAGLISTREV http://terminology.hl7.org/CodeSystem/v3-ActCode diagnosis list review task A person reviews a list of diagnoses of a given patient.
IMMLE http://terminology.hl7.org/CodeSystem/v3-ActCode immunization list entry Description: A person enters an Act was entered. immunization due or received for a given patient.
ORG LABRREV http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode origin laboratory results review task The location A person reviews a list of origin laboratory results of a given patient.
MICRORREV http://terminology.hl7.org/CodeSystem/v3-ActCode microbiology results review task A person reviews a list of microbiology results of a given patient.
MICROORGRREV http://terminology.hl7.org/CodeSystem/v3-ActCode microbiology organisms results review task A person reviews organisms of microbiology results of a given patient.
MICROSENSRREV http://terminology.hl7.org/CodeSystem/v3-ActCode microbiology sensitivity test results review task A person reviews the sensitivity test of microbiology results of a given patient.
MLREV http://terminology.hl7.org/CodeSystem/v3-ActCode medication list review task A person reviews a list of medication orders submitted to a given patient
MARWLREV http://terminology.hl7.org/CodeSystem/v3-ActCode medication administration record work list review task A clinician reviews a work list of medications to be administered to a given patient.
OREV http://terminology.hl7.org/CodeSystem/v3-ActCode orders review task A person reviews a list of orders submitted to a given patient.
PATREPREV http://terminology.hl7.org/CodeSystem/v3-ActCode pathology report review task A person reviews a pathology report of a given patient.
PROBLISTREV http://terminology.hl7.org/CodeSystem/v3-ActCode problem list review task A person reviews a list of problems of a given patient.
RADREPREV http://terminology.hl7.org/CodeSystem/v3-ActCode radiology report review task A person reviews a radiology report of a given patient.
REMLE http://terminology.hl7.org/CodeSystem/v3-ActCode reminder list entry Description: A person enters a health care reminder for services. May a given patient.
WELLREMLE http://terminology.hl7.org/CodeSystem/v3-ActCode wellness reminder list entry Description: A person enters a wellness or preventive care reminder for a given patient.
RISKASSESS http://terminology.hl7.org/CodeSystem/v3-ActCode risk assessment instrument task A person reviews a Risk Assessment Instrument report of a given patient.
FALLRISK http://terminology.hl7.org/CodeSystem/v3-ActCode falls risk assessment instrument task A person reviews a Falls Risk Assessment Instrument report of a given patient.
_ActTransportationModeCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActTransportationModeCode Characterizes how a transportation act was or will be carried out. Examples: Via private transport, via public transit, via courier.
_ActPatientTransportationModeCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActPatientTransportationModeCode Definition: Characterizes how a static building (or room therein) patient was or will be transported to the site of a movable facility (e.g., ship). patient encounter. Examples: Via ambulance, via public transit, on foot.
RML AFOOT http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode remote pedestrian transport Some services take place pedestrian transport
AMBT http://terminology.hl7.org/CodeSystem/v3-ActCode ambulance transport ambulance transport
AMBAIR http://terminology.hl7.org/CodeSystem/v3-ActCode fixed-wing ambulance transport fixed-wing ambulance transport
AMBGRND http://terminology.hl7.org/CodeSystem/v3-ActCode ground ambulance transport ground ambulance transport
AMBHELO http://terminology.hl7.org/CodeSystem/v3-ActCode helicopter ambulance transport helicopter ambulance transport
LAWENF http://terminology.hl7.org/CodeSystem/v3-ActCode law enforcement transport law enforcement transport
PRVTRN http://terminology.hl7.org/CodeSystem/v3-ActCode private transport private transport
PUBTRN http://terminology.hl7.org/CodeSystem/v3-ActCode public transport public transport
_ObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode ObservationType Identifies the kinds of observations that can be performed
_ActSpecObsCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsCode Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation
ARTBLD http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsArtBldCode Describes the artificial blood identifier that is associated with the specimen.
DILUTION http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsDilutionCode An observation that reports the dilution of a sample.
AUTO-HIGH http://terminology.hl7.org/CodeSystem/v3-ActCode Auto-High Dilution The dilution of a sample performed by automated equipment. The value is specified by the equipment
AUTO-LOW http://terminology.hl7.org/CodeSystem/v3-ActCode Auto-Low Dilution The dilution of a sample performed by automated equipment. The value is specified by the equipment
PRE http://terminology.hl7.org/CodeSystem/v3-ActCode Pre-Dilution The dilution of the specimen made prior to being loaded onto analytical equipment
RERUN http://terminology.hl7.org/CodeSystem/v3-ActCode Rerun Dilution The value of the dilution of a sample after it had been analyzed at multiple concurrent locations a prior dilution value
EVNFCTS http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsEvntfctsCode Domain provides codes that qualify the ActLabObsEnvfctsCode domain. (Environmental Factors)
INTFR http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsInterferenceCode An observation that relates to factors that may potentially cause interference with the observation
FIBRIN http://terminology.hl7.org/CodeSystem/v3-ActCode Fibrin The Fibrin Index of the specimen. In the case of only differentiating between Absent and Present, recommend using 0 and 1
HEMOLYSIS http://terminology.hl7.org/CodeSystem/v3-ActCode Hemolysis An observation of the hemolysis index of the specimen in g/L
ICTERUS http://terminology.hl7.org/CodeSystem/v3-ActCode Icterus An observation that describes the icterus index of the specimen. It is recommended to use mMol/L of bilirubin
LIPEMIA http://terminology.hl7.org/CodeSystem/v3-ActCode Lipemia 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).
VOLUME http://terminology.hl7.org/CodeSystem/v3-ActCode ActSpecObsVolumeCode An observation that reports the volume of a sample.
AVAILABLE http://terminology.hl7.org/CodeSystem/v3-ActCode Available Volume The available quantity of specimen. This is the current quantity minus any planned consumption (e.g., telemedicine, telephone consultation). tests that are planned)
CONSUMPTION http://terminology.hl7.org/CodeSystem/v3-ActCode Consumption Volume The location quantity of specimen that is used each time the equipment uses this substance
CURRENT http://terminology.hl7.org/CodeSystem/v3-ActCode Current Volume The current quantity of the specimen, i.e., initial quantity minus what has been actually used.
INITIAL http://terminology.hl7.org/CodeSystem/v3-ActCode Initial Volume The initial quantity of the specimen in inventory
_AnnotationType http://terminology.hl7.org/CodeSystem/v3-ActCode AnnotationType AnnotationType
_ActPatientAnnotationType http://terminology.hl7.org/CodeSystem/v3-ActCode ActPatientAnnotationType Description:Provides a categorization for annotations recorded directly against the patient .
ANNDI http://terminology.hl7.org/CodeSystem/v3-ActCode diagnostic image note Description:A note that is specific to a patient's diagnostic images, either historical, current or planned.
ANNGEN http://terminology.hl7.org/CodeSystem/v3-ActCode general note Description:A general or uncategorized note.
ANNIMM http://terminology.hl7.org/CodeSystem/v3-ActCode immunization note A note that is specific to a patient's immunizations, either historical, current or planned.
ANNLAB http://terminology.hl7.org/CodeSystem/v3-ActCode laboratory note Description:A note that is specific to a patient's laboratory results, either historical, current or planned.
ANNMED http://terminology.hl7.org/CodeSystem/v3-ActCode medication note Description:A note that is specific to a patient's medications, either historical, current or planned.
_GeneticObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode GeneticObservationType Description: None provided
GENE http://terminology.hl7.org/CodeSystem/v3-ActCode gene 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
_ImmunizationObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode ImmunizationObservationType Description: Observation codes which describe characteristics of the immunization material.
OBSANTC http://terminology.hl7.org/CodeSystem/v3-ActCode antigen count Description: Indicates the valid antigen count.
OBSANTV http://terminology.hl7.org/CodeSystem/v3-ActCode antigen validity Description: Indicates whether an antigen is valid or invalid.
_IndividualCaseSafetyReportType http://terminology.hl7.org/CodeSystem/v3-ActCode Individual Case Safety Report Type 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 principal performing actor initial sender did not specify the type of report. Example concepts include: Spontaneous, Report from study, Other.
PAT_ADV_EVNT http://terminology.hl7.org/CodeSystem/v3-ActCode patient adverse event Indicates that the ICSR is located describing problems that a patient experienced after receiving a vaccine product.
VAC_PROBLEM http://terminology.hl7.org/CodeSystem/v3-ActCode vaccine product problem Indicates that the ICSR is taken describing a problem with the actual vaccine product such as physical defects (cloudy, particulate matter) or inability to confer immunity.
_LOINCObservationActContextAgeType http://terminology.hl7.org/CodeSystem/v3-ActCode LOINCObservationActContextAgeType Definition:The set of LOINC codes for the primary location (LOC) while act of determining the other location(s) are period of time that has elapsed since an entity was born or created.
21611-9 http://terminology.hl7.org/CodeSystem/v3-ActCode age patient qn est Definition:Estimated age.
21612-7 http://terminology.hl7.org/CodeSystem/v3-ActCode age patient qn reported Definition:Reported age.
29553-5 http://terminology.hl7.org/CodeSystem/v3-ActCode age patient qn calc Definition:Calculated age.
30525-0 http://terminology.hl7.org/CodeSystem/v3-ActCode age patient qn definition Definition:General specification of age with no implied method of determination.
30972-4 http://terminology.hl7.org/CodeSystem/v3-ActCode age at onset of adverse event Definition:Age at onset of associated adverse event; no implied method of determination.
_MedicationObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode MedicationObservationType MedicationObservationType
REP_HALF_LIFE http://terminology.hl7.org/CodeSystem/v3-ActCode representative half-life Description:This observation represents an 'average' or 'expected' half-life typical of the product.
SPLCOATING http://terminology.hl7.org/CodeSystem/v3-ActCode coating 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 "remote." (for example, coatings to individual pellets or granules inside a capsule or tablet are excluded from consideration). 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.
VIA SPLCOLOR http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode via color For services, Definition: A characteristic of an intermediate location oral solid dosage form of a medicinal product, specifying the color or colors that specifies 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. Constraints: The Observation.value must be a path between origin 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 destination. 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;Orange;Brown;Blue;Turquoise.
PRF SPLIMAGE http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode performer image 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.
SPLIMPRINT http://terminology.hl7.org/CodeSystem/v3-ActCode imprint Definition: A person, non-person living subject, organization 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 device printed with ink. The presence of other non-textual distinguishing marks or symbols is recorded by SPLSYMBOL. Examples: Included in SPLIMPRINT are alphanumeric text that who actually appears on the bands of banded capsules and principally carries out logos and other symbols that can be interpreted as letters or numbers. Constraints: The Observation.value must be of type Character String (ST). Excluded from SPLIMPRINT are internal and external cut-outs in the action. Device should 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.
SPLSCORING http://terminology.hl7.org/CodeSystem/v3-ActCode scoring 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). 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. 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 assigned as divided into unequal pieces are given a performer null-value with nullFlavor other (OTH).
SPLSHAPE http://terminology.hl7.org/CodeSystem/v3-ActCode shape Description: A characteristic of an oral solid dosage form of a medicinal product, specifying the two dimensional representation of the solid dose form, in circumstances where terms of the device outside perimeter of a solid dosage form when the dosage form, resting on a flat surface, is performing independent viewed from directly above, including slight rounding of human intervention. Need 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.
SPLSIZE http://terminology.hl7.org/CodeSystem/v3-ActCode size 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 principal responsible actor. Exampe: nearest whole millimeter. Example: SPLSIZE for a rectangular shaped tablet is the length and SPLSIZE for a round shaped tablet is the diameter.
SPLSYMBOL http://terminology.hl7.org/CodeSystem/v3-ActCode symbol Definition: A surgery resident operating under supervision characteristic of an oral solid dosage form of attending surgeon, a search medicinal product, to describe whether or not the medicinal product has a mark or symbol appearing on it for easy and rescue dog locating survivors, 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. 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. Example:
_ObservationIssueTriggerCodedObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode ObservationIssueTriggerCodedObservationType 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.
_CaseTransmissionMode http://terminology.hl7.org/CodeSystem/v3-ActCode case transmission mode 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.
AIRTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode airborne transmission Communication of an electronic laboratory analyzer agent from a living subject or environmental source to a living subject through indirect contact via oral or nasal inhalation.
ANANTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode animal to animal transmission Communication of an agent from one animal to another proximate animal.
ANHUMTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode animal to human transmission Communication of an agent from an animal to a proximate person.
BDYFLDTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode body fluid contact transmission Communication of an agent from one living subject to another living subject through direct contact with any body fluid.
BLDTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode blood borne transmission Communication of an agent to a living subject through direct contact with blood or blood products whether the laboratory discipline requested contact with blood is part of a therapeutic procedure or not.
DERMTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode transdermal transmission Communication of an agent from a living subject or environmental source to perform a laboratory test. living subject via agent migration through intact skin.
ENVTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode environmental exposure transmission Communication of an agent from an environmental surface or source to a living subject by direct contact.
FECTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode fecal-oral transmission 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.
FOMTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode fomite transmission Communication of an agent from an non-living material to a living subject through direct contact.
FOODTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode food-borne transmission Communication of an agent from a food source to a living subject via oral consumption.
HUMHUMTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode human to human transmission Communication of an agent from a person to a proximate person.
INDTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode indeterminate disease transmission mode Communication of an agent to a living subject via an undetermined route.
LACTTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode lactation transmission Communication of an agent from one living subject to another living subject through direct contact with mammalian milk or colostrum.
NOSTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode nosocomial transmission Communication of an agent from any entity to a living subject while the living subject is in the patient role in a healthcare facility.
PARTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode parenteral transmission 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.
PLACTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode transplacental transmission 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.
SEXTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode sexual transmission 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.
TRNSFTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode transfusion transmission 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.
VECTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode vector-borne transmission 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.
WATTRNS http://terminology.hl7.org/CodeSystem/v3-ActCode water-borne transmission Communication of an agent from a contaminated water source to a living subject whether the water is ingested as a food or not. The performer route of entry of the water may also be through any bodily orifice.
_ObservationQualityMeasureAttribute http://terminology.hl7.org/CodeSystem/v3-ActCode ObservationQualityMeasureAttribute Codes used to define various metadata aspects of a health quality measure.
AGGREGATE http://terminology.hl7.org/CodeSystem/v3-ActCode aggregate measure observation Indicates that the patient observation is carrying out an aggregation calculation, contained in self-care, e.g. fingerstick blood sugar. the value element.
CMPMSRMTH http://terminology.hl7.org/CodeSystem/v3-ActCode composite measure method Indicates what method is used in a quality measure to combine the component measure results included in an composite measure.
CMPMSRSCRWGHT http://terminology.hl7.org/CodeSystem/v3-ActCode component measure scoring weight 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 traditional order filler 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 performer. This single composite measure SHALL be 1.0. The value assigned is scoped to the composite measure referencing this component measure only.
COPY http://terminology.hl7.org/CodeSystem/v3-ActCode copyright Identifies the organization(s) who own the intellectual property represented by the eMeasure.
CRS http://terminology.hl7.org/CodeSystem/v3-ActCode clinical recommendation statement Summary of relevant clinical guidelines or other clinical recommendations supporting this eMeasure.
DEF http://terminology.hl7.org/CodeSystem/v3-ActCode definition Description of individual terms, provided as needed.
DISC http://terminology.hl7.org/CodeSystem/v3-ActCode disclaimer Disclaimer information should accompany every service event. Note: for the eMeasure.
FINALDT http://terminology.hl7.org/CodeSystem/v3-ActCode finalized date/time The timestamp when the eMeasure was last packaged in the Measure Authoring Tool.
GUIDE http://terminology.hl7.org/CodeSystem/v3-ActCode guidance 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.
IDUR http://terminology.hl7.org/CodeSystem/v3-ActCode improvement notation 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).
ITMCNT http://terminology.hl7.org/CodeSystem/v3-ActCode items counted Describes the items counted by the measure (e.g., patients, encounters, procedures, etc.)
KEY http://terminology.hl7.org/CodeSystem/v3-ActCode keyword A significant word that existing HL7 designs assign aids in discoverability.
MEDT http://terminology.hl7.org/CodeSystem/v3-ActCode measurement end date The end date of the measurement period.
MSD http://terminology.hl7.org/CodeSystem/v3-ActCode measurement start date The start date of the measurement period.
MSRADJ http://terminology.hl7.org/CodeSystem/v3-ActCode risk adjustment 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 organization eMeasure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow more useful comparisons.
MSRAGG http://terminology.hl7.org/CodeSystem/v3-ActCode rate aggregation 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). 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.
MSRIMPROV http://terminology.hl7.org/CodeSystem/v3-ActCode health quality measure improvement notation Information on whether an increase or decrease in score is the playing entity preferred result. This should reflect information on which way is better, an increase or decrease in score.
MSRJUR http://terminology.hl7.org/CodeSystem/v3-ActCode jurisdiction The list of jurisdiction(s) for which the Role measure applies.
MSRRPTR http://terminology.hl7.org/CodeSystem/v3-ActCode reporter type Type of person or organization that is expected to report the performer. issue.
MSRRPTTIME http://terminology.hl7.org/CodeSystem/v3-ActCode timeframe for reporting The maximum time that may elapse following completion of the measure until the measure report must be sent to the receiver.
MSRSCORE http://terminology.hl7.org/CodeSystem/v3-ActCode measure scoring Indicates how the calculation is performed for the eMeasure (e.g., proportion, continuous variable, ratio)
MSRSET http://terminology.hl7.org/CodeSystem/v3-ActCode health quality measure care setting Location(s) in which care being measured is rendered 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).
MSRTOPIC http://terminology.hl7.org/CodeSystem/v3-ActCode health quality measure topic type health quality measure topic type
MSRTP http://terminology.hl7.org/CodeSystem/v3-ActCode measurement period The time period for which the eMeasure applies.
MSRTYPE http://terminology.hl7.org/CodeSystem/v3-ActCode measure type Indicates whether the eMeasure is used to examine a process or an outcome over time (e.g., Structure, Process, Outcome).
RAT http://terminology.hl7.org/CodeSystem/v3-ActCode rationale Succinct statement of the need for the measure. Usually includes statements pertaining to Importance criterion: impact, gap in care and evidence.
REF http://terminology.hl7.org/CodeSystem/v3-ActCode reference Identifies bibliographic citations or references to clinical practice guidelines, sources of evidence, or other relevant materials supporting the intent and rationale of the eMeasure.
SDE http://terminology.hl7.org/CodeSystem/v3-ActCode supplemental data elements 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.
STRAT http://terminology.hl7.org/CodeSystem/v3-ActCode stratification Describes the strata for which the measure is to be evaluated. There are three examples of reasons for stratification based on existing work. These designs should 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]).
TRANF http://terminology.hl7.org/CodeSystem/v3-ActCode transmission format Can be revised a URL or hyperlinks that link to the transmission formats that are specified for a particular reporting program.
USE http://terminology.hl7.org/CodeSystem/v3-ActCode notice of use Usage notes.
_ObservationSequenceType http://terminology.hl7.org/CodeSystem/v3-ActCode ObservationSequenceType ObservationSequenceType
TIME_ABSOLUTE http://terminology.hl7.org/CodeSystem/v3-ActCode absolute time sequence A sequence of values in subsequent releases the "absolute" time domain. This is the same time domain that all HL7 timestamps use. It is time as measured by the Gregorian calendar
TIME_RELATIVE http://terminology.hl7.org/CodeSystem/v3-ActCode relative time sequence A sequence of values in a "relative" time domain. The time is measured relative to make the earliest effective time in the Observation Series containing this sequence.
_ObservationSeriesType http://terminology.hl7.org/CodeSystem/v3-ActCode ObservationSeriesType ObservationSeriesType
_ECGObservationSeriesType http://terminology.hl7.org/CodeSystem/v3-ActCode ECGObservationSeriesType ECGObservationSeriesType
REPRESENTATIVE_BEAT http://terminology.hl7.org/CodeSystem/v3-ActCode ECG representative beat waveforms 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 scooping entity 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.
RHYTHM http://terminology.hl7.org/CodeSystem/v3-ActCode ECG rhythm waveforms 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.
_PatientImmunizationRelatedObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode PatientImmunizationRelatedObservationType Description: Reporting codes that are related to an immunization event.
CLSSRM http://terminology.hl7.org/CodeSystem/v3-ActCode classroom Description: The class room associated with the patient during the immunization event.
GRADE http://terminology.hl7.org/CodeSystem/v3-ActCode grade Description: The school grade or level the patient was in when immunized.
SCHL http://terminology.hl7.org/CodeSystem/v3-ActCode school Description: The school the patient attended when immunized.
SCHLDIV http://terminology.hl7.org/CodeSystem/v3-ActCode school division Description: The school division or district associated with the patient during the immunization event.
TEACHER http://terminology.hl7.org/CodeSystem/v3-ActCode teacher Description: The patient's teacher when immunized.
_PopulationInclusionObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode PopulationInclusionObservationType Observation types for specifying criteria used to assert that a subject is included in a particular population.
DENEX http://terminology.hl7.org/CodeSystem/v3-ActCode denominator exclusions Criteria which specify subjects who should be removed from the role involved. 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.
DIST DENEXCEP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode distributor denominator exceptions Distributes material 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 generated during continuous variable eMeasures. Denominator exceptions allow for the act. 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: Medical reasons Patient (or subject) reasons System reasons
PPRF DENOM http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode primary performer denominator 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 principal denominator can be the same as the initial population, or primary performer it may be a subset of the act. 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.
SPRF IPOP http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode secondary performer initial population A person assisting 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).
IPPOP http://terminology.hl7.org/CodeSystem/v3-ActCode initial patient population 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.
MSROBS http://terminology.hl7.org/CodeSystem/v3-ActCode measure observation 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. Examples: 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
MSRPOPL http://terminology.hl7.org/CodeSystem/v3-ActCode measure population 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.
MSRPOPLEX http://terminology.hl7.org/CodeSystem/v3-ActCode measure population exclusions 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).
NUMER http://terminology.hl7.org/CodeSystem/v3-ActCode numerator 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).
NUMEX http://terminology.hl7.org/CodeSystem/v3-ActCode numerator exclusions 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.
_PreferenceObservationType http://terminology.hl7.org/CodeSystem/v3-ActCode _PreferenceObservationType Types of observations that can be made about Preferences.
PREFSTRENGTH http://terminology.hl7.org/CodeSystem/v3-ActCode preference strength An observation about how important a preference is to the target of the preference.
ADVERSE_REACTION http://terminology.hl7.org/CodeSystem/v3-ActCode Adverse Reaction Indicates that the observation is of an act through his substantial presence 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.
ASSERTION http://terminology.hl7.org/CodeSystem/v3-ActCode Assertion 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 involvement observation.value="fracture of femur present" is an assertion of a clinical finding of femur fracture.
CASESER http://terminology.hl7.org/CodeSystem/v3-ActCode case seriousness criteria Definition:An observation that provides a characterization of the level of harm to an investigation subject as a result of a reaction or event.
CDIO http://terminology.hl7.org/CodeSystem/v3-ActCode case disease imported observation 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. OpenIssue: This includes: assistants, technicians, associates, code could be moved to LOINC if it can be done before there are significant implemenations using it.
CRIT http://terminology.hl7.org/CodeSystem/v3-ActCode criticality 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 whatever organ system threatening potential, it is considered to be of high criticality.
CTMO http://terminology.hl7.org/CodeSystem/v3-ActCode case transmission mode observation An observation that states the job titles may be. mechanism by which disease was acquired by the living subject involved in the public health case. OpenIssue: This code could be moved to LOINC if it can be done before there are significant implemenations using it.
RESP DX http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode responsible party ObservationDiagnosisTypes Includes all codes defining types of indications such as diagnosis, symptom and other indications such as contrast agents for lab tests.
ADMDX http://terminology.hl7.org/CodeSystem/v3-ActCode admitting diagnosis Admitting diagnosis are the diagnoses documented for administrative purposes as the basis for a hospital admission.
DISDX http://terminology.hl7.org/CodeSystem/v3-ActCode discharge diagnosis Discharge diagnosis are the diagnoses documented for administrative purposes as the time of hospital discharge.
INTDX http://terminology.hl7.org/CodeSystem/v3-ActCode intermediate diagnosis Intermediate diagnoses are those diagnoses documented for administrative purposes during the course of a hospital stay.
NOI http://terminology.hl7.org/CodeSystem/v3-ActCode nature of injury The person or organization type of injury that has primary responsibility the injury coding specifies.
GISTIER http://terminology.hl7.org/CodeSystem/v3-ActCode GIS tier Description: Accuracy determined as per the GIS tier code system.
HHOBS http://terminology.hl7.org/CodeSystem/v3-ActCode household situation observation Indicates that the observation is of a person’s living situation in a household including the household composition and circumstances.
ISSUE http://terminology.hl7.org/CodeSystem/v3-ActCode detected issue There is a clinical issue for the act. therapy that makes continuation of the therapy inappropriate. Open Issue: The responsible definition of this code does not correctly represent the concept space of its specializations (children)
_ActAdministrativeDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdministrativeDetectedIssueCode Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains.
_ActAdministrativeAuthorizationDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdministrativeAuthorizationDetectedIssueCode ActAdministrativeAuthorizationDetectedIssueCode
NAT http://terminology.hl7.org/CodeSystem/v3-ActCode Insufficient authorization The requesting party is has insufficient authorization to invoke the interaction.
SUPPRESSED http://terminology.hl7.org/CodeSystem/v3-ActCode record suppressed Description: One or more records in the query response have been suppressed due to consent or privacy restrictions.
VALIDAT http://terminology.hl7.org/CodeSystem/v3-ActCode validation issue Description:The specified element did not necessarily present pass business-rule validation.
KEY204 http://terminology.hl7.org/CodeSystem/v3-ActCode Unknown key identifier The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient.
KEY205 http://terminology.hl7.org/CodeSystem/v3-ActCode Duplicate key identifier The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).
COMPLY http://terminology.hl7.org/CodeSystem/v3-ActCode Compliance Alert There may be an action, issue with the patient complying with the intentions of the proposed therapy
DUPTHPY http://terminology.hl7.org/CodeSystem/v3-ActCode Duplicate Therapy Alert The proposed therapy appears to duplicate an existing therapy
DUPTHPCLS http://terminology.hl7.org/CodeSystem/v3-ActCode duplicate therapeutic alass alert Description:The proposed therapy appears to have the same intended therapeutic benefit as an existing therapy, though the specific mechanisms of action vary.
DUPTHPGEN http://terminology.hl7.org/CodeSystem/v3-ActCode duplicate generic alert 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.
ABUSE http://terminology.hl7.org/CodeSystem/v3-ActCode commonly abused/misused alert Description:The proposed therapy is frequently misused or abused and therefore should be used with caution and/or monitoring.
FRAUD http://terminology.hl7.org/CodeSystem/v3-ActCode potential fraud Description:The request is suspected to have a fraudulent basis.
PLYDOC http://terminology.hl7.org/CodeSystem/v3-ActCode Poly-orderer Alert A similar or identical therapy was recently ordered by a different practitioner.
PLYPHRM http://terminology.hl7.org/CodeSystem/v3-ActCode Poly-supplier Alert This patient was recently supplied a similar or identical therapy from a different pharmacy or supplier.
DOSE http://terminology.hl7.org/CodeSystem/v3-ActCode Dosage problem Proposed dosage instructions for therapy differ from standard practice.
DOSECOND http://terminology.hl7.org/CodeSystem/v3-ActCode dosage-condition alert Description:Proposed dosage is inappropriate due to patient's medical condition.
DOSEDUR http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Duration Alert Proposed length of therapy differs from standard practice.
DOSEDURH http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Duration High Alert Proposed length of therapy is longer than standard practice
DOSEDURHIND http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Duration High for Indication Alert Proposed length of therapy is longer than standard practice for the identified indication or diagnosis
DOSEDURL http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Duration Low Alert Proposed length of therapy is shorter than that necessary for therapeutic effect
DOSEDURLIND http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Duration Low for Indication Alert Proposed length of therapy is shorter than standard practice for the identified indication or diagnosis
DOSEH http://terminology.hl7.org/CodeSystem/v3-ActCode High Dose Alert Proposed dosage exceeds standard practice
DOSEHINDA http://terminology.hl7.org/CodeSystem/v3-ActCode High Dose for Age Alert Proposed dosage exceeds standard practice for the patient's age
DOSEHIND http://terminology.hl7.org/CodeSystem/v3-ActCode High Dose for Indication Alert High Dose for Indication Alert
DOSEHINDSA http://terminology.hl7.org/CodeSystem/v3-ActCode High Dose for Height/Surface Area Alert Proposed dosage exceeds standard practice for the patient's height or body surface area
DOSEHINDW http://terminology.hl7.org/CodeSystem/v3-ActCode High Dose for Weight Alert Proposed dosage exceeds standard practice for the patient's weight
DOSEIVL http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Interval Alert Proposed dosage interval/timing differs from standard practice
DOSEIVLIND http://terminology.hl7.org/CodeSystem/v3-ActCode Dose-Interval for Indication Alert Proposed dosage interval/timing differs from standard practice for the identified indication or diagnosis
DOSEL http://terminology.hl7.org/CodeSystem/v3-ActCode Low Dose Alert Proposed dosage is below suggested therapeutic levels
DOSELINDA http://terminology.hl7.org/CodeSystem/v3-ActCode Low Dose for Age Alert Proposed dosage is below suggested therapeutic levels for the patient's age
DOSELIND http://terminology.hl7.org/CodeSystem/v3-ActCode Low Dose for Indication Alert Low Dose for Indication Alert
DOSELINDSA http://terminology.hl7.org/CodeSystem/v3-ActCode Low Dose for Height/Surface Area Alert Proposed dosage is below suggested therapeutic levels for the patient's height or body surface area
DOSELINDW http://terminology.hl7.org/CodeSystem/v3-ActCode Low Dose for Weight Alert Proposed dosage is below suggested therapeutic levels for the patient's weight
MDOSE http://terminology.hl7.org/CodeSystem/v3-ActCode maximum dosage reached Description:The maximum quantity of this drug allowed to be administered within a particular time-range (month, year, lifetime) has been reached or exceeded.
OBSA http://terminology.hl7.org/CodeSystem/v3-ActCode Observation Alert Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient
AGE http://terminology.hl7.org/CodeSystem/v3-ActCode Age Alert Proposed therapy may be inappropriate or contraindicated due to patient age
ADALRT http://terminology.hl7.org/CodeSystem/v3-ActCode adult alert Proposed therapy is outside of the standard practice for an adult patient.
GEALRT http://terminology.hl7.org/CodeSystem/v3-ActCode geriatric alert Proposed therapy is outside of standard practice for a geriatric patient.
PEALRT http://terminology.hl7.org/CodeSystem/v3-ActCode pediatric alert Proposed therapy is outside of the standard practice for a pediatric patient.
COND http://terminology.hl7.org/CodeSystem/v3-ActCode Condition Alert Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis
HGHT http://terminology.hl7.org/CodeSystem/v3-ActCode
LACT http://terminology.hl7.org/CodeSystem/v3-ActCode Lactation Alert Proposed therapy may be inappropriate or contraindicated when breast-feeding
PREG http://terminology.hl7.org/CodeSystem/v3-ActCode Pregnancy Alert Proposed therapy may be inappropriate or contraindicated during pregnancy
WGHT http://terminology.hl7.org/CodeSystem/v3-ActCode
CREACT http://terminology.hl7.org/CodeSystem/v3-ActCode common reaction alert Description:Proposed therapy may be inappropriate or contraindicated because of a common but non-patient specific reaction to the product. Example:There is accountable no record of a specific sensitivity for the action through patient, but the power presence of the sensitivity is common and therefore caution is warranted.
GEN http://terminology.hl7.org/CodeSystem/v3-ActCode Genetic Alert Proposed therapy may be inappropriate or contraindicated due to delegate, patient genetic indicators.
GEND http://terminology.hl7.org/CodeSystem/v3-ActCode Gender Alert Proposed therapy may be inappropriate or contraindicated due to patient gender.
LAB http://terminology.hl7.org/CodeSystem/v3-ActCode Lab Alert Proposed therapy may be inappropriate or contraindicated due to recent lab test results
REACT http://terminology.hl7.org/CodeSystem/v3-ActCode Reaction Alert Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product
ALGY http://terminology.hl7.org/CodeSystem/v3-ActCode Allergy Alert Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to the proposed product. (Allergies are immune based reactions.)
INT http://terminology.hl7.org/CodeSystem/v3-ActCode Intolerance Alert Proposed therapy may be inappropriate or contraindicated because of a recorded patient intolerance to the proposed product. (Intolerances are non-immune based sensitivities.)
RREACT http://terminology.hl7.org/CodeSystem/v3-ActCode Related Reaction Alert Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product.
RALG http://terminology.hl7.org/CodeSystem/v3-ActCode Related Allergy Alert Proposed therapy may be inappropriate or contraindicated because of a recorded patient allergy to a cross-sensitivity related product. (Allergies are immune based reactions.)
RAR http://terminology.hl7.org/CodeSystem/v3-ActCode Related Prior Reaction Alert Proposed therapy may be inappropriate or contraindicated because of a recorded prior adverse reaction to a cross-sensitivity related product.
RINT http://terminology.hl7.org/CodeSystem/v3-ActCode Related Intolerance Alert 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.)
BUS http://terminology.hl7.org/CodeSystem/v3-ActCode business constraint violation Description:A local business rule relating multiple elements has been violated.
CODE_INVAL http://terminology.hl7.org/CodeSystem/v3-ActCode code is not valid Description:The specified code is not valid against the list of codes allowed for the element.
CODE_DEPREC http://terminology.hl7.org/CodeSystem/v3-ActCode code has been deprecated Description:The specified code has been deprecated and should no longer be used. Select another code from the duty code system.
FORMAT http://terminology.hl7.org/CodeSystem/v3-ActCode invalid format Description:The element does not follow the formatting or type rules defined for the field.
ILLEGAL http://terminology.hl7.org/CodeSystem/v3-ActCode illegal Description:The request is missing elements or contains elements which cause it to review actions not meet the legal standards for actioning.
LEN_RANGE http://terminology.hl7.org/CodeSystem/v3-ActCode length out of range Description:The length of the data specified falls out of the range defined for the element.
LEN_LONG http://terminology.hl7.org/CodeSystem/v3-ActCode length is too long Description:The length of the data specified is greater than the maximum length defined for the element.
LEN_SHORT http://terminology.hl7.org/CodeSystem/v3-ActCode length is too short Description:The length of the data specified is less than the minimum length defined for the element.
MISSCOND http://terminology.hl7.org/CodeSystem/v3-ActCode conditional element missing Description:The specified element must be specified with a non-null value under certain conditions. In this case, the performing actor conditions are true but the element is still missing or null.
MISSMAND http://terminology.hl7.org/CodeSystem/v3-ActCode mandatory element missing Description:The specified element is mandatory and was not included in the instance.
NODUPS http://terminology.hl7.org/CodeSystem/v3-ActCode duplicate values are not permitted Description:More than one element with the same value exists in the set. Duplicates not permission in this set in a set.
NOPERSIST http://terminology.hl7.org/CodeSystem/v3-ActCode element will not be persisted Description: Element in submitted message will not persist in data storage based on detected issue.
REP_RANGE http://terminology.hl7.org/CodeSystem/v3-ActCode repetitions out of range Description:The number of repeating elements falls outside the range of the allowed number of repetitions.
MAXOCCURS http://terminology.hl7.org/CodeSystem/v3-ActCode repetitions above maximum Description:The number of repeating elements is above the maximum number of repetitions allowed.
MINOCCURS http://terminology.hl7.org/CodeSystem/v3-ActCode repetitions below minimum Description:The number of repeating elements is below the minimum number of repetitions allowed.
_ActAdministrativeRuleDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActAdministrativeRuleDetectedIssueCode ActAdministrativeRuleDetectedIssueCode
KEY206 http://terminology.hl7.org/CodeSystem/v3-ActCode non-matching identification Description: Metadata associated with the identification (e.g. name or gender) does not match the identification being verified.
OBSOLETE http://terminology.hl7.org/CodeSystem/v3-ActCode obsolete record returned Description: One or more records in the query response have a status of 'obsolete'.
_ActSuppliedItemDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActSuppliedItemDetectedIssueCode Identifies types of detected issues regarding the administration or supply of an item to a patient.
_AdministrationDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode AdministrationDetectedIssueCode Administration of the proposed therapy may be inappropriate or contraindicated as proposed
_AppropriatenessDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode AppropriatenessDetectedIssueCode AppropriatenessDetectedIssueCode
_InteractionDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode InteractionDetectedIssueCode InteractionDetectedIssueCode
FOOD http://terminology.hl7.org/CodeSystem/v3-ActCode Food Interaction Alert Proposed therapy may interact with certain foods
TPROD http://terminology.hl7.org/CodeSystem/v3-ActCode Therapeutic Product Alert Proposed therapy may interact with an existing or recent therapeutic product
DRG http://terminology.hl7.org/CodeSystem/v3-ActCode Drug Interaction Alert Proposed therapy may interact with an existing or recent drug therapy
NHP http://terminology.hl7.org/CodeSystem/v3-ActCode Natural Health Product Alert Proposed therapy may interact with existing or recent natural health product therapy
NONRX http://terminology.hl7.org/CodeSystem/v3-ActCode Non-Prescription Interaction Alert Proposed therapy may interact with a non-prescription drug (e.g. alcohol, tobacco, Aspirin)
PREVINEF http://terminology.hl7.org/CodeSystem/v3-ActCode previously ineffective Definition:The same or similar treatment has previously been attempted with the patient without achieving a positive effect.
DACT http://terminology.hl7.org/CodeSystem/v3-ActCode drug action detected issue Description:Proposed therapy may be contraindicated or ineffective based on an existing or recent drug therapy.
TIME http://terminology.hl7.org/CodeSystem/v3-ActCode timing detected issue Description:Proposed therapy may be inappropriate or ineffective based on the proposed start or end time.
ALRTENDLATE http://terminology.hl7.org/CodeSystem/v3-ActCode end too late alert Definition:Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy.
ALRTSTRTLATE http://terminology.hl7.org/CodeSystem/v3-ActCode start too late alert Definition:Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the fact. onset of the condition.
_TimingDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode TimingDetectedIssueCode Proposed therapy may be inappropriate or ineffective based on the proposed start or end time.
ENDLATE http://terminology.hl7.org/CodeSystem/v3-ActCode End Too Late Alert Proposed therapy may be inappropriate or ineffective because the end of administration is too close to another planned therapy
STRTLATE http://terminology.hl7.org/CodeSystem/v3-ActCode Start Too Late Alert Proposed therapy may be inappropriate or ineffective because the start of administration is too late after the onset of the condition
_SupplyDetectedIssueCode http://terminology.hl7.org/CodeSystem/v3-ActCode SupplyDetectedIssueCode Supplying the product at this time may be inappropriate or indicate compliance issues with the associated therapy
ALLDONE http://terminology.hl7.org/CodeSystem/v3-ActCode already performed Definition:The requested action has already been performed and so this request has no effect
FULFIL http://terminology.hl7.org/CodeSystem/v3-ActCode fulfillment alert Definition:The therapy being performed is in some way out of alignment with the requested therapy.
NOTACTN http://terminology.hl7.org/CodeSystem/v3-ActCode no longer actionable Definition:The status of the request being fulfilled has changed such that it is no longer actionable. This responsibility may be ethical, legal, contractual, fiscal, because the request has expired, has already been completely fulfilled or fiduciary has been otherwise stopped or disabled. (Not used for 'suspended' orders.)
NOTEQUIV http://terminology.hl7.org/CodeSystem/v3-ActCode not equivalent alert Definition:The therapy being performed is not sufficiently equivalent to the therapy which was requested.
NOTEQUIVGEN http://terminology.hl7.org/CodeSystem/v3-ActCode not generically equivalent alert Definition:The therapy being performed is not generically equivalent (having the identical biological action) to the therapy which was requested.
NOTEQUIVTHER http://terminology.hl7.org/CodeSystem/v3-ActCode not therapeutically equivalent alert Definition:The therapy being performed is not therapeutically equivalent (having the same overall patient effect) to the therapy which was requested.
TIMING http://terminology.hl7.org/CodeSystem/v3-ActCode event timing incorrect alert Definition:The therapy is being performed at a time which diverges from the time the therapy was requested
INTERVAL http://terminology.hl7.org/CodeSystem/v3-ActCode outside requested time Definition:The therapy action is being performed outside the bounds of the time period requested
MINFREQ http://terminology.hl7.org/CodeSystem/v3-ActCode too soon within frequency based on the usage Definition:The therapy action is being performed too soon after the previous occurrence based on the requested frequency
HELD http://terminology.hl7.org/CodeSystem/v3-ActCode held/suspended alert Definition:There should be no actions taken in nature. Example: fulfillment of a request that has been held or suspended.
TOOLATE http://terminology.hl7.org/CodeSystem/v3-ActCode Refill Too Late Alert The patient is receiving a subsequent fill significantly later than would be expected based on the amount previously supplied and the therapy dosage instructions
TOOSOON http://terminology.hl7.org/CodeSystem/v3-ActCode Refill Too Soon Alert The patient is receiving a subsequent fill significantly earlier than would be expected based on the amount previously supplied and the therapy dosage instructions
HISTORIC http://terminology.hl7.org/CodeSystem/v3-ActCode record recorded as historical Description: While the record was accepted in the repository, there is a more recent version of a record of this type.
PATPREF http://terminology.hl7.org/CodeSystem/v3-ActCode violates stated preferences Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record.
PATPREFALT http://terminology.hl7.org/CodeSystem/v3-ActCode violates stated preferences, alternate available Definition:The proposed therapy goes against preferences or consent constraints recorded in the patient's record. An alternate therapy meeting those constraints is available.
KSUBJ http://terminology.hl7.org/CodeSystem/v3-ActCode knowledge subject Categorization of types of observation that capture the main clinical knowledge subject which may be a medication, a laboratory test, a disease.
KSUBT http://terminology.hl7.org/CodeSystem/v3-ActCode knowledge subtopic Categorization of types of observation that capture a knowledge subtopic which might be treatment, etiology, or prognosis.
OINT http://terminology.hl7.org/CodeSystem/v3-ActCode intolerance Hypersensitivity resulting in an adverse reaction upon exposure to an agent.
ALG http://terminology.hl7.org/CodeSystem/v3-ActCode Allergy Hypersensitivity to an agent caused by an immunologic response to an initial exposure
DALG http://terminology.hl7.org/CodeSystem/v3-ActCode Drug Allergy An allergy to a pharmaceutical product.
EALG http://terminology.hl7.org/CodeSystem/v3-ActCode Environmental Allergy An allergy to a substance other than a drug or a food. E.g. Latex, pollen, etc.
FALG http://terminology.hl7.org/CodeSystem/v3-ActCode Food Allergy An allergy to a substance generally consumed for nutritional purposes.
DINT http://terminology.hl7.org/CodeSystem/v3-ActCode Drug Intolerance Hypersensitivity resulting in an adverse reaction upon exposure to a drug.
DNAINT http://terminology.hl7.org/CodeSystem/v3-ActCode Drug Non-Allergy Intolerance Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure
EINT http://terminology.hl7.org/CodeSystem/v3-ActCode Environmental Intolerance Hypersensitivity resulting in an adverse reaction upon exposure to environmental conditions.
ENAINT http://terminology.hl7.org/CodeSystem/v3-ActCode Environmental Non-Allergy Intolerance Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure
FINT http://terminology.hl7.org/CodeSystem/v3-ActCode Food Intolerance Hypersensitivity resulting in an adverse reaction upon exposure to food.
FNAINT http://terminology.hl7.org/CodeSystem/v3-ActCode Food Non-Allergy Intolerance Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure
NAINT http://terminology.hl7.org/CodeSystem/v3-ActCode Non-Allergy Intolerance Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure
SEV http://terminology.hl7.org/CodeSystem/v3-ActCode Severity Observation A person who subjective evaluation of the seriousness or intensity associated with another observation.
_FDALabelData http://terminology.hl7.org/CodeSystem/v3-ActCode FDALabelData FDA label data
FDACOATING http://terminology.hl7.org/CodeSystem/v3-ActCode coating FDA label coating
FDACOLOR http://terminology.hl7.org/CodeSystem/v3-ActCode color FDA label color
FDAIMPRINTCD http://terminology.hl7.org/CodeSystem/v3-ActCode imprint code FDA label imprint code
FDALOGO http://terminology.hl7.org/CodeSystem/v3-ActCode logo FDA label logo
FDASCORING http://terminology.hl7.org/CodeSystem/v3-ActCode scoring FDA label scoring
FDASHAPE http://terminology.hl7.org/CodeSystem/v3-ActCode shape FDA label shape
FDASIZE http://terminology.hl7.org/CodeSystem/v3-ActCode size FDA label size
_ROIOverlayShape http://terminology.hl7.org/CodeSystem/v3-ActCode ROIOverlayShape Shape of the region on the object being referenced
CIRCLE http://terminology.hl7.org/CodeSystem/v3-ActCode circle A circle defined by two (column,row) pairs. The first point is the head center of the circle and the second point is a biochemical laboratory; point on the perimeter of the circle.
ELLIPSE http://terminology.hl7.org/CodeSystem/v3-ActCode ellipse 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.
POINT http://terminology.hl7.org/CodeSystem/v3-ActCode point A single point denoted by a sponsor single (column,row) pair, or multiple points each denoted by a (column,row) pair.
POLY http://terminology.hl7.org/CodeSystem/v3-ActCode polyline 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.
C http://terminology.hl7.org/CodeSystem/v3-ActCode corrected Description:Indicates that result data has been corrected.
DIET http://terminology.hl7.org/CodeSystem/v3-ActCode Diet Code set to define specialized/allowed diets
BR http://terminology.hl7.org/CodeSystem/v3-ActCode breikost (GE) A diet exclusively composed of oatmeal, semolina, or rice, to be extremely easy to eat and digest.
DM http://terminology.hl7.org/CodeSystem/v3-ActCode diabetes mellitus diet A diet that uses carbohydrates sparingly. Typically with a restriction in daily energy content (e.g. 1600-2000 kcal).
FAST http://terminology.hl7.org/CodeSystem/v3-ActCode fasting No enteral intake of foot or liquids whatsoever, no smoking. Typically 6 to 8 hours before anesthesia.
FORMULA http://terminology.hl7.org/CodeSystem/v3-ActCode formula diet 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.
GF http://terminology.hl7.org/CodeSystem/v3-ActCode gluten free Gluten free diet for celiac disease.
LF http://terminology.hl7.org/CodeSystem/v3-ActCode low fat A diet low in fat, particularly to patients with hepatic diseases.
LP http://terminology.hl7.org/CodeSystem/v3-ActCode low protein A low protein diet for patients with renal failure.
LQ http://terminology.hl7.org/CodeSystem/v3-ActCode liquid A strictly liquid diet, that can be fully absorbed in the intestine, and therefore may not contain fiber. Used before enteral surgeries.
LS http://terminology.hl7.org/CodeSystem/v3-ActCode low sodium A diet low in sodium for patients with congestive heart failure and/or renal failure.
N http://terminology.hl7.org/CodeSystem/v3-ActCode normal diet 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.
NF http://terminology.hl7.org/CodeSystem/v3-ActCode no fat A no fat diet for acute hepatic diseases.
PAF http://terminology.hl7.org/CodeSystem/v3-ActCode phenylalanine free Phenylketonuria diet.
PAR http://terminology.hl7.org/CodeSystem/v3-ActCode parenteral Patient is supplied with parenteral nutrition, typically described in terms of i.v. medications.
RD http://terminology.hl7.org/CodeSystem/v3-ActCode reduction diet A diet that seeks to reduce body fat, typically low energy content (800-1600 kcal).
SCH http://terminology.hl7.org/CodeSystem/v3-ActCode schonkost (GE) A diet that avoids ingredients that might cause digestion problems, e.g., avoid excessive fat, avoid too much fiber (cabbage, peas, beans).
SUPPLEMENT http://terminology.hl7.org/CodeSystem/v3-ActCode nutritional supplement A diet that is not intended to be complete but is added to other diets.
T http://terminology.hl7.org/CodeSystem/v3-ActCode tea only This is not really a policy diet, since it contains little nutritional value, but is essentially just water. Used before coloscopy examinations.
VLI http://terminology.hl7.org/CodeSystem/v3-ActCode low valin, leucin, isoleucin Diet with low content of the amino-acids valin, leucin, and isoleucin, for "maple syrup disease."
DRUGPRG http://terminology.hl7.org/CodeSystem/v3-ActCode drug program Definition: A public or government program. health program that administers and funds coverage for prescription drugs to assist program eligible who meet financial and health status criteria.
VRF F http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode verifier final 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.
PRLMN http://terminology.hl7.org/CodeSystem/v3-ActCode preliminary 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.
SECOBS http://terminology.hl7.org/CodeSystem/v3-ActCode SecurityObservationType 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. 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: 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: 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".
SECCATOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security category observation 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." Rationale: A person who verifies security category observation supports requirement to specify the correctness 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] Examples: Types of security categories include: 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 appropriateness 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)
SECCLASSOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security classification observation Type of security metadata observation made about the service (plan, order, event, etc.) 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 hence takes the risk of financial, reputational, or other harm that could result from unauthorized disclosure. 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 accountability. parameters beyond the original assignment of an Act or Role confidentiality. 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. Usage Note: Security classification observation type codes designate security label field types, which are valued with an applicable SecurityClassificationObservationValue code as the "security label tag".
AUTHEN SECCONOBS http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode authenticator security control observation 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. 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] Examples: Types of security control metadata include: handling caveats dissemination controls obligations refrain policies purpose of use constraints
SECINTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security integrity observation 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. Rationale: A verifier who attests 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) Examples: Types of security integrity metadata include: 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 act, but who does IT resource
SECALTINTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security alteration integrity observation 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. 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: translation syntactic transformation semantic mapping redaction masking pseudonymization anonymization
SECDATINTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security data integrity observation 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 have privileges 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." Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature.
SECINTCONOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security integrity confidence observation 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 legally authenticate make access control decisions. Examples: Types of security integrity confidence observation metadata, which may value the act. An example would observation, include highly reliable, uncertain reliability, and not reliable. 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.
SECINTPRVOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security integrity provenance observation 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. Examples: Types of security integrity provenance observation metadata, which may value the observation about an IT resource, include: completeness or workflow status, such as authentication the entity responsible for original authoring or informing about an IT resource the entity responsible for a resident physician who sees report or assertion about an IT resource relayed “second-hand� the entity responsible for excerpting, transforming, or compiling an IT resource
SECINTPRVABOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security integrity provenance asserted by observation 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. Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including: assertions about an IT resource by a patient and dictates assertions about an IT resource by a note, then later signs it. Their signature constitutes clinician assertions about an authentication. IT resource by a device
LA SECINTPRVRBOBS http://terminology.hl7.org/CodeSystem/v3-ParticipationType http://terminology.hl7.org/CodeSystem/v3-ActCode legal authenticator security integrity provenance reported by observation A verifier who legally authenticates Type of security metadata observation made about the accuracy integrity provenance of an act. 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. Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include: reports about an IT resource by a patient reports about an IT resource by a clinician reports about an IT resource by a device
SECINTSTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode security integrity status observation 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. 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.
SECTRSTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode SECTRSTOBS An example would observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a staff physician who sees trust attribute to populate a patient 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 dictates access control decisions.
TRSTACCRDOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust accreditation observation 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 note, then later signs it. Their signature constitutes security domain or trust framework.
TRSTAGREOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust agreement observation Type of security metadata observation made about privacy and security requirements with which a legal authentication. security domain must comply. [ISO IEC 10181-1]
TRSTCERTOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust certificate observation 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] For example, 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.]
TRSTFWKOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust framework observation 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]
TRSTLOAOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust assurance observation Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.
TRSTMECOBS http://terminology.hl7.org/CodeSystem/v3-ActCode trust mechanism observation Type of security metadata observation made about a security architecture system component that supports enforcement of security policies.
SUBSIDFFS http://terminology.hl7.org/CodeSystem/v3-ActCode subsidized fee for service program 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. 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.
WRKCOMP http://terminology.hl7.org/CodeSystem/v3-ActCode (workers compensation program 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.
_ActProcedureCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActProcedureCode An identifying code for healthcare interventions/procedures.
_ActBillableServiceCode http://terminology.hl7.org/CodeSystem/v3-ActCode ActBillableServiceCode Definition: An identifying code for billable services, as opposed to codes for similar services used to identify them for functional purposes.
_HL7DefinedActCodes http://terminology.hl7.org/CodeSystem/v3-ActCode HL7DefinedActCodes Domain provides the root for HL7-defined detailed or rich codes for the Act classes.
COPAY http://terminology.hl7.org/CodeSystem/v3-ActCode
DEDUCT http://terminology.hl7.org/CodeSystem/v3-ActCode
DOSEIND http://terminology.hl7.org/CodeSystem/v3-ActCode
PRA http://terminology.hl7.org/CodeSystem/v3-ActCode

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code