# Resources

Type: ValueSet
Id: v2-0951
Web: ValueSet-v2-0951.html
Url: http://terminology.hl7.org/ValueSet/v2-0951
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Hl7VSReasonForStudy
Title: hl7VS-ReasonForStudy
Experimental: false
Description:
Value Set of codes that provide additional information to the universal service identifier on why a test, study or review was ordered.


Type: ValueSet
Id: v2-0952
Web: ValueSet-v2-0952.html
Url: http://terminology.hl7.org/ValueSet/v2-0952
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Confidentiality
Title: Confidentiality
Experimental: false
Description:
Concepts drawn from the HL7 V3 Confidentiality code system .
Used in Version 2 messaging in the Security Classification elements  in the Message Header segment (MSH) and the Access Restrictions segment (ARV).


Type: ValueSet
Id: v2-0959
Web: ValueSet-v2-0959.html
Url: http://terminology.hl7.org/ValueSet/v2-0959
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: WorkClassificationODH
Title: workClassificationODH
Experimental: false
Description:
A person’s employment type as defined by compensation and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.).


Type: ValueSet
Id: v2-4000
Web: ValueSet-v2-4000.html
Url: http://terminology.hl7.org/ValueSet/v2-4000
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Hl7VSNameAddressRepresentation
Title: hl7VS-name-addressRepresentation
Experimental: false
Description:
Value Set of codes that provide an indication of the kind of representation provided by a name or address, but does not necessarily specify the character sets used for the data.  It is used to provides hints for a receiver, so it can make choic


Type: ValueSet
Id: v2-notAllCodes-0291
Web: ValueSet-v2-notAllCodes-0291.html
Url: http://terminology.hl7.org/ValueSet/v2-notAllCodes-0291
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Hl7VSSubtypeOfReferencedData
Title: hl7VS-subtypeOfReferencedData
Experimental: false
Description:
A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream.


Type: ValueSet
Id: v2-notAllCodes-0347
Web: ValueSet-v2-notAllCodes-0347.html
Url: http://terminology.hl7.org/ValueSet/v2-notAllCodes-0347
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Hl7VsStateProvince
Title: HL7 Value Set for State/Province
Experimental: false
Description:
Concepts used to specify a state or province.  Used in Version 2 messaging in the Extended Composite ID with Check Digit (CX), Performing Person Time Stamp (PPN), and Extended Composite ID Number and Name for Persons (XCN) values as well as the Accident (ACC) segment.


Type: ValueSet
Id: v2-notAllCodes-0399
Web: ValueSet-v2-notAllCodes-0399.html
Url: http://terminology.hl7.org/ValueSet/v2-notAllCodes-0399
Version: 2.0.0
Status: active
Date: 2019-12-01
Name: Hl7VSCountryCode3
Title: hl7VS-countryCode-3alpha
Experimental: false
Description:
Value Set of codes that identifies a country of origin for a message.  It will be used primarily to specify default elements, such as currency denominations. The values to be used are those of ISO 3166. The ISO 3166 table has three separate forms for the codes for each country, this value set includes only the 3-character alpha form.


Type: CodeSystem
Id: v3-AcknowledgementCondition
Web: CodeSystem-v3-AcknowledgementCondition.html
Url: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementCondition
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: AcknowledgementCondition
Title: AcknowledgementCondition
Experimental: false
content: complete
Description:
The codes identify the conditions under which accept acknowledgements are required to be returned in response to this message. Note that accept acknowledgement address two different issues at the same time: reliable transport as well as syntactical correctness


Type: CodeSystem
Id: v3-AcknowledgementDetailType
Web: CodeSystem-v3-AcknowledgementDetailType.html
Url: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: AcknowledgementDetailType
Title: AcknowledgementDetailType
Experimental: false
content: complete
Description:
A code identifying the specific message to be provided.

*Discussion:* A textual value may be specified as the print name, or for non-coded messages, as the original text.

*Examples:* 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'


Type: CodeSystem
Id: v3-AcknowledgementType
Web: CodeSystem-v3-AcknowledgementType.html
Url: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: AcknowledgementType
Title: AcknowledgementType
Experimental: false
content: complete
Description:
This attribute contains an acknowledgement code as described in the HL7 message processing rules.

*OpenIssue:* Description was copied from attribute and needs to be improved to be appropriate for a code system.


Type: CodeSystem
Id: v3-ActClass
Web: CodeSystem-v3-ActClass.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActClass
Version: 4.0.0
Status: active
Date: 2019-03-20
Name: ActClass
Title: ActClass
Experimental: false
content: complete
Description:
A code specifying the major type of Act that this Act-instance represents.

*Constraints:* The classCode domain is a tightly controlled vocabulary, not an external or user-defined vocabulary.

Every Act-instance must have a classCode. If the act class is not further specified, the most general Act.classCode (ACT) is used.

The Act.classCode must be a generalization of the specific Act concept (e.g., as expressed in Act.code), in other words, the Act concepts conveyed in an Act must be specializations of the Act.classCode. Especially, Act.code is not a "modifier" that can alter the meaning of a class code. (See Act.code for contrast.)


Type: CodeSystem
Id: v3-ActCode
Web: CodeSystem-v3-ActCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActCode
Version: 9.0.0
Status: active
Date: 2023-05-30
Name: ActCode
Title: ActCode
Experimental: false
content: complete
Description:
A code specifying the particular kind of Act that the Act-instance represents within its class.

*Constraints:* The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc.

Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure.

Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted.


Type: CodeSystem
Id: v3-ActExposureLevelCode
Web: CodeSystem-v3-ActExposureLevelCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActExposureLevelCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActExposureLevelCode
Title: ActExposureLevelCode
Experimental: false
content: complete
Description:
A qualitative measure of the degree of exposure to the causative agent. This includes concepts such as "low", "medium" and "high". This quantifies how the quantity that was available to be administered to the target differs from typical or background levels of the substance.


Type: CodeSystem
Id: v3-ActMood
Web: CodeSystem-v3-ActMood.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActMood
Version: 3.0.0
Status: active
Date: 2023-05-30
Name: ActMood
Title: ActMood
Experimental: false
content: complete
Description:
OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM.


Type: CodeSystem
Id: v3-ActPriority
Web: CodeSystem-v3-ActPriority.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActPriority
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActPriority
Title: ActPriority
Experimental: false
content: complete
Description:
A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.


Type: CodeSystem
Id: v3-ActReason
Web: CodeSystem-v3-ActReason.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActReason
Version: 3.1.0
Status: active
Date: 2024-02-28
Name: ActReason
Title: ActReason
Experimental: false
content: complete
Description:
A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act.

*Examples:* Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".


Type: CodeSystem
Id: v3-ActRelationshipCheckpoint
Web: CodeSystem-v3-ActRelationshipCheckpoint.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipCheckpoint
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActRelationshipCheckpoint
Title: ActRelationshipCheckpoint
Experimental: false
content: complete
Description:
A code specifying when in the course of an Act a precondition for the Act is evaluated (e.g., before the Act starts for the first time, before every repetition, after each repetition but not before the first, or throughout the entire time of the Act.)

*Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Before each step is executed and has preconditions these conditions are tested and if the test is positive, the Act has clearance for execution. The repeatNumber may indicate that an Act may be repeatedly executed. The checkpointCode is specifies when the precondition is checked and is analogous to the various conditional statements and loop constructs in programming languages "while-do" vs. "do-while" or "repeat-until" vs. "loop-exit".

For all checkpointCodes, except "end", preconditions are being checked at the time when the preceding step of the plan has terminated and this step would be next in the sequence established by the sequenceNumber attribute.

When the checkpointCode for a criterion of a repeatable Act is "end", the criterion is tested only at the end of each repetition of that Act. When the condition holds true, the next repetition is ready for execution.

When the checkpointCode is "entry" the criterion is checked at the beginning of each repetition (if any) whereas "beginning" means the criterion is checked only once before the repetition "loop" starts.

The checkpointCode "through" is special in that it requires the condition to hold throughout the execution of the Act, even throughout a single execution. As soon as the condition turns false, the Act should receive an interrupt event (see interruptibleInd) and will eventually terminate.

The checkpointCode "exit" is only used on a special plan step that represents a loop exit step. This allows an action plan to exit due to a condition tested inside the execution of this plan. Such exit criteria are sequenced with the other plan components using the ActRelationship.sequenceNumber.


Type: CodeSystem
Id: v3-ActRelationshipJoin
Web: CodeSystem-v3-ActRelationshipJoin.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipJoin
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActRelationshipJoin
Title: ActRelationshipJoin
Experimental: false
content: complete
Description:
A code specifying how concurrent Acts are resynchronized in a parallel branch construct.

*Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. Branches are parallel if the splitCode specifies that more than one branch can be executed at the same time. The joinCode then specifies if and how the braches are resynchronized.

The principal re-synchronization actions are (1) the control flow waits for a branch to terminate (wait-branch), (2) the branch that is not yet terminated is aborted (kill-branch), (3) the branch is not re-synchronized at all and continues in parallel (detached branch).

A kill branch is only executed if there is at least one active wait (or exclusive wait) branch. If there is no other wait branch active, a kill branch is not started at all (rather than being aborted shortly after it is started.) Since a detached branch is unrelated to all other branches, active detached branches do not protect a kill-branch from being aborted.


Type: CodeSystem
Id: v3-ActRelationshipSplit
Web: CodeSystem-v3-ActRelationshipSplit.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSplit
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActRelationshipSplit
Title: ActRelationshipSplit
Experimental: false
content: complete
Description:
A code specifying how branches in an action plan are selected among other branches.

*Discussion:* This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches.

In addition to exlusive and inclusive split the splitCode specifies how the pre-condition (also known as "guard conditions" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true.

In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.


Type: CodeSystem
Id: v3-ActRelationshipSubset
Web: CodeSystem-v3-ActRelationshipSubset.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSubset
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActRelationshipSubset
Title: ActRelationshipSubset
Experimental: false
content: complete
Description:
Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.  Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.


Type: CodeSystem
Id: v3-ActStatus
Web: CodeSystem-v3-ActStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActStatus
Title: ActStatus
Experimental: false
content: complete
Description:
Codes representing the defined possible states of an Act, as defined by the Act class state machine.


Type: CodeSystem
Id: v3-ActUSPrivacyLaw
Web: CodeSystem-v3-ActUSPrivacyLaw.html
Url: http://terminology.hl7.org/CodeSystem/v3-ActUSPrivacyLaw
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActUSPrivacyLaw
Title: ActUSPrivacyLaw
Experimental: false
content: complete
Description:
A jurisdictional mandate in the US relating to privacy.

***Deprecation Comment:*** Content moved to ActCode under \_ActPrivacyLaw; use that instead.


Type: CodeSystem
Id: v3-AddressPartType
Web: CodeSystem-v3-AddressPartType.html
Url: http://terminology.hl7.org/CodeSystem/v3-AddressPartType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: AddressPartType
Title: AddressPartType
Experimental: false
content: complete
Description:
**Description:** Code that specifies whether an address part names the street, city, country, postal code, post box, etc.

Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"


Type: CodeSystem
Id: v3-CodingRationale
Web: CodeSystem-v3-CodingRationale.html
Url: http://terminology.hl7.org/CodeSystem/v3-CodingRationale
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: CodingRationale
Title: CodingRationale
Experimental: false
content: complete
Description:
Identifies how to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values:

SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination)

There may be additional values added to this value set as we work through the use of codes in messages and determine other Use Cases requiring special interpretation of the translations.


Type: CodeSystem
Id: v3-CommunicationFunctionType
Web: CodeSystem-v3-CommunicationFunctionType.html
Url: http://terminology.hl7.org/CodeSystem/v3-CommunicationFunctionType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: CommunicationFunctionType
Title: CommunicationFunctionType
Experimental: false
content: complete
Description:
Describes the type of communication function that the associated entity plays in the associated transmission.


Type: CodeSystem
Id: v3-Confidentiality
Web: CodeSystem-v3-Confidentiality.html
Url: http://terminology.hl7.org/CodeSystem/v3-Confidentiality
Version: 3.0.0
Status: active
Date: 2023-05-30
Name: Confidentiality
Title: Confidentiality
Experimental: false
content: complete
Description:
A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality".


Type: CodeSystem
Id: v3-ContainerSeparator
Web: CodeSystem-v3-ContainerSeparator.html
Url: http://terminology.hl7.org/CodeSystem/v3-ContainerSeparator
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ContainerSeparator
Title: ContainerSeparator
Experimental: false
content: complete
Description:
A material in a blood collection container that facilites the separation of of blood cells from serum or plasma


Type: CodeSystem
Id: v3-ContextControl
Web: CodeSystem-v3-ContextControl.html
Url: http://terminology.hl7.org/CodeSystem/v3-ContextControl
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ContextControl
Title: ContextControl
Experimental: false
content: complete
Description:
A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd).


Type: CodeSystem
Id: v3-EntityClass
Web: CodeSystem-v3-EntityClass.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityClass
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityClass
Title: EntityClass
Experimental: false
content: complete
Description:
Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing.


Type: CodeSystem
Id: v3-EntityDeterminer
Web: CodeSystem-v3-EntityDeterminer.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityDeterminer
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityDeterminer
Title: EntityDeterminer
Experimental: false
content: complete
Description:
EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing.


Type: CodeSystem
Id: v3-EntityHandling
Web: CodeSystem-v3-EntityHandling.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityHandling
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityHandling
Title: EntityHandling
Experimental: false
content: complete
Description:
Special handling requirements for an Entity.

*Example:*Keep at room temperature; Keep frozen below 0 C; Keep in a dry environment; Keep upright, do not turn upside down.


Type: CodeSystem
Id: v3-EntityNamePartQualifierR2
Web: CodeSystem-v3-EntityNamePartQualifierR2.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityNamePartQualifierR2
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityNamePartQualifierR2
Title: EntityNamePartQualifierR2
Experimental: false
content: complete
Description:
**Description:**The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records.


Type: CodeSystem
Id: v3-EntityNameUseR2
Web: CodeSystem-v3-EntityNameUseR2.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityNameUseR2
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityNameUseR2
Title: EntityNameUseR2
Experimental: false
content: complete
Description:
**Description:**A set of codes advising a system or user which name in a set of names to select for a given purpose.


Type: CodeSystem
Id: v3-EntityStatus
Web: CodeSystem-v3-EntityStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-EntityStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: EntityStatus
Title: EntityStatus
Experimental: false
content: complete
Description:
Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.


Type: CodeSystem
Id: v3-Ethnicity
Web: CodeSystem-v3-Ethnicity.html
Url: http://terminology.hl7.org/CodeSystem/v3-Ethnicity
Version: 4.0.0
Status: active
Date: 2022-01-30
Name: Ethnicity
Title: Ethnicity
Experimental: false
content: complete
Description:
**Deprecation Information:** Deprecated due to UP-265. This code system in NOT the acknowledged source of truth for Ethnicity concepts and codes. It should no longer be used. https://terminology.hl7.org/CodeSystem-CDCREC.html should be used in its place. In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.


Type: CodeSystem
Id: v3-ExposureMode
Web: CodeSystem-v3-ExposureMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ExposureMode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ExposureMode
Title: ExposureMode
Experimental: false
content: complete
Description:
Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.


Type: CodeSystem
Id: v3-GTSAbbreviation
Web: CodeSystem-v3-GTSAbbreviation.html
Url: http://terminology.hl7.org/CodeSystem/v3-GTSAbbreviation
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: GTSAbbreviation
Title: GTSAbbreviation
Experimental: false
content: complete
Description:
*Open Issue:* It appears that the printnames are suboptimal and should be improved for many of the existing codes.


Type: CodeSystem
Id: v3-HL7ContextConductionStyle
Web: CodeSystem-v3-HL7ContextConductionStyle.html
Url: http://terminology.hl7.org/CodeSystem/v3-HL7ContextConductionStyle
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: HL7ContextConductionStyle
Title: HL7ContextConductionStyle
Experimental: false
content: complete
Description:
The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.


Type: CodeSystem
Id: v3-HL7DefinedRoseProperty
Web: CodeSystem-v3-HL7DefinedRoseProperty.html
Url: http://terminology.hl7.org/CodeSystem/v3-HL7DefinedRoseProperty
Version: 3.0.0
Status: retired
Date: 2019-03-20
Name: HL7DefinedRoseProperty
Title: HL7DefinedRoseProperty
Experimental: false
content: complete
Description:
The property Ids that HL7 has defined for customizing Rational Rose.

**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.


Type: CodeSystem
Id: v3-HL7DocumentFormatCodes
Web: CodeSystem-v3-HL7DocumentFormatCodes.html
Url: http://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodes
Version: 4.1.0
Status: active
Date: 2024-11-10
Name: HL7DocumentFormatCodes
Title: HL7 Document Format Codes
Experimental: false
content: complete
Description:
This codeSystem contains codes which specify the technical format of a document. Each code provides sufficient information to allow any potential document consumer to know if it will be able to process the document. The codes are sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. For example, formatCodes can be used in the FHIR DocumentReference resource to characterize the document being referenced.


Type: CodeSystem
Id: v3-HL7StandardVersionCode
Web: CodeSystem-v3-HL7StandardVersionCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-HL7StandardVersionCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: HL7StandardVersionCode
Title: HL7StandardVersionCode
Experimental: false
content: complete
Description:
This code system holds version codes for the Version 3 standards. Values are to be determined by HL7 and added with each new version of the HL7 Standard.


Type: CodeSystem
Id: v3-HL7UpdateMode
Web: CodeSystem-v3-HL7UpdateMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-HL7UpdateMode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: HL7UpdateMode
Title: HL7UpdateMode
Experimental: false
content: complete
Description:
The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.


Type: CodeSystem
Id: v3-HtmlLinkType
Web: CodeSystem-v3-HtmlLinkType.html
Url: http://terminology.hl7.org/CodeSystem/v3-HtmlLinkType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: HtmlLinkType
Title: HtmlLinkType
Experimental: false
content: complete
Description:
HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link


Type: CodeSystem
Id: v3-IdentifierReliability
Web: CodeSystem-v3-IdentifierReliability.html
Url: http://terminology.hl7.org/CodeSystem/v3-IdentifierReliability
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: IdentifierReliability
Title: IdentifierReliability
Experimental: false
content: complete
Description:
Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.


Type: CodeSystem
Id: v3-IdentifierScope
Web: CodeSystem-v3-IdentifierScope.html
Url: http://terminology.hl7.org/CodeSystem/v3-IdentifierScope
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: IdentifierScope
Title: IdentifierScope
Experimental: false
content: complete
Description:
**Description:** Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.


Type: CodeSystem
Id: v3-LanguageAbilityMode
Web: CodeSystem-v3-LanguageAbilityMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-LanguageAbilityMode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: LanguageAbilityMode
Title: LanguageAbilityMode
Experimental: false
content: complete
Description:
A value representing the method of expression of the language.

*Example:*Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.

*OpenIssue:* Description copied from Concept Domain of same name. Must be verified.


Type: CodeSystem
Id: v3-LanguageAbilityProficiency
Web: CodeSystem-v3-LanguageAbilityProficiency.html
Url: http://terminology.hl7.org/CodeSystem/v3-LanguageAbilityProficiency
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: LanguageAbilityProficiency
Title: LanguageAbilityProficiency
Experimental: false
content: complete
Description:
A value representing the level of proficiency in a language.

*Example:*Excellent, good, fair, poor.

*OpenIssue:* Description copied from Concept Domain of same name. Must be verified.


Type: CodeSystem
Id: v3-LocalMarkupIgnore
Web: CodeSystem-v3-LocalMarkupIgnore.html
Url: http://terminology.hl7.org/CodeSystem/v3-LocalMarkupIgnore
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: LocalMarkupIgnore
Title: LocalMarkupIgnore
Experimental: false
content: complete
Description:
Tells a receiver to ignore just the local markup tags (local\_markup, local\_header, local\_attr) when value="markup", or to ignore the local markup tags and all contained content when value="all"


Type: CodeSystem
Id: v3-LocalRemoteControlState
Web: CodeSystem-v3-LocalRemoteControlState.html
Url: http://terminology.hl7.org/CodeSystem/v3-LocalRemoteControlState
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: LocalRemoteControlState
Title: LocalRemoteControlState
Experimental: false
content: complete
Description:
A value representing the current state of control associated with the device.

*Examples:* A device can either work autonomously (localRemoteControlStateCode="Local") or it can be controlled by another system (localRemoteControlStateCode="Remote").

*Rationale:* The control status of a device must be communicated between devices prior to remote commands being transmitted. If the device is not in "Remote" status then external commands will be ignored.


Type: CodeSystem
Id: v3-ManagedParticipationStatus
Web: CodeSystem-v3-ManagedParticipationStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-ManagedParticipationStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ManagedParticipationStatus
Title: ManagedParticipationStatus
Experimental: false
content: complete
Description:
Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine.


Type: CodeSystem
Id: v3-ManufacturerModelNameExample
Web: CodeSystem-v3-ManufacturerModelNameExample.html
Url: http://terminology.hl7.org/CodeSystem/v3-ManufacturerModelNameExample
Version: 2.0.0
Status: active
Date: 2022-10-11
Name: ManufacturerModelNameExample
Title: ManufacturerModelNameExample
Experimental: true
content: complete
Description:
This code system serves to capture the ManufacturerModelName concept domain used to convey a coded name for a device.


Type: CodeSystem
Id: v3-MapRelationship
Web: CodeSystem-v3-MapRelationship.html
Url: http://terminology.hl7.org/CodeSystem/v3-MapRelationship
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: MapRelationship
Title: MapRelationship
Experimental: false
content: complete
Description:
The closeness or quality of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and the source coding system. The values are patterned after the similar relationships used in the UMLS Metathesaurus. Because the HL7 coding sy


Type: CodeSystem
Id: v3-MaritalStatus
Web: CodeSystem-v3-MaritalStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-MaritalStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: MaritalStatus
Title: MaritalStatus
Experimental: false
content: complete
Description:
\* \* \* No description supplied \* \* \*

*Open Issue:* The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency.

*Open Issue:* fixing and completion of the hierarchy and proper good definitions of all the concepts is badly needed.


Type: CodeSystem
Id: v3-MessageWaitingPriority
Web: CodeSystem-v3-MessageWaitingPriority.html
Url: http://terminology.hl7.org/CodeSystem/v3-MessageWaitingPriority
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: MessageWaitingPriority
Title: MessageWaitingPriority
Experimental: false
content: complete
Description:
Indicates that the receiver has messages for the sender

*OpenIssue:* Description does not make sense relative to name of coding system. Must be reviewed and improved.


Type: CodeSystem
Id: v3-ObservationCategory
Web: CodeSystem-v3-ObservationCategory.html
Url: http://terminology.hl7.org/CodeSystem/v3-ObservationCategory
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationCategory
Title: ObservationCategory
Experimental: false
content: complete
Description:
High level observation categories for the general type of observation being made.

URL: http://hl7-fhir.github.io/valueset-observation-category.html

This is an inline code system http://hl7.org/fhir/observation-category.


Type: CodeSystem
Id: v3-ObservationInterpretation
Web: CodeSystem-v3-ObservationInterpretation.html
Url: http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationInterpretation
Title: ObservationInterpretation
Experimental: false
content: complete
Description:
One or more codes providing a rough qualitative interpretation of the observation, such as "normal" / "abnormal", "low" / "high", "better" / "worse", "resistant" / "susceptible", "expected" / "not expected". The value set is intended to be for ANY use where coded representation of an interpretation is needed.


Type: CodeSystem
Id: v3-ObservationMethod
Web: CodeSystem-v3-ObservationMethod.html
Url: http://terminology.hl7.org/CodeSystem/v3-ObservationMethod
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationMethod
Title: ObservationMethod
Experimental: false
content: complete
Description:
A code that provides additional detail about the means or technique used to ascertain the observation.

*Examples:* Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.

*OpenIssue:* Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved.


Type: CodeSystem
Id: v3-ObservationValue
Web: CodeSystem-v3-ObservationValue.html
Url: http://terminology.hl7.org/CodeSystem/v3-ObservationValue
Version: 4.0.0
Status: active
Date: 2024-02-28T00:00:00.000-07:00
Name: ObservationValue
Title: ObservationValue
Experimental: false
content: complete
Description:
This code system covers all concepts of HL7-defined values for the Observation value element, when it has a coded datatype.


Type: CodeSystem
Id: v3-ParticipationFunction
Web: CodeSystem-v3-ParticipationFunction.html
Url: http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ParticipationFunction
Title: ParticipationFunction
Experimental: false
content: complete
Description:
This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE).


Type: CodeSystem
Id: v3-ParticipationMode
Web: CodeSystem-v3-ParticipationMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ParticipationMode
Version: 4.0.0
Status: active
Date: 2021-08-10
Name: ParticipationMode
Title: ParticipationMode
Experimental: false
content: complete
Description:
A set of codes specifying the modality by which the Entity playing the Role is participating in the Act.

*Examples:* Physically present, over the telephone, written communication.

*Rationale:* Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically.

*Open Issue:* There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies.


Type: CodeSystem
Id: v3-ParticipationSignature
Web: CodeSystem-v3-ParticipationSignature.html
Url: http://terminology.hl7.org/CodeSystem/v3-ParticipationSignature
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ParticipationSignature
Title: ParticipationSignature
Experimental: false
content: complete
Description:
A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.

*Examples:* A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)


Type: CodeSystem
Id: v3-ParticipationType
Web: CodeSystem-v3-ParticipationType.html
Url: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
Version: 5.0.0
Status: active
Date: 2019-03-20
Name: ParticipationType
Title: ParticipationType
Experimental: false
content: complete
Description:
A code specifying the meaning and purpose of every Participation instance. Each of its values implies specific constraints on the Roles undertaking the participation.


Type: CodeSystem
Id: v3-PaymentTerms
Web: CodeSystem-v3-PaymentTerms.html
Url: http://terminology.hl7.org/CodeSystem/v3-PaymentTerms
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: PaymentTerms
Title: PaymentTerms
Experimental: false
content: complete
Description:
Describes payment terms for a financial transaction, used in an invoice.

This is typically expressed as a responsibility of the acceptor or payor of an invoice.


Type: CodeSystem
Id: v3-ProcessingMode
Web: CodeSystem-v3-ProcessingMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ProcessingMode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ProcessingMode
Title: ProcessingMode
Experimental: false
content: complete
Description:
This attribute defines whether the message is being sent in current processing, archive mode, initial load mode, restore from archive mode, etc.


Type: CodeSystem
Id: v3-QueryRequestLimit
Web: CodeSystem-v3-QueryRequestLimit.html
Url: http://terminology.hl7.org/CodeSystem/v3-QueryRequestLimit
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: QueryRequestLimit
Title: QueryRequestLimit
Experimental: false
content: complete
Description:
**Definition:** Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application.


Type: CodeSystem
Id: v3-QueryResponse
Web: CodeSystem-v3-QueryResponse.html
Url: http://terminology.hl7.org/CodeSystem/v3-QueryResponse
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: QueryResponse
Title: QueryResponse
Experimental: false
content: complete
Description:
A code classifying the general nature of the response to a given query. Includes whether or not data was found, or whether an error occurred.


Type: CodeSystem
Id: v3-Race
Web: CodeSystem-v3-Race.html
Url: http://terminology.hl7.org/CodeSystem/v3-Race
Version: 4.0.0
Status: active
Date: 2022-01-05
Name: Race
Title: Race
Experimental: false
content: complete
Description:
**Deprecation Information:** Deprecated per UP-263. This code system is NOT the acknowledged source of truth for Race concepts and codes. It should no longer be used. https://terminology.hl7.org/CodeSystem-CDCREC.html should be used in its place. In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct in which an individual's own identification with one more race categories is preferred to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories.


Type: CodeSystem
Id: v3-RelationshipConjunction
Web: CodeSystem-v3-RelationshipConjunction.html
Url: http://terminology.hl7.org/CodeSystem/v3-RelationshipConjunction
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: RelationshipConjunction
Title: RelationshipConjunction
Experimental: false
content: complete
Description:
A code specifying the logical conjunction of the criteria among all the condition-links of Acts (e.g., and, or, exclusive-or.)

*Constraints:* All AND criteria must be true. If OR and AND criteria occur together, one criterion out of the OR-group must be true and all AND criteria must be true also. If XOR criteria occur together with OR and AND criteria, exactly one of the XOR criteria must be true, and at least one of the OR criteria and all AND criteria must be true. In other words, the sets of AND, OR, and XOR criteria are in turn combined by a logical AND operator (all AND criteria and at least one OR criterion and exactly one XOR criterion.) To overcome this ordering, Act criteria can be nested in any way necessary.


Type: CodeSystem
Id: v3-ResponseLevel
Web: CodeSystem-v3-ResponseLevel.html
Url: http://terminology.hl7.org/CodeSystem/v3-ResponseLevel
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ResponseLevel
Title: ResponseLevel
Experimental: false
content: complete
Description:
Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include


Type: CodeSystem
Id: v3-ResponseModality
Web: CodeSystem-v3-ResponseModality.html
Url: http://terminology.hl7.org/CodeSystem/v3-ResponseModality
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ResponseModality
Title: ResponseModality
Experimental: false
content: complete
Description:
Defines the timing and grouping of the response instances.

*OpenIssue:* Description copied from Concept Domain of same name. Must be verified.


Type: CodeSystem
Id: v3-ResponseMode
Web: CodeSystem-v3-ResponseMode.html
Url: http://terminology.hl7.org/CodeSystem/v3-ResponseMode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ResponseMode
Title: ResponseMode
Experimental: false
content: complete
Description:
Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.


Type: CodeSystem
Id: v3-RoleClass
Web: CodeSystem-v3-RoleClass.html
Url: http://terminology.hl7.org/CodeSystem/v3-RoleClass
Version: 4.0.0
Status: active
Date: 2019-03-20
Name: RoleClass
Title: RoleClass
Experimental: false
content: complete
Description:
Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.

The role hierarchy stems from three core concepts, or abstract domains:

 *  **RoleClassOntological** is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.
 *  **RoleClassPartitive** collects roles in which the playing entity is in some sense a "part" of the scoping entity.
 *  **RoleClassAssociative** collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:
    
     *  **RoleClassPassive** which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.
     *  **RoleClassMutualRelationship** which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be *de facto* behavior. Thus, this sub-domain is further divided into:
        
         *  **RoleClassRelationshipFormal** in which the relationship is formally defined, frequently by a contract or agreement.
         *  **Personal relationship** which inks two people in a personal relationship.

The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept.

*OpenIssue:* Description copied from Concept Domain of same name. Must be verified.


Type: CodeSystem
Id: v3-RoleCode
Web: CodeSystem-v3-RoleCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-RoleCode
Version: 3.0.0
Status: active
Date: 2019-12-15
Name: RoleCode
Title: RoleCode
Experimental: false
content: complete
Description:
A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.


Type: CodeSystem
Id: v3-RoleLinkStatus
Web: CodeSystem-v3-RoleLinkStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-RoleLinkStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: RoleLinkStatus
Title: RoleLinkStatus
Experimental: false
content: complete
Description:
**Description:**Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.


Type: CodeSystem
Id: v3-RoleLinkType
Web: CodeSystem-v3-RoleLinkType.html
Url: http://terminology.hl7.org/CodeSystem/v3-RoleLinkType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: RoleLinkType
Title: RoleLinkType
Experimental: false
content: complete
Description:
A code specifying the meaning and purpose of every RoleLink instance. Each of its values implies specific constraints to what kinds of Role objects can be related and in which way.


Type: CodeSystem
Id: v3-RoleStatus
Web: CodeSystem-v3-RoleStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-RoleStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: RoleStatus
Title: RoleStatus
Experimental: false
content: complete
Description:
Codes representing the defined possible states of an Role, as defined by the Role class state machine.


Type: CodeSystem
Id: v3-SoftwareNameExample
Web: CodeSystem-v3-SoftwareNameExample.html
Url: http://terminology.hl7.org/CodeSystem/v3-SoftwareNameExample
Version: 2.0.0
Status: active
Date: 2022-10-11
Name: SoftwareNameExample
Title: SoftwareNameExample
Experimental: true
content: complete
Description:
This code system serves to capture the SoftwareName concept domain used to convey a coded name for the software used to author content.


Type: CodeSystem
Id: v3-SubstitutionCondition
Web: CodeSystem-v3-SubstitutionCondition.html
Url: http://terminology.hl7.org/CodeSystem/v3-SubstitutionCondition
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: SubstitutionCondition
Title: SubstitutionCondition
Experimental: false
content: complete
Description:
Identifies what sort of change is permitted or has occurred between the item that was ordered/requested and the one that was/will be provided.


Type: CodeSystem
Id: v3-TargetAwareness
Web: CodeSystem-v3-TargetAwareness.html
Url: http://terminology.hl7.org/CodeSystem/v3-TargetAwareness
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: TargetAwareness
Title: TargetAwareness
Experimental: false
content: complete
Description:
A code specifying the extent to which the Entity playing the participating Role (usually as a target Participation) is aware of the associated Act.

*Examples:* For diagnostic observations, is the patient, family member or other participant aware of his terminal illness?

*Discussion:* If the awareness, denial, unconsciousness, etc. is the subject of medical considerations (e.g., part of the problem list), one should use explicit observations in these matters as well, and should not solely rely on this simple attribute in the Participation.


Type: CodeSystem
Id: v3-TelecommunicationCapabilities
Web: CodeSystem-v3-TelecommunicationCapabilities.html
Url: http://terminology.hl7.org/CodeSystem/v3-TelecommunicationCapabilities
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: TelecommunicationCapabilities
Title: TelecommunicationCapabilities
Experimental: false
content: complete
Description:
**Description:** Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address.


Type: CodeSystem
Id: v3-TransmissionRelationshipTypeCode
Web: CodeSystem-v3-TransmissionRelationshipTypeCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-TransmissionRelationshipTypeCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: TransmissionRelationshipTypeCode
Title: TransmissionRelationshipTypeCode
Experimental: false
content: complete
Description:
**Description:**A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way.


Type: CodeSystem
Id: v3-TribalEntityUS
Web: CodeSystem-v3-TribalEntityUS.html
Url: http://terminology.hl7.org/CodeSystem/v3-TribalEntityUS
Version: 4.0.0
Status: active
Date: 2019-03-20
Name: TribalEntityUS
Title: TribalEntityUS
Experimental: false
content: complete
Description:
INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS


Type: CodeSystem
Id: v3-URLScheme
Web: CodeSystem-v3-URLScheme.html
Url: http://terminology.hl7.org/CodeSystem/v3-URLScheme
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: URLScheme
Title: Universal Resource Locator Scheme
Experimental: false
content: complete
Description:
A Universal Resource Locator (URL) is a type of telecommunications address specified as Internet standard RFC 1738 \[http://www.isi.edu/in-notes/rfc1738.txt\]. The URL specifies the protocol and the contact point defined by that protocol for the resource.


Type: CodeSystem
Id: v3-WorkClassificationODH
Web: CodeSystem-v3-WorkClassificationODH.html
Url: http://terminology.hl7.org/CodeSystem/v3-WorkClassificationODH
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: WorkClassificationODH
Title: Work Classification (Occupational Data for Health)
Experimental: false
content: complete
Description:
Code system of concepts representing a person's job type as defined by compensation and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.).


Type: CodeSystem
Id: v3-hl7ApprovalStatus
Web: CodeSystem-v3-hl7ApprovalStatus.html
Url: http://terminology.hl7.org/CodeSystem/v3-hl7ApprovalStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: Hl7ApprovalStatus
Title: HL7ApprovalStatus
Experimental: false
content: complete
Description:
**Description:** Codes for concepts describing the approval level of HL7 artifacts. This code system reflects the concepts expressed in HL7's Governance & Operations Manual (GOM) past and present.


Type: CodeSystem
Id: v3-hl7ITSVersionCode
Web: CodeSystem-v3-hl7ITSVersionCode.html
Url: http://terminology.hl7.org/CodeSystem/v3-hl7ITSVersionCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: Hl7ITSVersionCode
Title: HL7 ITS Version Code
Experimental: false
content: complete
Description:
HL7 implementation technology specification versions. These codes will document the ITS type and version for message encoding. The code will appear in the instances based upon rules expressed in the ITS, and do not appear in the abstract message, either as it is presented to received from the ITS.


Type: CodeSystem
Id: v3-hl7Realm
Web: CodeSystem-v3-hl7Realm.html
Url: http://terminology.hl7.org/CodeSystem/v3-hl7Realm
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: Hl7Realm
Title: HL7Realm
Experimental: false
content: complete
Description:
**Description:** Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of \_BindingRealm or \_NamespaceRealm. For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters.

*Open Issue:* The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code.

*Open Issue:* In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length.


Type: CodeSystem
Id: v3-hl7VoteResolution
Web: CodeSystem-v3-hl7VoteResolution.html
Url: http://terminology.hl7.org/CodeSystem/v3-hl7VoteResolution
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: Hl7VoteResolution
Title: HL7VoteResolution
Experimental: false
content: complete
Description:
**Description:** Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).


Type: CodeSystem
Id: v3-styleType
Web: CodeSystem-v3-styleType.html
Url: http://terminology.hl7.org/CodeSystem/v3-styleType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: StyleType
Title: Style Type
Experimental: false
content: complete
Description:
The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style.


Type: CodeSystem
Id: v3-substanceAdminSubstitution
Web: CodeSystem-v3-substanceAdminSubstitution.html
Url: http://terminology.hl7.org/CodeSystem/v3-substanceAdminSubstitution
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: SubstanceAdminSubstitution
Title: Substance Admin Substitution
Experimental: false
content: complete
Description:
Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.


Type: CodeSystem
Id: triggerEventID
Web: CodeSystem-triggerEventID.html
Url: http://terminology.hl7.org/CodeSystem/triggerEventID
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: TriggerEventID
Title: Trigger Event ID
Experimental: false
content: fragment
Description:
**Description:** This code system contains all HL7 artifacts of type TE (Trigger Event) that are created by HL7 or its affiliates or their designates using the realm namespacing rules approved by HL7. Local implementations who create trigger events outside of these namespacing rules, (e.g. using the ZZ realm code) must register their own code system. The specific list of legal codes can be found by consulting the HL7 publications (editions, ballots, implementation guides, etc.) published by HL7 Inc. and by the various HL7 affiliates and their designates. Codes shall be expressed in upper case, with separator as shown in HL7 publications with no version id. E.g. PORX\_TE123456UV.


Type: NamingSystem
Id: v3-SpecialArrangement
Web: NamingSystem-v3-SpecialArrangement.html
Url: http://terminology.hl7.org/NamingSystem/v3-SpecialArrangement
Version: 2.1.0
Status: active
Date: 2019-03-20T00:00:00-04:00
Name: SpecialArrangement
Title: SpecialArrangement
Description:
A code indicating the type of special arrangements provided for a patient encounter (e.g., wheelchair, stretcher, interpreter, attendant, seeing eye dog). For encounters in intention moods, this information can be used to identify special arrangements that will need to be made for the incoming patient.


Type: NamingSystem
Id: v3-UnitOfMeasurePrefix
Web: NamingSystem-v3-UnitOfMeasurePrefix.html
Url: http://terminology.hl7.org/NamingSystem/v3-UnitOfMeasurePrefix
Version: 2.2.0
Status: retired
Date: 2019-03-20T00:00:00-04:00
Name: UnitOfMeasurePrefix
Title: Unit of Measure Prefix
Description:
Decimal multipliers for units of measure

**Deprecation Comment:** This code system was created in error. Implementations should use the code system UCUM with OID 2.16.840.1.113883.6.8

Note that due to some tooling issues, some of the synonym codes that differed only in case (upper/lower) were not being assembled into MIF correctly, therefore they have been removed as a workaround for these tooling issues. This should have limited effect as this system has been deprecated for 8 years, and retired for 4 years, and will be removed soon.


Type: NamingSystem
Id: v3-policyHolderRole
Web: NamingSystem-v3-policyHolderRole.html
Url: http://terminology.hl7.org/NamingSystem/v3-policyHolderRole
Version: 3.0.0
Status: active
Date: 2019-03-20T00:00:00-04:00
Name: PolicyHolderRole
Title: Policy Holder Role
Description:
This vocabulary is defined by Implementation Guide for CDA Release 2 - Level 1 - Care Record Summary (US realm).

It describes roles recognized through the issuance of an insurance policy to a policyholder who a relationship with the covered party, such as spouse, child, etc. This vocabulary is essentially an inversion of the role relations of the HL7 CoverageRoleType vocabulary. It provides more detailed roles with respect to the underwriter (the scoping organization) for those participants in the policyholder role for a patient.

*Open Issue:* 

The code values for this coding system must be extracted from the CDA documentation and brought forward through Harmonization for instantiation in this repository.


Type: ValueSet
Id: v3-tst0272
Web: ValueSet-v3-tst0272.html
Url: http://terminology.hl7.org/ValueSet/v3-tst0272
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Tst0272
Title: _0272
Experimental: false
Description:
Testing to measure the minimum concentration of the antibacterial agent in a given culture medium below which bacterial growth is not inhibited.


Type: ValueSet
Id: v3-tst0280
Web: ValueSet-v3-tst0280.html
Url: http://terminology.hl7.org/ValueSet/v3-tst0280
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Tst0280
Title: _0280
Experimental: false
Description:
Test methods designed to determine a microorganismaTMs susceptibility to being killed by an antibiotic.


Type: ValueSet
Id: v3-AcknowledgementCondition
Web: ValueSet-v3-AcknowledgementCondition.html
Url: http://terminology.hl7.org/ValueSet/v3-AcknowledgementCondition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AcknowledgementCondition
Title: AcknowledgementCondition
Experimental: false
Description:
Acknowledgement Condition codes describe the conditions under which accept or application level acknowledgements are required to be returned in response to the message send operation.


Type: ValueSet
Id: v3-AcknowledgementDetailNotSupportedCode
Web: ValueSet-v3-AcknowledgementDetailNotSupportedCode.html
Url: http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailNotSupportedCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AcknowledgementDetailNotSupportedCode
Title: AcknowledgementDetailNotSupportedCode
Experimental: false
Description:
Refelects rejections because elements of the communication are not supported in the current context.


Type: ValueSet
Id: v3-AcknowledgementDetailType
Web: ValueSet-v3-AcknowledgementDetailType.html
Url: http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AcknowledgementDetailType
Title: AcknowledgementDetailType
Experimental: false
Description:
A code identifying the specific message to be provided.

A textual value may be specified as the print name, or for non-coded messages, as the original text.*Discussion:*

'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'*Examples:*


Type: ValueSet
Id: v3-ActAccountCode
Web: ValueSet-v3-ActAccountCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAccountCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAccountCode
Title: ActAccountCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActAdjudicationCode
Web: ValueSet-v3-ActAdjudicationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAdjudicationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAdjudicationCode
Title: ActAdjudicationCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActAdjudicationGroupCode
Web: ValueSet-v3-ActAdjudicationGroupCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAdjudicationGroupCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAdjudicationGroupCode
Title: ActAdjudicationGroupCode
Experimental: false
Description:
Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals).


Type: ValueSet
Id: v3-ActAdministrativeDetectedIssueCode
Web: ValueSet-v3-ActAdministrativeDetectedIssueCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAdministrativeDetectedIssueCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAdministrativeDetectedIssueCode
Title: ActAdministrativeDetectedIssueCode
Experimental: false
Description:
Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains.


Type: ValueSet
Id: v3-ActAdministrativeDetectedIssueManagementCode
Web: ValueSet-v3-ActAdministrativeDetectedIssueManagementCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAdministrativeDetectedIssueManagementCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAdministrativeDetectedIssueManagementCode
Title: ActAdministrativeDetectedIssueManagementCode
Experimental: false
Description:
Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains.


Type: ValueSet
Id: v3-ActAmbulatoryEncounterCode
Web: ValueSet-v3-ActAmbulatoryEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActAmbulatoryEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActAmbulatoryEncounterCode
Title: ActAmbulatoryEncounterCode
Experimental: false
Description:
**Definition:**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.


Type: ValueSet
Id: v3-ActBillingArrangementCode
Web: ValueSet-v3-ActBillingArrangementCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActBillingArrangementCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActBillingArrangementCode
Title: ActBillingArrangementCode
Experimental: false
Description:
The type of provision(s) made for reimbursing for the deliver of healthcare services and/or goods provided by a Provider, over a specified period.


Type: ValueSet
Id: v3-ActCareProvisionCode
Web: ValueSet-v3-ActCareProvisionCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCareProvisionCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCareProvisionCode
Title: ActCareProvisionCode
Experimental: false
Description:
**Description:**The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care.


Type: ValueSet
Id: v3-ActClassAccession
Web: ValueSet-v3-ActClassAccession.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassAccession
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassAccession
Title: ActClassAccession
Experimental: false
Description:
A unit of work, a grouper of work items as defined by the system performing that work. Typically some laboratory order fulfillers communicate references to accessions in their communications regarding laboratory orders. Often one or more specimens are related to an accession such that in some environments the accession number is taken as an identifier for a specimen (group).


Type: ValueSet
Id: v3-ActClassAccommodation
Web: ValueSet-v3-ActClassAccommodation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassAccommodation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassAccommodation
Title: ActClassAccommodation
Experimental: false
Description:
An accommodation is a service provided for a Person or other LivingSubject in which a place is provided for the subject to reside for a period of time. Commonly used to track the provision of ward, private and semi-private accommodations for a patient.


Type: ValueSet
Id: v3-ActClassAcquisitionExposure
Web: ValueSet-v3-ActClassAcquisitionExposure.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassAcquisitionExposure
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassAcquisitionExposure
Title: ActClassAcquisitionExposure
Experimental: false
Description:
**Description:** 

An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity. The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.

**Constraints:** The Acquisition Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPSRC (exposure source) participation must never be associated with the Transmission Exposure either directly or via context conduction.


Type: ValueSet
Id: v3-ActClassAction
Web: ValueSet-v3-ActClassAction.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassAction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassAction
Title: ActClassAction
Experimental: false
Description:
Sender asks addressee to do something depending on the focal Act of the payload. An example is "fulfill this order". Addressee has responsibilities to either reject the message or to act on it in an appropriate way (specified by the specific receiver responsibilities for the interaction).


Type: ValueSet
Id: v3-ActClassBattery
Web: ValueSet-v3-ActClassBattery.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassBattery
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassBattery
Title: ActClassBattery
Experimental: false
Description:
**Description:**A battery specifies a set of observations. These observations typically have a logical or practical grouping for generally accepted clinical or functional purposes, such as observations that are run together because of automation. A battery can define required and optional components and, in some cases, will define complex rules that determine whether or not a particular observation is made.

**Examples:** "Blood pressure", "Full blood count", "Chemistry panel".


Type: ValueSet
Id: v3-ActClassBoundedRoi
Web: ValueSet-v3-ActClassBoundedRoi.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassBoundedRoi
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassBoundedRoi
Title: ActClassBoundedRoi
Experimental: false
Description:
A Region of Interest (ROI) specified for a multidimensional observation, such as an Observation Series (OBSSER). The ROI is specified using a set of observation criteria, each delineating the boundary of the region in one of the dimensions in the multidimensional observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type subject (SUBJ), which must always be present. Each of the boundary criteria observations is connected with the ROI using ActRelationships of type "has component" (COMP). In each boundary criterion, the Act.code names the dimension and the Observation.value specifies the range of values inside the region. Typically the bounded dimension is continuous, and so the Observation.value will be an interval (IVL) data type. The Observation.value need not be specified if the respective dimension is only named but not constrained. For example, an ROI for the QT interval of a certain beat in ECG Lead II would contain 2 boundary criteria, one naming the interval in time (constrained), and the other naming the interval in ECG Lead II (only named, but not constrained).


Type: ValueSet
Id: v3-ActClassCareProvision
Web: ValueSet-v3-ActClassCareProvision.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCareProvision
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCareProvision
Title: ActClassCareProvision
Experimental: false
Description:
An **Act** that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care.

*Discussion:* A **care provision** event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.

In **request** (RQO) mood **care provision** communicates a referral, which is a request:

 *  from one party (linked as a **participant** of type **author** (AUT)),
 *  to another party (linked as a **participant** of type **performer** (PRF),
 *  to take responsibility for a scope specified by the code attribute,
 *  for an entity (linked as a **participant** of type **subject** (SBJ)).

The scope of the care for which responsibility is taken is identified by *code* attribute.

In **event** (EVN) mood **care provision** indicates the effective time interval of a specified scope of responsibility by a **performer** (PRF) or set of **performers** (PRF) for a **subject** (SBJ).

*Examples:*

1.  Referral from GP to a specialist.
2.  Assignment of a patient or group of patients to the case list of a health professional.
3.  Assignment of inpatients to the care of particular nurses for a working shift.


Type: ValueSet
Id: v3-ActClassCategory
Web: ValueSet-v3-ActClassCategory.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCategory
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCategory
Title: ActClassCategory
Experimental: false
Description:
A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan.

The distinction from Topic relates to value sets. For Category there is a bounded list of things like "Examination", "Diagnosis" or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter.

A CATEGORY MAY CONTAIN ENTRIES.


Type: ValueSet
Id: v3-ActClassClinicalDocument
Web: ValueSet-v3-ActClassClinicalDocument.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassClinicalDocument
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassClinicalDocument
Title: ActClassClinicalDocument
Experimental: false
Description:
A clinical document is a documentation of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable."


Type: ValueSet
Id: v3-ActClassClinicalTrial
Web: ValueSet-v3-ActClassClinicalTrial.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassClinicalTrial
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassClinicalTrial
Title: ActClassClinicalTrial
Experimental: false
Description:
The set of actions that define an experiment to assess the effectiveness and/or safety of a biopharmaceutical product (food, drug, device, etc.). In definition mood, this set of actions is often embodied in a clinical trial protocol; in event mood, this designates the aggregate act of applying the actions to one or more subjects.


Type: ValueSet
Id: v3-ActClassClinicalTrialTimepointEvent
Web: ValueSet-v3-ActClassClinicalTrialTimepointEvent.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassClinicalTrialTimepointEvent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassClinicalTrialTimepointEvent
Title: ActClassClinicalTrialTimepointEvent
Experimental: false
Description:
An identified point during a clinical trial at which one or more actions are scheduled to be performed (definition mood), or are actually performed (event mood). The actions may or may not involve an encounter between the subject and a healthcare professional.


Type: ValueSet
Id: v3-ActClassCluster
Web: ValueSet-v3-ActClassCluster.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCluster
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCluster
Title: ActClassCluster
Experimental: false
Description:
A group of entries within a composition, topic or category that have a logical association with one another.

The representation of a single observation or action might itself be multi-part. The data might need to be represented as a nested set of values, as a table, list, or as a time series. The Cluster class permits such aggregation within an entry for such compound data.

Examples include "Haematology investigations" which might include two or more distinct batteries.

A cluster may contain batteries and/or individual entries


Type: ValueSet
Id: v3-ActClassComposition
Web: ValueSet-v3-ActClassComposition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassComposition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassComposition
Title: ActClassComposition
Experimental: false
Description:
A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.

A composition represents part of a patient record originating from a single interaction between an authenticator and the record.

Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application.

A composition contains organizers and entries.


Type: ValueSet
Id: v3-ActClassCondition
Web: ValueSet-v3-ActClassCondition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCondition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCondition
Title: ActClassCondition
Experimental: false
Description:
An observable finding or state that persists over time and tends to require intervention or management, and, therefore, distinguished from an Observation made at a point in time; may exist before an Observation of the Condition is made or after interventions to manage the Condition are undertaken. Examples: equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, chronic illness


Type: ValueSet
Id: v3-ActClassConsent
Web: ValueSet-v3-ActClassConsent.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassConsent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassConsent
Title: ActClassConsent
Experimental: false
Description:
The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.

The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.

The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.

Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed.


Type: ValueSet
Id: v3-ActClassContainer
Web: ValueSet-v3-ActClassContainer.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassContainer
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassContainer
Title: ActClassContainer
Experimental: false
Description:
Used to group a set of acts sharing a common context. Container structures can nest within other context structures - such as where a document is contained within a folder, or a folder is contained within an EHR extract.

**Open issue:**  There is a clear conflict between this act and the use of the more general "component" ActRelationship. The question that must be resolved is what should be the class code of the parent (or containing) Act.


Type: ValueSet
Id: v3-ActClassContainerRegistration
Web: ValueSet-v3-ActClassContainerRegistration.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassContainerRegistration
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassContainerRegistration
Title: ActClassContainerRegistration
Experimental: false
Description:
An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt


Type: ValueSet
Id: v3-ActClassContract
Web: ValueSet-v3-ActClassContract.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassContract
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassContract
Title: ActClassContract
Experimental: false
Description:
An agreement of obligation between two or more parties that is subject to contractual law and enforcement.


Type: ValueSet
Id: v3-ActClassControlAct
Web: ValueSet-v3-ActClassControlAct.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassControlAct
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassControlAct
Title: ActClassControlAct
Experimental: false
Description:
An act representing a system action such as the change of state of another act or the initiation of a query. All control acts represent trigger events in the HL7 context. ControlActs may occur in different moods.


Type: ValueSet
Id: v3-ActClassCorrelatedObservationSequences
Web: ValueSet-v3-ActClassCorrelatedObservationSequences.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCorrelatedObservationSequences
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCorrelatedObservationSequences
Title: ActClassCorrelatedObservationSequences
Experimental: false
Description:
Container for Observation Sequences (Observations whose values are contained in LIST<>'s) having values correlated with each other. Each contained Observation Sequence LIST<> must be the same length. Values in the LIST<>'s are correlated based on index. E.g. the values in position 2 in all the LIST<>'s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST<> of values, and each row in the table is a correlation between the columns. For example, a 12-lead ECG would contain 13 sequences: one sequence for time, and a sequence for each of the 12 leads.


Type: ValueSet
Id: v3-ActClassCoverage
Web: ValueSet-v3-ActClassCoverage.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassCoverage
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassCoverage
Title: ActClassCoverage
Experimental: false
Description:
When used in the EVN mood, this concept means with respect to a covered party:

1.  A health care insurance policy or plan that is contractually binding between two or more parties; or
2.  A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program.

 *  When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party.
 *  The concept's meaning is fully specified by the choice of ActCoverageTypeCode (abstract) ActProgramCode or ActInsurancePolicyCode.


Type: ValueSet
Id: v3-ActClassDetectedIssue
Web: ValueSet-v3-ActClassDetectedIssue.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassDetectedIssue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassDetectedIssue
Title: ActClassDetectedIssue
Experimental: false
Description:
An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.

*Examples:* Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.

*Discussion:* This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.

*Constraints:* the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id).


Type: ValueSet
Id: v3-ActClassDisciplinaryAction
Web: ValueSet-v3-ActClassDisciplinaryAction.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassDisciplinaryAction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassDisciplinaryAction
Title: ActClassDisciplinaryAction
Experimental: false
Description:
An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable.

Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.*Examples:*


Type: ValueSet
Id: v3-ActClassDocumentBody
Web: ValueSet-v3-ActClassDocumentBody.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassDocumentBody
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassDocumentBody
Title: ActClassDocumentBody
Experimental: false
Description:
A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete <head> and <body> elements.


Type: ValueSet
Id: v3-ActClassDocumentSection
Web: ValueSet-v3-ActClassDocumentSection.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassDocumentSection
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassDocumentSection
Title: ActClassDocumentSection
Experimental: false
Description:
A context that subdivides the body of a document. Document sections are typically used for human navigation, to give a reader a clue as to the expected content. Document sections are used to organize and provide consistency to the contents of a document body. Document sections can contain document sections and can contain entries.


Type: ValueSet
Id: v3-ActClassElectronicHealthRecord
Web: ValueSet-v3-ActClassElectronicHealthRecord.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassElectronicHealthRecord
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassElectronicHealthRecord
Title: ActClassElectronicHealthRecord
Experimental: false
Description:
A context that comprises all compositions. The EHR is an extract that includes the entire chart.

**NOTE:** In an exchange scenario, an EHR is a specialization of an extract.


Type: ValueSet
Id: v3-ActClassEncounter
Web: ValueSet-v3-ActClassEncounter.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassEncounter
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassEncounter
Title: ActClassEncounter
Experimental: false
Description:
An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.


Type: ValueSet
Id: v3-ActClassExposure
Web: ValueSet-v3-ActClassExposure.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassExposure
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassExposure
Title: ActClassExposure
Experimental: false
Description:
The action of coming into sufficient physical proximity to allow physical or chemical interaction. Examples include: exposure to radiation, inhalation of peanut aerosol or viral particles. This includes intended exposure (e.g. administering a drug product) as well as accidental or environmental exposure. Actual vs. potential exposure can be differentiated using Act.uncertaintyCode.

The agent to which the subject was exposed is conveyed as a *Direct* participation or specialization there-of.

*Constraints:* The following Participations should be used with the following Roles and Entities to distinguish the specific entities:

 *  The ***exposed entity*** is the entity of interest that is the recipient of the exposure and potentially affected. This is conveyed through the subject (SBJ) Participation.
 *  An entity that has carried the agent transmitted in the exposure is the "***exposure source***" (EXSRC). For example:
    
     *  a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (SBJ) transmitting the disease agent; or
     *  a place or other environment (EXSRC) and a person or animal (SBJ) who is exposed in the presence of this environment.
 *  When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (SBJ), also known as "***exposure contact***", the "participant" (PART) is used.
 *  The substance to which the subject is exposed that carries the exposure agent or the chemical substance of interest itself, participates as a "consumable" (CSM). There are at least two configurations: (a) the player of the Role that participates as CSM is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or (b) the player of the Role that participates as CSM is a mixture known to contain the chemical, radiological or biological substance of interest.
 *  The device specifically used to administer the substance is associated using the device (DEV) Participation. This may be a device intentionally used (such as applicator device) or it may be a thing that accidentally carried this substance; for instance, an infected needle or knife. The same entity may be related in the act as both EXSRC and DEV.


Type: ValueSet
Id: v3-ActClassExtract
Web: ValueSet-v3-ActClassExtract.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassExtract
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassExtract
Title: ActClassExtract
Experimental: false
Description:
This context represents the part of a patient record conveyed in a single communication. It is drawn from a providing system for the purposes of communication to a requesting process (which might be another repository, a client application or a middleware service such as an electronic guideline engine), and supporting the faithful inclusion of the communicated data in the receiving system.

An extract may be the entirety of the patient record as held by the sender or it may be a part of that record (e.g. changes since a specified date).

An extract contains folders or compositions.

An extract cannot contain another extract.


Type: ValueSet
Id: v3-ActClassFinancialAdjudication
Web: ValueSet-v3-ActClassFinancialAdjudication.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassFinancialAdjudication
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassFinancialAdjudication
Title: ActClassFinancialAdjudication
Experimental: false
Description:
A transformation process where a requested invoice is transformed into an agreed invoice. Represents the adjudication processing of an invoice (claim). Adjudication results can be adjudicated as submitted, with adjustments or refused.

Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim


Type: ValueSet
Id: v3-ActClassFinancialTransaction
Web: ValueSet-v3-ActClassFinancialTransaction.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassFinancialTransaction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassFinancialTransaction
Title: ActClassFinancialTransaction
Experimental: false
Description:
A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms.

In the "intent" mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts.

In the "event" mood, communicates the posting of a transaction to an account.


Type: ValueSet
Id: v3-ActClassIncident
Web: ValueSet-v3-ActClassIncident.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassIncident
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassIncident
Title: ActClassIncident
Experimental: false
Description:
An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident.


Type: ValueSet
Id: v3-ActClassInform
Web: ValueSet-v3-ActClassInform.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassInform
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassInform
Title: ActClassInform
Experimental: false
Description:
The act of transmitting information and understanding about a topic to a subject where the participation association must be SBJ.

**Discussion:** This act may be used to request that a patient or provider be informed about an Act, or to indicate that a person was informed about a particular act.


Type: ValueSet
Id: v3-ActClassInformation
Web: ValueSet-v3-ActClassInformation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassInformation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassInformation
Title: ActClassInformation
Experimental: false
Description:
Sender sends payload to addressee as information. Addressee does not have responsibilities beyond serving addressee's own interest (i.e., read and memorize if you see fit). This is equivalent to an FYI on a memo.


Type: ValueSet
Id: v3-ActClassInvestigation
Web: ValueSet-v3-ActClassInvestigation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassInvestigation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassInvestigation
Title: ActClassInvestigation
Experimental: false
Description:
An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.


Type: ValueSet
Id: v3-ActClassJurisdictionalPolicy
Web: ValueSet-v3-ActClassJurisdictionalPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassJurisdictionalPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassJurisdictionalPolicy
Title: ActClassJurisdictionalPolicy
Experimental: false
Description:
**Description:**A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on:

 *  The activity of another party
 *  The behavior of another party
 *  The manner in which an act is executed

**Examples:**A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries.


Type: ValueSet
Id: v3-ActClassMonitoringProgram
Web: ValueSet-v3-ActClassMonitoringProgram.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassMonitoringProgram
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassMonitoringProgram
Title: ActClassMonitoringProgram
Experimental: false
Description:
An officially or unofficially instituted program to track acts of a particular type or categorization.


Type: ValueSet
Id: v3-ActClassObservation
Web: ValueSet-v3-ActClassObservation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassObservation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassObservation
Title: ActClassObservation
Experimental: false
Description:
**Description:**An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The **code** attribute of Observation and the **value** attribute of Observation must be considered in combination to determine the semantics of the observation.

**Discussion:**

Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.

As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects.

The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.

An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.

Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC.

Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.

**Examples:**

 *  Recording the results of a Family History Assessment
 *  Laboratory test and associated result
 *  Physical exam test and associated result
 *  Device temperature
 *  Soil lead level


Type: ValueSet
Id: v3-ActClassObservationSeries
Web: ValueSet-v3-ActClassObservationSeries.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassObservationSeries
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassObservationSeries
Title: ActClassObservationSeries
Experimental: false
Description:
Container for Correlated Observation Sequences sharing a common frame of reference. All Observations of the same cd must be comparable and relative to the common frame of reference. For example, a 3-channel ECG device records a 12-lead ECG in 4 steps (3 leads at a time). Each of the separate 3-channel recordings would be in their own "OBSCOR". And, all 4 OBSCOR would be contained in one OBSSER because all the times are relative to the same origin (beginning of the recording) and all the ECG signals were from a fixed set of electrodes.


Type: ValueSet
Id: v3-ActClassOrganizationalPolicy
Web: ValueSet-v3-ActClassOrganizationalPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassOrganizationalPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassOrganizationalPolicy
Title: ActClassOrganizationalPolicy
Experimental: false
Description:
**Description:**A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on:

 *  The activity of another party
 *  The behavior of another party
 *  The manner in which an act is executed

**Examples:**A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options.


Type: ValueSet
Id: v3-ActClassOutbreak
Web: ValueSet-v3-ActClassOutbreak.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassOutbreak
Version: 3.0.0
Status: retired
Date: 2014-03-26
Name: ActClassOutbreak
Title: ActClassOutbreak
Experimental: false
Description:
An outbreak represents a series of public health cases. The date on which an outbreak starts is the earliest date of onset among the cases assigned to the outbreak, and its ending date is the last date of onset among the cases assigned to the outbreak.


Type: ValueSet
Id: v3-ActClassOverlayRoi
Web: ValueSet-v3-ActClassOverlayRoi.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassOverlayRoi
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassOverlayRoi
Title: ActClassOverlayRoi
Experimental: false
Description:
A Region of Interest (ROI) specified for an image using an overlay shape. Typically used to make reference to specific regions in images, e.g., to specify the location of a radiologic finding in an image or to specify the site of a physical finding by "circling" a region in a schematic picture of a human body. The units of the coordinate values are in pixels. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present.


Type: ValueSet
Id: v3-ActClassPolicy
Web: ValueSet-v3-ActClassPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassPolicy
Title: ActClassPolicy
Experimental: false
Description:
**Description:**A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on:

 *  The activity of another party
 *  The behavior of another party
 *  The manner in which an act is executed


Type: ValueSet
Id: v3-ActClassPosition
Web: ValueSet-v3-ActClassPosition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPosition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassPosition
Title: ActClassPosition
Experimental: false
Description:
An observation denoting the physical location of a person or thing based on a reference coordinate system.


Type: ValueSet
Id: v3-ActClassPositionAccuracy
Web: ValueSet-v3-ActClassPositionAccuracy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPositionAccuracy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassPositionAccuracy
Title: ActClassPositionAccuracy
Experimental: false
Description:
**Description:**An observation representing the degree to which the assignment of the spatial coordinates, based on a matching algorithm by a geocoding engine against a reference spatial database, matches true or accepted values.


Type: ValueSet
Id: v3-ActClassPositionCoordinate
Web: ValueSet-v3-ActClassPositionCoordinate.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPositionCoordinate
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassPositionCoordinate
Title: ActClassPositionCoordinate
Experimental: false
Description:
**Description:**An observation representing one of a set of numerical values used to determine the position of a place. The name of the coordinate value is determined by the reference coordinate system.


Type: ValueSet
Id: v3-ActClassProcedure
Web: ValueSet-v3-ActClassProcedure.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassProcedure
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassProcedure
Title: ActClassProcedure
Experimental: false
Description:
An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.

*Examples:* : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.


Type: ValueSet
Id: v3-ActClassProcessStep
Web: ValueSet-v3-ActClassProcessStep.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassProcessStep
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassProcessStep
Title: ActClassProcessStep
Experimental: false
Description:
**ActCodeProcessStep** \- Property applies to value sets that contain classCode values in structural vocabularies. It identifies by name the Concept Domain(s) that represent(s) the concepts that are sub-types of the concept collection established by the value sets of class codes.


Type: ValueSet
Id: v3-ActClassPublicHealthCase
Web: ValueSet-v3-ActClassPublicHealthCase.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPublicHealthCase
Version: 3.0.0
Status: retired
Date: 2014-03-26
Name: ActClassPublicHealthCase
Title: ActClassPublicHealthCase
Experimental: false
Description:
A public health case is an Observation representing a condition or event that has a specific significance for public health. Typically it involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health. An outbreak involving multiple individuals may be considered as a type of public health case. A public health case definition (Act.moodCode = "definition") includes the description of the clinical, laboratory, and epidemiologic indicators associated with a disease or condition of interest to public health. There are case definitions for conditions that are reportable, as well as for those that are not. There are also case definitions for outbreaks. A public health case definition is a construct used by public health for the purpose of counting cases, and should not be used as clinical indications for treatment. Examples include AIDS, toxic-shock syndrome, and salmonellosis and their associated indicators that are used to define a case.


Type: ValueSet
Id: v3-ActClassPublicHealthCase2
Web: ValueSet-v3-ActClassPublicHealthCase2.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassPublicHealthCase2
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassPublicHealthCase2
Title: ActClassPublicHealthCase2
Experimental: false
Description:
A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern. The decision to track is related to but somewhat independent of the underlying event or observation.


Type: ValueSet
Id: v3-ActClassROI
Web: ValueSet-v3-ActClassROI.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassROI
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassROI
Title: ActClassROI
Experimental: false
Description:
Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present.


Type: ValueSet
Id: v3-ActClassRegistration
Web: ValueSet-v3-ActClassRegistration.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassRegistration
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassRegistration
Title: ActClassRegistration
Experimental: false
Description:
Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment.

The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system.*Usage notes:* 


Type: ValueSet
Id: v3-ActClassReview
Web: ValueSet-v3-ActClassReview.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassReview
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassReview
Title: ActClassReview
Experimental: false
Description:
The act of examining and evaluating the subject, usually another act. For example, "This prescription needs to be reviewed in 2 months."


Type: ValueSet
Id: v3-ActClassRoot
Web: ValueSet-v3-ActClassRoot.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassRoot
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassRoot
Title: ActClassRoot
Experimental: false
Description:
A record of something that is being done, has been done, can be done, or is intended or requested to be done.

*Examples:*The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8) editing and maintaining documents, and many others.

*Discussion and Rationale:* Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action.

Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear.

One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who "owns" the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances.

In this sense, an Act-instance represents a "statement" according to Rector and Nowlan (1991) \[Foundations for an electronic medical record. Methods Inf Med. 30.\] Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but "a faithful record of what clinicians have heard, seen, thought, and done." Rector and Nowlan go on saying that "the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view." Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements.

Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as "speech-acts" in linguistics and philosophy. The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) \[How to do things with words. Oxford University Press\].

An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle. This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category "sequel").

Act as statements or speech-acts are the only representation of real world facts or processes in the HL7 RIM. The truth about the real world is constructed through a combination (and arbitration) of such attributed statements only, and there is no class in the RIM whose objects represent "objective state of affairs" or "real processes" independent from attributed statements. As such, there is no distinction between an activity and its documentation. Every Act includes both to varying degrees. For example, a factual statement made about recent (but past) activities, authored (and signed) by the performer of such activities, is commonly known as a procedure report or original documentation (e.g., surgical procedure report, clinic note etc.). Conversely, a status update on an activity that is presently in progress, authored by the performer (or a close observer) is considered to capture that activity (and is later superceded by a full procedure report). However, both status update and procedure report are acts of the same kind, only distinguished by mood and state (see statusCode) and completeness of the information.


Type: ValueSet
Id: v3-ActClassScopeOfPracticePolicy
Web: ValueSet-v3-ActClassScopeOfPracticePolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassScopeOfPracticePolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassScopeOfPracticePolicy
Title: ActClassScopeOfPracticePolicy
Experimental: false
Description:
**Description:**An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on:

 *  The activity of another party
 *  The behavior of another party
 *  The manner in which an act is executed

**Examples:**An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide.


Type: ValueSet
Id: v3-ActClassSpecimenObservation
Web: ValueSet-v3-ActClassSpecimenObservation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassSpecimenObservation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassSpecimenObservation
Title: ActClassSpecimenObservation
Experimental: false
Description:
An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation


Type: ValueSet
Id: v3-ActClassStandardOfPracticePolicy
Web: ValueSet-v3-ActClassStandardOfPracticePolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassStandardOfPracticePolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassStandardOfPracticePolicy
Title: ActClassStandardOfPracticePolicy
Experimental: false
Description:
**Description:**A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on:

 *  The activity of another party
 *  The behavior of another party
 *  The manner in which an act is executed

**Examples:**A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems.


Type: ValueSet
Id: v3-ActClassStateTransitionControl
Web: ValueSet-v3-ActClassStateTransitionControl.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassStateTransitionControl
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassStateTransitionControl
Title: ActClassStateTransitionControl
Experimental: false
Description:
Sender transmits a status change pertaining to the focal act of the payload. This status of the focal act is the final state of the state transition. This can be either a request or a command, according to the mood of the control act.


Type: ValueSet
Id: v3-ActClassStorage
Web: ValueSet-v3-ActClassStorage.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassStorage
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassStorage
Title: ActClassStorage
Experimental: false
Description:
The act of putting something away for safe keeping. The "something" may be physical object such as a specimen, or information, such as observations regarding a specimen.


Type: ValueSet
Id: v3-ActClassSubjectPhysicalPosition
Web: ValueSet-v3-ActClassSubjectPhysicalPosition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassSubjectPhysicalPosition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassSubjectPhysicalPosition
Title: ActClassSubjectPhysicalPosition
Experimental: false
Description:
The spatial relationship of a subject whether human, other animal, or plant, to a frame of reference such as gravity or a collection device.


Type: ValueSet
Id: v3-ActClassSubstanceAdministration
Web: ValueSet-v3-ActClassSubstanceAdministration.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassSubstanceAdministration
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassSubstanceAdministration
Title: ActClassSubstanceAdministration
Experimental: false
Description:
The act of introducing or otherwise applying a substance to the subject.

*Discussion:* The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine. This class also includes the application of chemical treatments to an area.

*Examples:* Chemotherapy protocol; Drug prescription; Vaccination record


Type: ValueSet
Id: v3-ActClassSubstitution
Web: ValueSet-v3-ActClassSubstitution.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassSubstitution
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassSubstitution
Title: ActClassSubstitution
Experimental: false
Description:
Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code.

Rationale: Used to specify "allowed" substitution when creating orders, "actual" susbstitution when sending events, as well as the reason for the substitution and who was responsible for it.


Type: ValueSet
Id: v3-ActClassSupply
Web: ValueSet-v3-ActClassSupply.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassSupply
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassSupply
Title: ActClassSupply
Experimental: false
Description:
Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.


Type: ValueSet
Id: v3-ActClassTopic
Web: ValueSet-v3-ActClassTopic.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassTopic
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassTopic
Title: ActClassTopic
Experimental: false
Description:
A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services.

A topic may contain categories and entries.


Type: ValueSet
Id: v3-ActClassTransfer
Web: ValueSet-v3-ActClassTransfer.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassTransfer
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassTransfer
Title: ActClassTransfer
Experimental: false
Description:
**Definition:** The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD.


Type: ValueSet
Id: v3-ActClassTransmissionExposure
Web: ValueSet-v3-ActClassTransmissionExposure.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassTransmissionExposure
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassTransmissionExposure
Title: ActClassTransmissionExposure
Experimental: false
Description:
**Description:** 

A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity. The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion.

**Constraints:** The Transmission Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPTRGT (exposure target) participation must never be associated with the Transmission Exposure either directly or via context conduction.


Type: ValueSet
Id: v3-ActClassTransportation
Web: ValueSet-v3-ActClassTransportation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassTransportation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassTransportation
Title: ActClassTransportation
Experimental: false
Description:
Transportation is the moving of a payload (people or material) from a location of origin to a destination location. Thus, any transport service has the three target instances of type payload, origin, and destination, besides the targets that are generally used for any service (i.e., performer, device, etc.)


Type: ValueSet
Id: v3-ActClassVerification
Web: ValueSet-v3-ActClassVerification.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassVerification
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassVerification
Title: ActClassVerification
Experimental: false
Description:
An act which describes the process whereby a 'verifying party' validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details.


Type: ValueSet
Id: v3-ActClassWorkingList
Web: ValueSet-v3-ActClassWorkingList.html
Url: http://terminology.hl7.org/ValueSet/v3-ActClassWorkingList
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActClassWorkingList
Title: ActClassWorkingList
Experimental: false
Description:
Working list collects a dynamic list of individual instances of Act via ActRelationship which reflects the need of an individual worker, team of workers, or an organization to manage lists of acts for many different clinical and administrative reasons. Examples of working lists include problem lists, goal lists, allergy lists, and to-do lists.


Type: ValueSet
Id: v3-ActCode
Web: ValueSet-v3-ActCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCode
Version: 3.0.0
Status: active
Date: 2018-08-12
Name: ActCode
Title: v3 Code System ActCode
Experimental: false
Description:
A code specifying the particular kind of Act that the Act-instance represents within its class.  Constraints:
The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems.  The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted.


Type: ValueSet
Id: v3-ActConsentDirective
Web: ValueSet-v3-ActConsentDirective.html
Url: http://terminology.hl7.org/ValueSet/v3-ActConsentDirective
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActConsentDirective
Title: ActConsentDirective
Experimental: false
Description:
ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms.


Type: ValueSet
Id: v3-ActConsentDirectiveType
Web: ValueSet-v3-ActConsentDirectiveType.html
Url: http://terminology.hl7.org/ValueSet/v3-ActConsentDirectiveType
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActConsentDirectiveType
Title: ActConsentDirectiveType
Experimental: false
Description:
ActConsentDirective and ActConsentType codes are used to specify the type of Consent Directive or Consent Type to which, for example, a Consent Act conforms, to which a Security Observation (Security Label) refers to, or to which a Privacy or Security Act refers.

>

*Steward:* Security WG


Type: ValueSet
Id: v3-ActConsentInformationAccessOverrideReason
Web: ValueSet-v3-ActConsentInformationAccessOverrideReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActConsentInformationAccessOverrideReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActConsentInformationAccessOverrideReason
Title: ActConsentInformationAccessOverrideReason
Experimental: false
Description:
**Definition:** Use to convey the reason that a provider may or has accessed personal healthcare information. Typically, this involves overriding the subject's consent directives.


Type: ValueSet
Id: v3-ActConsentType
Web: ValueSet-v3-ActConsentType.html
Url: http://terminology.hl7.org/ValueSet/v3-ActConsentType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActConsentType
Title: ActConsentType
Experimental: false
Description:
**Definition:** The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research.


Type: ValueSet
Id: v3-ActControlVariable
Web: ValueSet-v3-ActControlVariable.html
Url: http://terminology.hl7.org/ValueSet/v3-ActControlVariable
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActControlVariable
Title: ActControlVariable
Experimental: false
Description:
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 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).


Type: ValueSet
Id: v3-ActCoverageAssessmentObservationValue
Web: ValueSet-v3-ActCoverageAssessmentObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCoverageAssessmentObservationValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCoverageAssessmentObservationValue
Title: ActCoverageAssessmentObservationValue
Experimental: false
Description:
Codes specify the category of observation, evidence, or document used to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program. The type of evidence is coded as observation values.


Type: ValueSet
Id: v3-ActCoverageAuthorizationConfirmationCode
Web: ValueSet-v3-ActCoverageAuthorizationConfirmationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCoverageAuthorizationConfirmationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCoverageAuthorizationConfirmationCode
Title: ActCoverageAuthorizationConfirmationCode
Experimental: false
Description:
Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside.


Type: ValueSet
Id: v3-ActCoverageQuantityLimitCode
Web: ValueSet-v3-ActCoverageQuantityLimitCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCoverageQuantityLimitCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCoverageQuantityLimitCode
Title: ActCoverageQuantityLimitCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActCoverageReason
Web: ValueSet-v3-ActCoverageReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCoverageReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCoverageReason
Title: ActCoverageReason
Experimental: false
Description:
**Description:**Codes used to specify reasons or criteria relating to coverage provided under a policy or program. May be used to convey reasons pertaining to coverage contractual provisions, including criteria for eligibility, coverage limitations, coverage maximums, or financial participation required of covered parties.


Type: ValueSet
Id: v3-ActCoverageTypeCode
Web: ValueSet-v3-ActCoverageTypeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCoverageTypeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCoverageTypeCode
Title: ActCoverageTypeCode
Experimental: false
Description:
**Definition:** Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.


Type: ValueSet
Id: v3-ActCredentialedCareCode
Web: ValueSet-v3-ActCredentialedCareCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCredentialedCareCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCredentialedCareCode
Title: ActCredentialedCareCode
Experimental: false
Description:
**Description:**The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by a credentialing agency, i.e. government or non-government agency. Failure in executing this Act may result in loss of credential to the person or organization who participates as performer of the Act. Excludes employment agreements.

**Example:**Hospital license; physician license; clinic accreditation.


Type: ValueSet
Id: v3-ActCredentialedCareProvisionPersonCode
Web: ValueSet-v3-ActCredentialedCareProvisionPersonCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActCredentialedCareProvisionPersonCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActCredentialedCareProvisionPersonCode
Title: ActCredentialedCareProvisionPersonCode
Experimental: false
Description:
**Description:**The type and scope of legal and/or professional responsibility taken-on by the performer of the Act for a specific subject of care as described by an agency for credentialing individuals.


Type: ValueSet
Id: v3-ActEmergencyEncounterCode
Web: ValueSet-v3-ActEmergencyEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActEmergencyEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActEmergencyEncounterCode
Title: ActEmergencyEncounterCode
Experimental: false
Description:
**Definition:**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.)


Type: ValueSet
Id: v3-ActEncounterAccommodationCode
Web: ValueSet-v3-ActEncounterAccommodationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActEncounterAccommodationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActEncounterAccommodationCode
Title: ActEncounterAccommodationCode
Experimental: false
Description:
Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type.


Type: ValueSet
Id: v3-ActExposureCode
Web: ValueSet-v3-ActExposureCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActExposureCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActExposureCode
Title: ActExposureCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActFieldEncounterCode
Web: ValueSet-v3-ActFieldEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActFieldEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActFieldEncounterCode
Title: ActFieldEncounterCode
Experimental: false
Description:
**Definition:**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.


Type: ValueSet
Id: v3-ActFinancialStatusObservationValue
Web: ValueSet-v3-ActFinancialStatusObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ActFinancialStatusObservationValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActFinancialStatusObservationValue
Title: ActFinancialStatusObservationValue
Experimental: false
Description:
Code specifying financial indicators used to assess or establish eligibility for coverage under a policy or program; e.g., pay stub; tax or income document; asset document; living expenses.


Type: ValueSet
Id: v3-ActHealthInformationManagementReason
Web: ValueSet-v3-ActHealthInformationManagementReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActHealthInformationManagementReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActHealthInformationManagementReason
Title: ActHealthInformationManagementReason
Experimental: false
Description:
The rationale or purpose for an act relating to health information management, such as archiving information for the purpose of complying with an organization policy or jurisdictional law relating to data retention.


Type: ValueSet
Id: v3-ActHealthInsuranceTypeCode
Web: ValueSet-v3-ActHealthInsuranceTypeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActHealthInsuranceTypeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActHealthInsuranceTypeCode
Title: ActHealthInsuranceTypeCode
Experimental: false
Description:
**Definition:** Set of codes indicating the type of health insurance policy that covers health services provided to covered parties. A health insurance policy is a written contract for insurance between the insurance company and the policyholder, and contains pertinent facts about the policy owner (the policy holder), the health insurance coverage, the insured subscribers and dependents, and the insurer. Health insurance is typically administered in accordance with a plan, which specifies (1) the type of health services and health conditions that will be covered under what circumstances (e.g., exclusion of a pre-existing condition, service must be deemed medically necessary; service must not be experimental; service must provided in accordance with a protocol; drug must be on a formulary; service must be prior authorized; or be a referral from a primary care provider); (2) the type and affiliation of providers (e.g., only allopathic physicians, only in network, only providers employed by an HMO); (3) financial participations required of covered parties (e.g., co-pays, coinsurance, deductibles, out-of-pocket); and (4) the manner in which services will be paid (e.g., under indemnity or fee-for-service health plans, the covered party typically pays out-of-pocket and then file a claim for reimbursement, while health plans that have contractual relationships with providers, i.e., network providers, typically do not allow the providers to bill the covered party for the cost of the service until after filing a claim with the payer and receiving reimbursement).


Type: ValueSet
Id: v3-ActIneligibilityReason
Web: ValueSet-v3-ActIneligibilityReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActIneligibilityReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActIneligibilityReason
Title: ActIneligibilityReason
Experimental: false
Description:
Identifies the reason or rational for why a person is not eligibile for benefits under an insurance policy.

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


Type: ValueSet
Id: v3-ActInformationAccessCode
Web: ValueSet-v3-ActInformationAccessCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInformationAccessCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInformationAccessCode
Title: ActInformationAccessCode
Experimental: false
Description:
The type of personal health information to which the subject of the information, or the delegate of the subject, consents or dissents to authorize access.


Type: ValueSet
Id: v3-ActInformationAccessContextCode
Web: ValueSet-v3-ActInformationAccessContextCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInformationAccessContextCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ActInformationAccessContextCode
Title: ActInformationAccessContextCode
Experimental: false
Description:
Conveyance of the type of 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.

*Steward:* Security WG


Type: ValueSet
Id: v3-ActInformationCategoryCode
Web: ValueSet-v3-ActInformationCategoryCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInformationCategoryCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInformationCategoryCode
Title: ActInformationCategoryCode
Experimental: false
Description:
**Definition:**Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions.


Type: ValueSet
Id: v3-ActInformationSensitivityPolicy
Web: ValueSet-v3-ActInformationSensitivityPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInformationSensitivityPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInformationSensitivityPolicy
Title: ActInformationSensitivityPolicy
Experimental: false
Description:
ActSensitivity codes are used to bind information to an Act.confidentialityCode according to local sensitivity policy so that those confidentiality codes can then govern its handling across enterprises. Internally to a policy domain, however, local policies guide the access control system on how end users in that policy domain are able to use information tagged with these sensitivity values.


Type: ValueSet
Id: v3-ActInpatientEncounterCode
Web: ValueSet-v3-ActInpatientEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInpatientEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInpatientEncounterCode
Title: ActInpatientEncounterCode
Experimental: false
Description:
An inpatient encounter is an encounter in which the patient is admitted to a hospital or equivalent facility.


Type: ValueSet
Id: v3-ActInsurancePolicyCode
Web: ValueSet-v3-ActInsurancePolicyCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInsurancePolicyCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInsurancePolicyCode
Title: ActInsurancePolicyCode
Experimental: false
Description:
Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs.


Type: ValueSet
Id: v3-ActInsuranceTypeCode
Web: ValueSet-v3-ActInsuranceTypeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInsuranceTypeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInsuranceTypeCode
Title: ActInsuranceTypeCode
Experimental: false
Description:
**Definition:** Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an individual or an organization enters into a contract with an underwriter which stipulates that, in exchange for payment of a sum of money (a premium), one or more covered parties (insureds) is guaranteed compensation for losses resulting from certain perils under specified conditions. The underwriter analyzes the risk of loss, makes a decision as to whether the risk is insurable, and prices the premium accordingly. A policy provides benefits that indemnify or cover the cost of a loss incurred by a covered party, and may include coverage for services required to remediate a loss. An insurance policy contains pertinent facts about the policy holder, the insurance coverage, the covered parties, and the insurer. A policy may include exemptions and provisions specifying the extent to which the indemnification clause cannot be enforced for intentional tortious conduct of a covered party, e.g., whether the covered parties are jointly or severably insured.

*Discussion:* In contrast to programs, an insurance policy has one or more policy holders, who own the policy. The policy holder may be the covered party, a relative of the covered party, a partnership, or a corporation, e.g., an employer. A subscriber of a self-insured health insurance policy is a policy holder. A subscriber of an employer sponsored health insurance policy is holds a certificate of coverage, but is not a policy holder; the policy holder is the employer. See CoveredRoleType.


Type: ValueSet
Id: v3-ActInvoiceAdjudicationPaymentCode
Web: ValueSet-v3-ActInvoiceAdjudicationPaymentCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceAdjudicationPaymentCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceAdjudicationPaymentCode
Title: ActInvoiceAdjudicationPaymentCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActInvoiceAdjudicationPaymentSummaryCode
Web: ValueSet-v3-ActInvoiceAdjudicationPaymentSummaryCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceAdjudicationPaymentSummaryCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceAdjudicationPaymentSummaryCode
Title: ActInvoiceAdjudicationPaymentSummaryCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActInvoiceDetailCode
Web: ValueSet-v3-ActInvoiceDetailCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailCode
Title: ActInvoiceDetailCode
Experimental: false
Description:
Codes representing a service or product that is being invoiced (billed). The code can represent such concepts as "office visit", "drug X", "wheelchair" and other billable items such as taxes, service charges and discounts.


Type: ValueSet
Id: v3-ActInvoiceDetailDrugProductCode
Web: ValueSet-v3-ActInvoiceDetailDrugProductCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailDrugProductCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailDrugProductCode
Title: ActInvoiceDetailDrugProductCode
Experimental: false
Description:
An identifying data string for A substance used as a medication or in the preparation of medication.


Type: ValueSet
Id: v3-ActInvoiceDetailGenericAdjudicatorCode
Web: ValueSet-v3-ActInvoiceDetailGenericAdjudicatorCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailGenericAdjudicatorCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailGenericAdjudicatorCode
Title: ActInvoiceDetailGenericAdjudicatorCode
Experimental: false
Description:
The billable item codes to identify adjudicator specified components to the total billing of a claim.


Type: ValueSet
Id: v3-ActInvoiceDetailGenericCode
Web: ValueSet-v3-ActInvoiceDetailGenericCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailGenericCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailGenericCode
Title: ActInvoiceDetailGenericCode
Experimental: false
Description:
The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments.


Type: ValueSet
Id: v3-ActInvoiceDetailGenericModifierCode
Web: ValueSet-v3-ActInvoiceDetailGenericModifierCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailGenericModifierCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailGenericModifierCode
Title: ActInvoiceDetailGenericModifierCode
Experimental: false
Description:
The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee.


Type: ValueSet
Id: v3-ActInvoiceDetailGenericProviderCode
Web: ValueSet-v3-ActInvoiceDetailGenericProviderCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailGenericProviderCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailGenericProviderCode
Title: ActInvoiceDetailGenericProviderCode
Experimental: false
Description:
The billable item codes to identify provider supplied charges or changes to the total billing of a claim.


Type: ValueSet
Id: v3-ActInvoiceDetailTaxCode
Web: ValueSet-v3-ActInvoiceDetailTaxCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceDetailTaxCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceDetailTaxCode
Title: ActInvoiceDetailTaxCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActInvoiceElementCode
Web: ValueSet-v3-ActInvoiceElementCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceElementCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceElementCode
Title: ActInvoiceElementCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActInvoiceElementSummaryCode
Web: ValueSet-v3-ActInvoiceElementSummaryCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceElementSummaryCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceElementSummaryCode
Title: ActInvoiceElementSummaryCode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ActInvoiceGroupCode
Web: ValueSet-v3-ActInvoiceGroupCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceGroupCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceGroupCode
Title: ActInvoiceGroupCode
Experimental: false
Description:
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 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.


Type: ValueSet
Id: v3-ActInvoiceInterGroupCode
Web: ValueSet-v3-ActInvoiceInterGroupCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceInterGroupCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceInterGroupCode
Title: ActInvoiceInterGroupCode
Experimental: false
Description:
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 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.

The domain is only specified for an intermediate invoice element group (non-root or non-top level) for an Invoice.


Type: ValueSet
Id: v3-ActInvoiceRootGroupCode
Web: ValueSet-v3-ActInvoiceRootGroupCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActInvoiceRootGroupCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActInvoiceRootGroupCode
Title: ActInvoiceRootGroupCode
Experimental: false
Description:
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 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 only specified for the root (top level) invoice element group for an Invoice.


Type: ValueSet
Id: v3-ActMood
Web: ValueSet-v3-ActMood.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMood
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMood
Title: ActMood
Experimental: false
Description:
A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc.

*Constraints:* An Act-instance must have one and only one moodCode value.

The moodCode of a single Act-instance never changes. Mood is not state.

To describe the progression of a business activity from defined to planned to executed, etc. one must instantiate different Act-instances in the different moods and link them using ActRelationship of general type "sequel". (See ActRelationship.type.)


Type: ValueSet
Id: v3-ActMoodCompletionTrack
Web: ValueSet-v3-ActMoodCompletionTrack.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodCompletionTrack
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodCompletionTrack
Title: ActMoodCompletionTrack
Experimental: false
Description:
These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.


Type: ValueSet
Id: v3-ActMoodCriterion
Web: ValueSet-v3-ActMoodCriterion.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodCriterion
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodCriterion
Title: ActMoodCriterion
Experimental: false
Description:
A criterion or condition over actual and potential services that must apply for an associated service to be considered. Matches records any ActMoodCompletionTrack moods.


Type: ValueSet
Id: v3-ActMoodDefinition
Web: ValueSet-v3-ActMoodDefinition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodDefinition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodDefinition
Title: ActMoodDefinition
Experimental: false
Description:
A definition of a service (master).

Historical note: in previous RIM versions, the definition mood was captured as a separate class hierarchy, called Master\_service.


Type: ValueSet
Id: v3-ActMoodEventCriterion
Web: ValueSet-v3-ActMoodEventCriterion.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodEventCriterion
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodEventCriterion
Title: ActMoodEventCriterion
Experimental: false
Description:
A criterion or condition over service events that must apply for an associated service to be considered.


Type: ValueSet
Id: v3-ActMoodEventOccurrence
Web: ValueSet-v3-ActMoodEventOccurrence.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodEventOccurrence
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodEventOccurrence
Title: ActMoodEventOccurrence
Experimental: false
Description:
A service that actually happens, may be an ongoing service or a documentation of a past service.

Historical note: in previous RIM versions, the event mood was captured as a separate class hierarchy, called Patient\_service\_event, and later Service\_event.


Type: ValueSet
Id: v3-ActMoodExpectation
Web: ValueSet-v3-ActMoodExpectation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodExpectation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodExpectation
Title: ActMoodExpectation
Experimental: false
Description:
**Definition:**An act that is considered likely to occur in the future. The essential feature of an act expressed in expectation mood is that it is likely to occur. An expectation may be desirable, undesirable or neutral in effect.

**Examples:**Prognosis of a condition, Expected date of discharge from hospital, patient will likely need an emergency decompression of the intracranial pressure by morning.

**Discussion:**INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with expectation, which is a prediction that something will happen in the future. GOL (goal) reflects a hope rather than a prediction. RSK (risk) reflects a potential negative event that may or may not be expected to happen.


Type: ValueSet
Id: v3-ActMoodGoal
Web: ValueSet-v3-ActMoodGoal.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodGoal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodGoal
Title: ActMoodGoal
Experimental: false
Description:
**Definition:**An observation that is considered to be desirable to occur in the future. The essential feature of a goal is that if it occurs it would be considered as a marker of a positive outcome or of progress towards a positive outcome.

**Examples:**Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.

**Discussion:** INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. "I will reduce the dose of drug x to 20mg" is an intent. "I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg" is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.


Type: ValueSet
Id: v3-ActMoodIntent
Web: ValueSet-v3-ActMoodIntent.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodIntent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodIntent
Title: ActMoodIntent
Experimental: false
Description:
An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service\_intent\_or\_order.


Type: ValueSet
Id: v3-ActMoodOption
Web: ValueSet-v3-ActMoodOption.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodOption
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodOption
Title: ActMoodOption
Experimental: false
Description:
An option is an alternative set of property-value bindings. Options specify alternative sets of values, typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together.

Historical note: in HL7 v2.x option existed in the special case for alternative medication routes (RXR segment).


Type: ValueSet
Id: v3-ActMoodPermissionRequest
Web: ValueSet-v3-ActMoodPermissionRequest.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodPermissionRequest
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodPermissionRequest
Title: ActMoodPermissionRequest
Experimental: false
Description:
A request for authorization to perform a kind of service.

This is distinct from RQO which is a request for an actual act. PERMRQ is merely a request for permission to perform an act.*Discussion:*


Type: ValueSet
Id: v3-ActMoodPredicate
Web: ValueSet-v3-ActMoodPredicate.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodPredicate
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodPredicate
Title: ActMoodPredicate
Experimental: false
Description:
Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.


Type: ValueSet
Id: v3-ActMoodPromise
Web: ValueSet-v3-ActMoodPromise.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodPromise
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodPromise
Title: ActMoodPromise
Experimental: false
Description:
An intent to perform a service that has the strength of a commitment, i.e., other parties may rely on the originator of such promise that said originator will see to it that the promised act will be fulfilled. A promise can be either solicited or unsolicited.


Type: ValueSet
Id: v3-ActMoodProposal
Web: ValueSet-v3-ActMoodProposal.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodProposal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodProposal
Title: ActMoodProposal
Experimental: false
Description:
A non-mandated intent to perform an act. Used to record intents that are explicitly not Orders. Professional responsibility for the 'proposal' may or may not be present.


Type: ValueSet
Id: v3-ActMoodRecommendation
Web: ValueSet-v3-ActMoodRecommendation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodRecommendation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodRecommendation
Title: ActMoodRecommendation
Experimental: false
Description:
A non-mandated intent to perform an act where a level of professional responsibility is being accepted by making the proposal.


Type: ValueSet
Id: v3-ActMoodRequest
Web: ValueSet-v3-ActMoodRequest.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodRequest
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodRequest
Title: ActMoodRequest
Experimental: false
Description:
A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer).

*Rationale:* The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request."

Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.

The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.


Type: ValueSet
Id: v3-ActMoodResourceSlot
Web: ValueSet-v3-ActMoodResourceSlot.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodResourceSlot
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodResourceSlot
Title: ActMoodResourceSlot
Experimental: false
Description:
Periods of time on a schedule for a resource. Appointments occupy sets of one or more booked slots. A slot that is open for appointments is considered available and a slot that is held back for administrative purposes is considered blocked. A Resource slot that is "tentatively" booked is referred to as reserved.


Type: ValueSet
Id: v3-ActMoodRisk
Web: ValueSet-v3-ActMoodRisk.html
Url: http://terminology.hl7.org/ValueSet/v3-ActMoodRisk
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActMoodRisk
Title: ActMoodRisk
Experimental: false
Description:
**Definition:**An act that may occur in the future and which is regarded as undesirable. The essential feature of a risk is that if it occurs this would be regarded as a marker of a negative outcome or of deterioration towards a negative outcome. Recording a risk indicates that it is seen as more likely to occur in the subject than in a general member of the population but does not mean it is expected to occur.

**Examples:**Increased risk of DVT, at risk for sub-acute bacterial endocarditis.

**Discussion:**Note: An observation in RSK mood expresses the undesirable act, and not the underlying risk factor. A risk factor that is present (e.g. obesity, smoking, etc) should be expressed in event mood. INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen. GOL (goal) reflects a hope to achieve something. EXPEC (expectation) is the prediction of a positive or negative event. This contrasts with RSK (risk), which is the potential that something negative will occur that may or may not ever happen, and may not be expected to happen.


Type: ValueSet
Id: v3-ActNoImmunizationReason
Web: ValueSet-v3-ActNoImmunizationReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActNoImmunizationReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActNoImmunizationReason
Title: ActNoImmunizationReason
Experimental: false
Description:
A coded description of the reason for why a patient did not receive a scheduled immunization.

(important for public health strategy


Type: ValueSet
Id: v3-ActNonObservationIndicationCode
Web: ValueSet-v3-ActNonObservationIndicationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActNonObservationIndicationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActNonObservationIndicationCode
Title: ActNonObservationIndicationCode
Experimental: false
Description:
**Description:**Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms.


Type: ValueSet
Id: v3-ActObservationVerificationType
Web: ValueSet-v3-ActObservationVerificationType.html
Url: http://terminology.hl7.org/ValueSet/v3-ActObservationVerificationType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActObservationVerificationType
Title: ActObservationVerificationType
Experimental: false
Description:
Identifies the type of verification investigation being undertaken with respect to the subject of the verification activity.

**Examples:**

1.  Verification of eligibility for coverage under a policy or program - aka enrolled/covered by a policy or program
2.  Verification of record - e.g., person has record in an immunization registry
3.  Verification of enumeration - e.g. NPI
4.  Verification of Board Certification - provider specific
5.  Verification of Certification - e.g. JAHCO, NCQA, URAC
6.  Verification of Conformance - e.g. entity use with HIPAA, conformant to the CCHIT EHR system criteria
7.  Verification of Provider Credentials
8.  Verification of no adverse findings - e.g. on National Provider Data Bank, Health Integrity Protection Data Base (HIPDB)


Type: ValueSet
Id: v3-ActPatientTransportationModeCode
Web: ValueSet-v3-ActPatientTransportationModeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPatientTransportationModeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPatientTransportationModeCode
Title: ActPatientTransportationModeCode
Experimental: false
Description:
Definition: Characterizes how a patient was or will be transported to the site of a patient encounter.

*Examples:* Via ambulance, via public transit, on foot.


Type: ValueSet
Id: v3-ActPaymentCode
Web: ValueSet-v3-ActPaymentCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPaymentCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPaymentCode
Title: ActPaymentCode
Experimental: false
Description:
Code identifying the method or the movement of payment instructions.

Codes are drawn from X12 data element 591 (PaymentMethodCode)


Type: ValueSet
Id: v3-ActPriority
Web: ValueSet-v3-ActPriority.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPriority
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPriority
Title: ActPriority
Experimental: false
Description:
A code or set of codes (e.g., for routine, emergency,) specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.

*Discussion:* This attribute is used in orders to indicate the ordered priority, and in event documentation it indicates the actual priority used to perform the act. In definition mood it indicates the available priorities.


Type: ValueSet
Id: v3-ActPriorityCallback
Web: ValueSet-v3-ActPriorityCallback.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPriorityCallback
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPriorityCallback
Title: ActPriorityCallback
Experimental: false
Description:
Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)


Type: ValueSet
Id: v3-ActPrivacyLaw
Web: ValueSet-v3-ActPrivacyLaw.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPrivacyLaw
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPrivacyLaw
Title: ActPrivacyLaw
Experimental: false
Description:
ActPrivacyLaw codes may be associated with an Act or a Role to indicate the legal provision to which the assignment of an Act.confidentialityCode or Role.confidentialtyCode complies. May be used to further specify rationale for assignment of other ActPrivacyPolicy codes in the US realm, e.g., ETH and 42CFRPart2 can be differentiated from ETH and Title38Part1.


Type: ValueSet
Id: v3-ActPrivacyPolicy
Web: ValueSet-v3-ActPrivacyPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActPrivacyPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActPrivacyPolicy
Title: ActPrivacyPolicy
Experimental: false
Description:
ActPrivacyPolicyType codes support the designation of the 1..\* policies that are applicable to an Act such as a Consent Directive, a Role such as a VIP Patient, or an Entity such as a patient who is a minor. 1..\* ActPrivacyPolicyType values may be associated with an Act or Role to indicate the policies that govern the assignment of an Act or Role confidentialityCode. Use of multiple ActPrivacyPolicyType values enables fine grain specification of applicable policies, but must be carefully assigned to ensure cogency and avoid creation of conflicting policy mandates. Statutory title may be named in the ActClassPolicy Act Act.title to specify which privacy policy is being referenced.


Type: ValueSet
Id: v3-ActProductAcquisitionCode
Web: ValueSet-v3-ActProductAcquisitionCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActProductAcquisitionCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActProductAcquisitionCode
Title: ActProductAcquisitionCode
Experimental: false
Description:
The method that a product is obtained for use by the subject of the supply act (e.g. patient). Product examples are consumable or durable goods.


Type: ValueSet
Id: v3-ActProgramTypeCode
Web: ValueSet-v3-ActProgramTypeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActProgramTypeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActProgramTypeCode
Title: ActProgramTypeCode
Experimental: false
Description:
**Definition:** A set of codes used to indicate coverage under a program. A program is an organized structure for administering and funding coverage of a benefit package for covered parties meeting eligibility criteria, typically related to employment, health, financial, and demographic status. Programs are typically established or permitted by legislation with provisions for ongoing government oversight. Regulations may mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation. Risk of loss under a program in most cases would not meet what an underwriter would consider an insurable risk, i.e., the risk is not random in nature, not financially measurable, and likely requires subsidization with government funds.

*Discussion:* Programs do not have policy holders or subscribers. Program eligibles are enrolled based on health status, statutory eligibility, financial status, or age. Program eligibles who are covered parties under the program may be referred to as members, beneficiaries, eligibles, or recipients. Programs risk are underwritten by not for profit organizations such as governmental entities, and the beneficiaries typically do not pay for any or some portion of the cost of coverage. See CoveredPartyRoleType.


Type: ValueSet
Id: v3-ActReason
Web: ValueSet-v3-ActReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActReason
Version: 3.0.0
Status: active
Date: 2018-08-12
Name: ActReason
Title: v3 Code System ActReason
Experimental: false
Description:
 A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act.  Examples:
Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".


Type: ValueSet
Id: v3-ActRelationshipAccounting
Web: ValueSet-v3-ActRelationshipAccounting.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipAccounting
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipAccounting
Title: ActRelationshipAccounting
Experimental: false
Description:
Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element.


Type: ValueSet
Id: v3-ActRelationshipActProvenance
Web: ValueSet-v3-ActRelationshipActProvenance.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipActProvenance
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ActRelationshipActProvenance
Title: ActRelationshipActProvenance
Experimental: false
Description:
Used to convey the relationship between two or more Acts for purpose of tracking provenance relationships such as the following:

 *  A predecessor Act and a successor Act (e.g., a predecessor Lab Result from which a successor Lab Result in derived)
 *  A ProvenanceEvent Act and a target Act for which it records the Provenance (e.g., a target Act is an update of a predecessor Act)
 *  A predecessor ProvenanceEvent Act and a successor ProvenanceEvent Act

*UsageConstraint:* The v:ActRelationshipActProvenance is intended to limit the types of relationships that could be conveyed by the ActRelationshipType codes to a subset that pertains to these provenance relations.


Type: ValueSet
Id: v3-ActRelationshipArrival
Web: ValueSet-v3-ActRelationshipArrival.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipArrival
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipArrival
Title: ActRelationshipArrival
Experimental: false
Description:
The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act.


Type: ValueSet
Id: v3-ActRelationshipAssignsName
Web: ValueSet-v3-ActRelationshipAssignsName.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipAssignsName
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipAssignsName
Title: ActRelationshipAssignsName
Experimental: false
Description:
Used to assign a "name" to a condition thread. Source is a condition node, target can be any service.


Type: ValueSet
Id: v3-ActRelationshipBlocks
Web: ValueSet-v3-ActRelationshipBlocks.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipBlocks
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipBlocks
Title: ActRelationshipBlocks
Experimental: false
Description:
**Definition:** The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring.


Type: ValueSet
Id: v3-ActRelationshipCheckpointEnd
Web: ValueSet-v3-ActRelationshipCheckpointEnd.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpointEnd
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipCheckpointEnd
Title: ActRelationshipCheckpointEnd
Experimental: false
Description:
Condition is tested at the end of a repeated service execution. The service is repeated only if the condition is true (DO service WHILE condition).


Type: ValueSet
Id: v3-ActRelationshipCheckpointExit
Web: ValueSet-v3-ActRelationshipCheckpointExit.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpointExit
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipCheckpointExit
Title: ActRelationshipCheckpointExit
Experimental: false
Description:
Condition is a loop checkpoint, i.e. it is a step of an activity plan and, if negative causes the containing loop to exit.


Type: ValueSet
Id: v3-ActRelationshipCheckpointThrough
Web: ValueSet-v3-ActRelationshipCheckpointThrough.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCheckpointThrough
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipCheckpointThrough
Title: ActRelationshipCheckpointThrough
Experimental: false
Description:
Condition must be true throughout the execution and the service is interrupted (asynchronously) as soon as the condition turns false (asynchronous WHILE loop). The service must be interruptible.


Type: ValueSet
Id: v3-ActRelationshipCostTracking
Web: ValueSet-v3-ActRelationshipCostTracking.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCostTracking
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipCostTracking
Title: ActRelationshipCostTracking
Experimental: false
Description:
Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act.


Type: ValueSet
Id: v3-ActRelationshipCoveredBy
Web: ValueSet-v3-ActRelationshipCoveredBy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipCoveredBy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipCoveredBy
Title: ActRelationshipCoveredBy
Experimental: false
Description:
A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy.


Type: ValueSet
Id: v3-ActRelationshipDeparture
Web: ValueSet-v3-ActRelationshipDeparture.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipDeparture
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipDeparture
Title: ActRelationshipDeparture
Experimental: false
Description:
The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act.


Type: ValueSet
Id: v3-ActRelationshipDocumentProvenance
Web: ValueSet-v3-ActRelationshipDocumentProvenance.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentProvenance
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ActRelationshipDocumentProvenance
Title: ActRelationshipDocumentProvenance
Experimental: false
Description:
Used to convey the relationship between two or more Documents for purpose of tracking provenance relationships such as a predecessor Document and a successor Document.

For example, a predecessor Clinical Summary Document from which a successor Clinical Summary Document is derived.


Type: ValueSet
Id: v3-ActRelationshipEndsAfterOrConcurrentWithEndOf
Web: ValueSet-v3-ActRelationshipEndsAfterOrConcurrentWithEndOf.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipEndsAfterOrConcurrentWithEndOf
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ActRelationshipEndsAfterOrConcurrentWithEndOf
Title: ActRelationshipEndsAfterOrConcurrentWithEndOf
Experimental: false
Description:
Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.


Type: ValueSet
Id: v3-ActRelationshipEndsBeforeEnd
Web: ValueSet-v3-ActRelationshipEndsBeforeEnd.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipEndsBeforeEnd
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipEndsBeforeEnd
Title: ActRelationshipEndsBeforeEnd
Experimental: false
Description:
The source Act ends after the end of the target Act (i.e. if we say "ActOne EBE ActTwo", it means that ActOne ends before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).


Type: ValueSet
Id: v3-ActRelationshipEndsConcurrentWithStart
Web: ValueSet-v3-ActRelationshipEndsConcurrentWithStart.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipEndsConcurrentWithStart
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipEndsConcurrentWithStart
Title: ActRelationshipEndsConcurrentWithStart
Experimental: false
Description:
The source Act ends when the target act starts (i.e. if we say "ActOne ECWS ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target).


Type: ValueSet
Id: v3-ActRelationshipEpisodelink
Web: ValueSet-v3-ActRelationshipEpisodelink.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipEpisodelink
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipEpisodelink
Title: ActRelationshipEpisodelink
Experimental: false
Description:
Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter.


Type: ValueSet
Id: v3-ActRelationshipEvaluatesGoal
Web: ValueSet-v3-ActRelationshipEvaluatesGoal.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipEvaluatesGoal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipEvaluatesGoal
Title: ActRelationshipEvaluatesGoal
Experimental: false
Description:
A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a "goal distance" (e.g., goal to observation) can be "calculated" and need not be sent explicitly.


Type: ValueSet
Id: v3-ActRelationshipFulfills
Web: ValueSet-v3-ActRelationshipFulfills.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipFulfills
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipFulfills
Title: ActRelationshipFulfills
Experimental: false
Description:
The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act.


Type: ValueSet
Id: v3-ActRelationshipHasBoundedSupport
Web: ValueSet-v3-ActRelationshipHasBoundedSupport.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasBoundedSupport
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasBoundedSupport
Title: ActRelationshipHasBoundedSupport
Experimental: false
Description:
A specialization of "has support" (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the "ST elevation" observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general "has support" relation is used. Likewise, if a ROI on an image defines the true bounds of a "1st degree burn", the relation "has bounded support" is used; but if the ROI only points to the approximate area of the burn, the general "has support" relation is used.


Type: ValueSet
Id: v3-ActRelationshipHasCharge
Web: ValueSet-v3-ActRelationshipHasCharge.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasCharge
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasCharge
Title: ActRelationshipHasCharge
Experimental: false
Description:
A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service.

The financial transaction will define the charge (bill) for delivery or performance of the service.

Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.


Type: ValueSet
Id: v3-ActRelationshipHasComponent
Web: ValueSet-v3-ActRelationshipHasComponent.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasComponent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasComponent
Title: ActRelationshipHasComponent
Experimental: false
Description:
A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.


Type: ValueSet
Id: v3-ActRelationshipHasContinuingObjective
Web: ValueSet-v3-ActRelationshipHasContinuingObjective.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasContinuingObjective
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasContinuingObjective
Title: ActRelationshipHasContinuingObjective
Experimental: false
Description:
A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood.


Type: ValueSet
Id: v3-ActRelationshipHasContra-indication
Web: ValueSet-v3-ActRelationshipHasContra-indication.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasContra-indication
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasContraIndication
Title: ActRelationshipHasContra-indication
Experimental: false
Description:
A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used.


Type: ValueSet
Id: v3-ActRelationshipHasControlVariable
Web: ValueSet-v3-ActRelationshipHasControlVariable.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasControlVariable
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasControlVariable
Title: ActRelationshipHasControlVariable
Experimental: false
Description:
A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation.


Type: ValueSet
Id: v3-ActRelationshipHasCost
Web: ValueSet-v3-ActRelationshipHasCost.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasCost
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasCost
Title: ActRelationshipHasCost
Experimental: false
Description:
A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service.

The financial transaction will define the cost of delivery or performance of the service.

Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.


Type: ValueSet
Id: v3-ActRelationshipHasCredit
Web: ValueSet-v3-ActRelationshipHasCredit.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasCredit
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasCredit
Title: ActRelationshipHasCredit
Experimental: false
Description:
A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance.


Type: ValueSet
Id: v3-ActRelationshipHasDebit
Web: ValueSet-v3-ActRelationshipHasDebit.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasDebit
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasDebit
Title: ActRelationshipHasDebit
Experimental: false
Description:
A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance.


Type: ValueSet
Id: v3-ActRelationshipHasExplanation
Web: ValueSet-v3-ActRelationshipHasExplanation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasExplanation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasExplanation
Title: ActRelationshipHasExplanation
Experimental: false
Description:
This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition.


Type: ValueSet
Id: v3-ActRelationshipHasFinalObjective
Web: ValueSet-v3-ActRelationshipHasFinalObjective.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasFinalObjective
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasFinalObjective
Title: ActRelationshipHasFinalObjective
Experimental: false
Description:
A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood.


Type: ValueSet
Id: v3-ActRelationshipHasGeneralization
Web: ValueSet-v3-ActRelationshipHasGeneralization.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasGeneralization
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasGeneralization
Title: ActRelationshipHasGeneralization
Experimental: false
Description:
The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic).


Type: ValueSet
Id: v3-ActRelationshipHasGoal
Web: ValueSet-v3-ActRelationshipHasGoal.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasGoal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasGoal
Title: ActRelationshipHasGoal
Experimental: false
Description:
A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood.


Type: ValueSet
Id: v3-ActRelationshipHasOption
Web: ValueSet-v3-ActRelationshipHasOption.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasOption
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasOption
Title: ActRelationshipHasOption
Experimental: false
Description:
A relationship between a source Act that provides more detailed properties to the target Act.

The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.

The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.

Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options.


Type: ValueSet
Id: v3-ActRelationshipHasPre-condition
Web: ValueSet-v3-ActRelationshipHasPre-condition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasPre-condition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasPreCondition
Title: ActRelationshipHasPre-condition
Experimental: false
Description:
A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable.


Type: ValueSet
Id: v3-ActRelationshipHasPreviousInstance
Web: ValueSet-v3-ActRelationshipHasPreviousInstance.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasPreviousInstance
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasPreviousInstance
Title: ActRelationshipHasPreviousInstance
Experimental: false
Description:
A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services.


Type: ValueSet
Id: v3-ActRelationshipHasReferenceValues
Web: ValueSet-v3-ActRelationshipHasReferenceValues.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasReferenceValues
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasReferenceValues
Title: ActRelationshipHasReferenceValues
Experimental: false
Description:
Reference ranges are essentially descriptors of a class of result values assumed to be "normal", "abnormal", or "critical." Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results.


Type: ValueSet
Id: v3-ActRelationshipHasRisk
Web: ValueSet-v3-ActRelationshipHasRisk.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasRisk
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasRisk
Title: ActRelationshipHasRisk
Experimental: false
Description:
A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed.


Type: ValueSet
Id: v3-ActRelationshipHasSubject
Web: ValueSet-v3-ActRelationshipHasSubject.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasSubject
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasSubject
Title: ActRelationshipHasSubject
Experimental: false
Description:
Relates an Act to its subject Act that the first Act is primarily concerned with.

Examples

1.  The first Act may be a ControlAct manipulating the subject Act
2.  The first act is a region of interest (ROI) that defines a region within the subject Act.
3.  The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.

Constraints

An Act may have multiple subject acts.

Rationale

The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.


Type: ValueSet
Id: v3-ActRelationshipHasSupport
Web: ValueSet-v3-ActRelationshipHasSupport.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasSupport
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasSupport
Title: ActRelationshipHasSupport
Experimental: false
Description:
Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post.)


Type: ValueSet
Id: v3-ActRelationshipHasTrigger
Web: ValueSet-v3-ActRelationshipHasTrigger.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasTrigger
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipHasTrigger
Title: ActRelationshipHasTrigger
Experimental: false
Description:
A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified.

*Discussion:* This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded.


Type: ValueSet
Id: v3-ActRelationshipICSRInvestigation
Web: ValueSet-v3-ActRelationshipICSRInvestigation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipICSRInvestigation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipICSRInvestigation
Title: ActRelationshipICSRInvestigation
Experimental: false
Description:
**Description:** The ways that product safety Investigations, about which information is captured in an Individual Case Safety Report, are related to each other. One investigation may be performed at a patient care institution, and the second by a manufacturer, a third by a regulatory agency. They may all investigate the same case and are thus related. Other kinds of relationships are replacement (if the mode of the Investigation is changed).


Type: ValueSet
Id: v3-ActRelationshipInstantiatesMaster
Web: ValueSet-v3-ActRelationshipInstantiatesMaster.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipInstantiatesMaster
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipInstantiatesMaster
Title: ActRelationshipInstantiatesMaster
Experimental: false
Description:
Used to capture the link between a potential service ("master" or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults.


Type: ValueSet
Id: v3-ActRelationshipIsAppendage
Web: ValueSet-v3-ActRelationshipIsAppendage.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipIsAppendage
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipIsAppendage
Title: ActRelationshipIsAppendage
Experimental: false
Description:
An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered.


Type: ValueSet
Id: v3-ActRelationshipIsDerivedFrom
Web: ValueSet-v3-ActRelationshipIsDerivedFrom.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipIsDerivedFrom
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipIsDerivedFrom
Title: ActRelationshipIsDerivedFrom
Experimental: false
Description:
Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.


Type: ValueSet
Id: v3-ActRelationshipIsEtiologyFor
Web: ValueSet-v3-ActRelationshipIsEtiologyFor.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipIsEtiologyFor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipIsEtiologyFor
Title: ActRelationshipIsEtiologyFor
Experimental: false
Description:
An assertion that a new observation was assumed to be the cause for another existing observation. The assumption is attributed to the same actor who asserts the observation. This is stronger and more specific than the support link. For example, a growth of Staphylococcus aureus may be considered the cause of an abscess. The source (cause) is typically an observation, but may be any service, while the target must be an observation.


Type: ValueSet
Id: v3-ActRelationshipIsManifestationOf
Web: ValueSet-v3-ActRelationshipIsManifestationOf.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipIsManifestationOf
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipIsManifestationOf
Title: ActRelationshipIsManifestationOf
Experimental: false
Description:
An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.


Type: ValueSet
Id: v3-ActRelationshipJoinDetached
Web: ValueSet-v3-ActRelationshipJoinDetached.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipJoinDetached
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipJoinDetached
Title: ActRelationshipJoinDetached
Experimental: false
Description:
Detach this branch from the other branches so it will not be resynchronized with the other branches.


Type: ValueSet
Id: v3-ActRelationshipJoinExclusiveWait
Web: ValueSet-v3-ActRelationshipJoinExclusiveWait.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipJoinExclusiveWait
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipJoinExclusiveWait
Title: ActRelationshipJoinExclusiveWait
Experimental: false
Description:
Wait for any one of the branches in the set of exclusive wait branches to terminate, then discontinue all the other exclusive wait branches.


Type: ValueSet
Id: v3-ActRelationshipLimitedBy
Web: ValueSet-v3-ActRelationshipLimitedBy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipLimitedBy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipLimitedBy
Title: ActRelationshipLimitedBy
Experimental: false
Description:
A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood.


Type: ValueSet
Id: v3-ActRelationshipMatchesTrigger
Web: ValueSet-v3-ActRelationshipMatchesTrigger.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipMatchesTrigger
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipMatchesTrigger
Title: ActRelationshipMatchesTrigger
Experimental: false
Description:
A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is "observation of pain" and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger.


Type: ValueSet
Id: v3-ActRelationshipModifies
Web: ValueSet-v3-ActRelationshipModifies.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipModifies
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipModifies
Title: ActRelationshipModifies
Experimental: false
Description:
Definition: Used to link a newer version or 'snapshot' of a business object (source) to an older version or 'snapshot' of the same business object (target).

*Usage:*The identifier of the Act should be the same for both source and target. If the identifiers are distinct, RPLC should be used instead.

Name from source to target = "modifiesPrior"

Name from target to source = "modifiesByNew"


Type: ValueSet
Id: v3-ActRelationshipObjective
Web: ValueSet-v3-ActRelationshipObjective.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipObjective
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipObjective
Title: ActRelationshipObjective
Experimental: false
Description:
The target act is a desired outcome of the source act. Source is any act (typically an intervention). Target must be an observation in criterion mood.


Type: ValueSet
Id: v3-ActRelationshipOccurrence
Web: ValueSet-v3-ActRelationshipOccurrence.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipOccurrence
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipOccurrence
Title: ActRelationshipOccurrence
Experimental: false
Description:
The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the "completion track" but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa).


Type: ValueSet
Id: v3-ActRelationshipOutcome
Web: ValueSet-v3-ActRelationshipOutcome.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipOutcome
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipOutcome
Title: ActRelationshipOutcome
Experimental: false
Description:
An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-condition".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute


Type: ValueSet
Id: v3-ActRelationshipPertains
Web: ValueSet-v3-ActRelationshipPertains.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipPertains
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipPertains
Title: ActRelationshipPertains
Experimental: false
Description:
This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays.


Type: ValueSet
Id: v3-ActRelationshipProvidesEvidenceFor
Web: ValueSet-v3-ActRelationshipProvidesEvidenceFor.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipProvidesEvidenceFor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipProvidesEvidenceFor
Title: ActRelationshipProvidesEvidenceFor
Experimental: false
Description:
Indicates that the target Act provides evidence in support of the action represented by the source Act. The target is not a 'reason' for the source act, but rather gives supporting information on why the source act is an appropriate course of action. Possible targets might be clinical trial results, journal articles, similar successful therapies, etc.

*Rationale:* Provides a mechanism for conveying clinical justification for non-approved or otherwise non-traditional therapies.


Type: ValueSet
Id: v3-ActRelationshipRe-challenge
Web: ValueSet-v3-ActRelationshipRe-challenge.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipRe-challenge
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipReChallenge
Title: ActRelationshipRe-challenge
Experimental: false
Description:
**Description:**A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated.


Type: ValueSet
Id: v3-ActRelationshipReason
Web: ValueSet-v3-ActRelationshipReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipReason
Title: ActRelationshipReason
Experimental: false
Description:
The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action.

*Discussion:* In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.


Type: ValueSet
Id: v3-ActRelationshipReferencesOrder
Web: ValueSet-v3-ActRelationshipReferencesOrder.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipReferencesOrder
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipReferencesOrder
Title: ActRelationshipReferencesOrder
Experimental: false
Description:
Relates either an appointment request or an appointment to the order for the service being scheduled.


Type: ValueSet
Id: v3-ActRelationshipRefersTo
Web: ValueSet-v3-ActRelationshipRefersTo.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipRefersTo
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipRefersTo
Title: ActRelationshipRefersTo
Experimental: false
Description:
A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.


Type: ValueSet
Id: v3-ActRelationshipReplaces
Web: ValueSet-v3-ActRelationshipReplaces.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipReplaces
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipReplaces
Title: ActRelationshipReplaces
Experimental: false
Description:
A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.


Type: ValueSet
Id: v3-ActRelationshipReverses
Web: ValueSet-v3-ActRelationshipReverses.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipReverses
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipReverses
Title: ActRelationshipReverses
Experimental: false
Description:
A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.

Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction.

Constraints: the "completion track" mood of the target Act must be equally or more "actual" than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT.


Type: ValueSet
Id: v3-ActRelationshipSequel
Web: ValueSet-v3-ActRelationshipSequel.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSequel
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSequel
Title: ActRelationshipSequel
Experimental: false
Description:
An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation.


Type: ValueSet
Id: v3-ActRelationshipSplitExclusiveTryOnce
Web: ValueSet-v3-ActRelationshipSplitExclusiveTryOnce.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplitExclusiveTryOnce
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSplitExclusiveTryOnce
Title: ActRelationshipSplitExclusiveTryOnce
Experimental: false
Description:
The pre-condition associated with the branch is evaluated once and if true the branch may be entered. All other exclusive branches compete with each other and only one will be selected. This implements a COND, IF and CASE conditionals, or "XOR-split." The order in which the branches are considered may be specified in the priorityNumber attribute.


Type: ValueSet
Id: v3-ActRelationshipSplitExclusiveWait
Web: ValueSet-v3-ActRelationshipSplitExclusiveWait.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplitExclusiveWait
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSplitExclusiveWait
Title: ActRelationshipSplitExclusiveWait
Experimental: false
Description:
A branch is selected as soon as the pre-condition associated with the branch evaluates to true. If the condition is false, the branch may be entered later, when the condition turns true. All other exclusive branches compete with each other and only one will be selected. Each waiting branch executes in parallel with the default join code wait (see below). The order in which the branches are considered may be specified in the Service\_relationship.priority\_nmb.


Type: ValueSet
Id: v3-ActRelationshipSplitInclusiveTryOnce
Web: ValueSet-v3-ActRelationshipSplitInclusiveTryOnce.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplitInclusiveTryOnce
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSplitInclusiveTryOnce
Title: ActRelationshipSplitInclusiveTryOnce
Experimental: false
Description:
A branch is executed if its associated preconditions permit. If associated preconditions do not permit, the branch is dropped. Inclusive branches are not suppressed and do not suppress other branches.


Type: ValueSet
Id: v3-ActRelationshipSplitInclusiveWait
Web: ValueSet-v3-ActRelationshipSplitInclusiveWait.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSplitInclusiveWait
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSplitInclusiveWait
Title: ActRelationshipSplitInclusiveWait
Experimental: false
Description:
A branch is executed as soon as its associated conditions permit. If the condition is false, the branch may be entered later, when the condition turns true. Inclusive branches are not suppressed and do not suppress other branches. Each waiting branch executes in parallel with the default join code wait (see below).


Type: ValueSet
Id: v3-ActRelationshipStartsAfterEndOf
Web: ValueSet-v3-ActRelationshipStartsAfterEndOf.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipStartsAfterEndOf
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipStartsAfterEndOf
Title: ActRelationshipStartsAfterEndOf
Experimental: false
Description:
**Description:**A relationship in which the target act takes place with a defined temporal relationship with respect to the time at which the source act terminates.


Type: ValueSet
Id: v3-ActRelationshipStartsAfterStartOf
Web: ValueSet-v3-ActRelationshipStartsAfterStartOf.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipStartsAfterStartOf
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipStartsAfterStartOf
Title: ActRelationshipStartsAfterStartOf
Experimental: false
Description:
The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).


Type: ValueSet
Id: v3-ActRelationshipStartsBeforeEnd
Web: ValueSet-v3-ActRelationshipStartsBeforeEnd.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipStartsBeforeEnd
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipStartsBeforeEnd
Title: ActRelationshipStartsBeforeEnd
Experimental: false
Description:
The source Act starts after the end of the target Act (i.e. if we say "ActOne SBE ActTwo", it means that ActOne starts before the end of ActTwo, therefore ActOne is the source and ActTwo is the target).


Type: ValueSet
Id: v3-ActRelationshipStartsConcurrentWithEnd
Web: ValueSet-v3-ActRelationshipStartsConcurrentWithEnd.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipStartsConcurrentWithEnd
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipStartsConcurrentWithEnd
Title: ActRelationshipStartsConcurrentWithEnd
Experimental: false
Description:
The source Act starts when the target act ends (i.e. if we say "ActOne SCWE ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target).


Type: ValueSet
Id: v3-ActRelationshipSubset
Web: ValueSet-v3-ActRelationshipSubset.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSubset
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSubset
Title: ActRelationshipSubset
Experimental: false
Description:
Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.

Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.


Type: ValueSet
Id: v3-ActRelationshipSucceeds
Web: ValueSet-v3-ActRelationshipSucceeds.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSucceeds
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSucceeds
Title: ActRelationshipSucceeds
Experimental: false
Description:
**Definition:** A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act.


Type: ValueSet
Id: v3-ActRelationshipSummarizedBy
Web: ValueSet-v3-ActRelationshipSummarizedBy.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipSummarizedBy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipSummarizedBy
Title: ActRelationshipSummarizedBy
Experimental: false
Description:
An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period.


Type: ValueSet
Id: v3-ActRelationshipTransformation
Web: ValueSet-v3-ActRelationshipTransformation.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipTransformation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipTransformation
Title: ActRelationshipTransformation
Experimental: false
Description:
Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)


Type: ValueSet
Id: v3-ActRelationshipType
Web: ValueSet-v3-ActRelationshipType.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipType
Title: ActRelationshipType
Experimental: false
Description:
A code specifying the meaning and purpose of every ActRelationship instance. Each of its values implies specific constraints to what kinds of Act objects can be related and in which way.

*Discussion:* The types of act relationships fall under one of 5 categories:

1.) (De)-composition, with composite (source) and component (target)

2.) Sequel which includes follow-up, fulfillment, instantiation, replacement, transformation, etc. that all have in common that source and target are Acts of essentially the same kind but with variances in mood and other attributes, and where the target exists before the source and the source refers to the target that it links back to.

3.) Pre-condition, trigger, reason, contraindication, with the conditioned Act at the source and the condition or reason at the target.

4.) Post-condition, outcome, goal and risk, with the Act at the source having the outcome or goal at the target.

5.) A host of functional relationships including support, cause, derivation, etc. generalized under the notion of "pertinence".


Type: ValueSet
Id: v3-ActRelationshipUpdatesCondition
Web: ValueSet-v3-ActRelationshipUpdatesCondition.html
Url: http://terminology.hl7.org/ValueSet/v3-ActRelationshipUpdatesCondition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActRelationshipUpdatesCondition
Title: ActRelationshipUpdatesCondition
Experimental: false
Description:
A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.


Type: ValueSet
Id: v3-ActResearchInformationAccess
Web: ValueSet-v3-ActResearchInformationAccess.html
Url: http://terminology.hl7.org/ValueSet/v3-ActResearchInformationAccess
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActResearchInformationAccess
Title: ActResearchInformationAccess
Experimental: false
Description:
**Definition:** Consent to have healthcare information in an electronic health record accessed for research purposes.


Type: ValueSet
Id: v3-ActShortStayEncounterCode
Web: ValueSet-v3-ActShortStayEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActShortStayEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActShortStayEncounterCode
Title: ActShortStayEncounterCode
Experimental: false
Description:
**Definition:**An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours.


Type: ValueSet
Id: v3-ActSpecObsCode
Web: ValueSet-v3-ActSpecObsCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActSpecObsCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActSpecObsCode
Title: ActSpecObsCode
Experimental: false
Description:
Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation


Type: ValueSet
Id: v3-ActStatusHeld
Web: ValueSet-v3-ActStatusHeld.html
Url: http://terminology.hl7.org/ValueSet/v3-ActStatusHeld
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActStatusHeld
Title: ActStatusHeld
Experimental: false
Description:
An Act that is still in the preparatory stages has been put aside. No action can occur until the Act is released.


Type: ValueSet
Id: v3-ActStatusNormal
Web: ValueSet-v3-ActStatusNormal.html
Url: http://terminology.hl7.org/ValueSet/v3-ActStatusNormal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActStatusNormal
Title: ActStatusNormal
Experimental: false
Description:
Encompasses the expected states of an Act, but excludes "nullified" and "obsolete" which represent unusual terminal states for the life-cycle.


Type: ValueSet
Id: v3-ActStatusNullified
Web: ValueSet-v3-ActStatusNullified.html
Url: http://terminology.hl7.org/ValueSet/v3-ActStatusNullified
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActStatusNullified
Title: ActStatusNullified
Experimental: false
Description:
This 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.


Type: ValueSet
Id: v3-ActStatusSuspended
Web: ValueSet-v3-ActStatusSuspended.html
Url: http://terminology.hl7.org/ValueSet/v3-ActStatusSuspended
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActStatusSuspended
Title: ActStatusSuspended
Experimental: false
Description:
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


Type: ValueSet
Id: v3-ActSubstanceAdministrationImmunizationCode
Web: ValueSet-v3-ActSubstanceAdministrationImmunizationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdministrationImmunizationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActSubstanceAdministrationImmunizationCode
Title: ActSubstanceAdministrationImmunizationCode
Experimental: false
Description:
The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents.


Type: ValueSet
Id: v3-ActSupplyFulfillmentRefusalReason
Web: ValueSet-v3-ActSupplyFulfillmentRefusalReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ActSupplyFulfillmentRefusalReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActSupplyFulfillmentRefusalReason
Title: ActSupplyFulfillmentRefusalReason
Experimental: false
Description:
Indicates why a fulfiller refused to fulfill a supply order, and considered it important to notify other providers of their decision. E.g. "Suspect fraud", "Possible abuse", "Contraindicated".

(used when capturing 'refusal to fill' annotations)


Type: ValueSet
Id: v3-ActTaskPatientInformationReviewCode
Web: ValueSet-v3-ActTaskPatientInformationReviewCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActTaskPatientInformationReviewCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActTaskPatientInformationReviewCode
Title: ActTaskPatientInformationReviewCode
Experimental: false
Description:
A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record.


Type: ValueSet
Id: v3-ActTherapyDurationWorkingListCode
Web: ValueSet-v3-ActTherapyDurationWorkingListCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActTherapyDurationWorkingListCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActTherapyDurationWorkingListCode
Title: ActTherapyDurationWorkingListCode
Experimental: false
Description:
Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed".


Type: ValueSet
Id: v3-ActTransportationModeCode
Web: ValueSet-v3-ActTransportationModeCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActTransportationModeCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActTransportationModeCode
Title: ActTransportationModeCode
Experimental: false
Description:
Characterizes how a transportation act was or will be carried out.

*Examples:* Via private transport, via public transit, via courier.


Type: ValueSet
Id: v3-ActUSPrivacyLaw
Web: ValueSet-v3-ActUSPrivacyLaw.html
Url: http://terminology.hl7.org/ValueSet/v3-ActUSPrivacyLaw
Version: 3.0.0
Status: retired
Date: 2014-03-26
Name: ActUSPrivacyLaw
Title: ActUSPrivacyLaw
Experimental: false
Description:
***Deprecation Comment:*** Content moved to ActCode, and is now represented in value set ActPrivacyLaw.


Type: ValueSet
Id: v3-ActUncertainty
Web: ValueSet-v3-ActUncertainty.html
Url: http://terminology.hl7.org/ValueSet/v3-ActUncertainty
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActUncertainty
Title: ActUncertainty
Experimental: false
Description:
A code indicating whether the Act statement as a whole, with its subordinate components has been asserted to be uncertain in any way.

*Examples:* Patient might have had a cholecystectomy procedure in the past (but isn't sure).

*Constraints:* Uncertainty asserted using this attribute applies to the combined meaning of the Act statement established by all descriptive attributes (e.g., Act.code, Act.effectiveTime, Observation.value, SubstanceAdministration.doseQuantity, etc.), and the meanings of any components.

*Discussion:*This is not intended for use to replace or compete with uncertainty associated with a Observation.values alone or other individual attributes of the class. Such pointed indications of uncertainty should be specified by applying the PPD, UVP or UVN data type extensions to the specific attribute. Particularly if the uncertainty is uncertainty of a quantitative measurement value, this must still be represented by a PPD<PQ> in the value and NOT using the uncertaintyCode. Also, when differential diagnoses are enumerated or weighed for probability, the UVP<CD> or UVN<CD> must be used, not the uncertaintyCode. The use of the uncertaintyCode is appropriate only if the entirety of the Act and its dependent Acts is questioned.

Note that very vague uncertainty may be thought related to negationInd, however, the two concepts are really independent. One may be very uncertain about an event, but that does not mean that one is certain about the negation of the event.


Type: ValueSet
Id: v3-ActVirtualEncounterCode
Web: ValueSet-v3-ActVirtualEncounterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ActVirtualEncounterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ActVirtualEncounterCode
Title: ActVirtualEncounterCode
Experimental: false
Description:
**Definition:**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.


Type: ValueSet
Id: v3-AdditionalLocator
Web: ValueSet-v3-AdditionalLocator.html
Url: http://terminology.hl7.org/ValueSet/v3-AdditionalLocator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AdditionalLocator
Title: AdditionalLocator
Experimental: false
Description:
This can be a unit designator, such as apartment number, suite number, or floor. There may be several unit designators in an address (e.g., "3rd floor, Appt. 342".) This can also be a designator pointing away from the location (e.g. Across the street from).


Type: ValueSet
Id: v3-AddressLine
Web: ValueSet-v3-AddressLine.html
Url: http://terminology.hl7.org/ValueSet/v3-AddressLine
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AddressLine
Title: AddressLine
Experimental: false
Description:
**Description:** An address line is for either an additional locator, a delivery address or a street address.


Type: ValueSet
Id: v3-AddressPartType
Web: ValueSet-v3-AddressPartType.html
Url: http://terminology.hl7.org/ValueSet/v3-AddressPartType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AddressPartType
Title: AddressPartType
Experimental: false
Description:
Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"


Type: ValueSet
Id: v3-AddressRepresentationUse
Web: ValueSet-v3-AddressRepresentationUse.html
Url: http://terminology.hl7.org/ValueSet/v3-AddressRepresentationUse
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AddressRepresentationUse
Title: AddressRepresentationUse
Experimental: false
Description:
**Description:**Identifies the different representations of a Address. The representation may affect how the address is used. (E.g. use of Ideographic for formal communications.)


Type: ValueSet
Id: v3-AdjudicatedWithAdjustments
Web: ValueSet-v3-AdjudicatedWithAdjustments.html
Url: http://terminology.hl7.org/ValueSet/v3-AdjudicatedWithAdjustments
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AdjudicatedWithAdjustments
Title: AdjudicatedWithAdjustments
Experimental: false
Description:
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).

Also includes the concept 'Adjudicate as zero' and items not covered under a particular Policy.

Invoice element can be reversed (nullified).

Recommend that the invoice element is saved for DUR (Drug Utilization Reporting).


Type: ValueSet
Id: v3-AdministrableDrugForm
Web: ValueSet-v3-AdministrableDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-AdministrableDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AdministrableDrugForm
Title: AdministrableDrugForm
Experimental: false
Description:
Indicates the form in which the drug product should be administered.

This element only needs to be specified when (a) the form in which the drug is measured for dispensing differs from the form in which the drug is administered; and (b) the form in which the quantity of the administered drug being administered is not expressed as a discrete measured mass or volume.*Usage:*


Type: ValueSet
Id: v3-AdministrativeContactRoleType
Web: ValueSet-v3-AdministrativeContactRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-AdministrativeContactRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AdministrativeContactRoleType
Title: AdministrativeContactRoleType
Experimental: false
Description:
A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClassCommissioningParty.


Type: ValueSet
Id: v3-AdoptedChild
Web: ValueSet-v3-AdoptedChild.html
Url: http://terminology.hl7.org/ValueSet/v3-AdoptedChild
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AdoptedChild
Title: AdoptedChild
Experimental: false
Description:
The player of the role is a child taken into a family through legal means and raised by the scoping person (parent) as his or her own child.


Type: ValueSet
Id: v3-AlgorithmicDecisionObservationMethod
Web: ValueSet-v3-AlgorithmicDecisionObservationMethod.html
Url: http://terminology.hl7.org/ValueSet/v3-AlgorithmicDecisionObservationMethod
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AlgorithmicDecisionObservationMethod
Title: AlgorithmicDecisionObservationMethod
Experimental: false
Description:
Reaching a decision through the application of an algorithm designed to weigh the different factors involved.


Type: ValueSet
Id: v3-AllergyStatus
Web: ValueSet-v3-AllergyStatus.html
Url: http://terminology.hl7.org/ValueSet/v3-AllergyStatus
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: AllergyStatus
Title: Allergy Status
Experimental: false
Description:
The clinical status of an allergy disposition (Clinical Focus)

Used in Program: C-CDA, C-CDA R2.1 2017-06-09 using this value set


Type: ValueSet
Id: v3-AmbulanceHIPAA
Web: ValueSet-v3-AmbulanceHIPAA.html
Url: http://terminology.hl7.org/ValueSet/v3-AmbulanceHIPAA
Version: 4.0.0
Status: retired
Date: 2014-03-26
Name: AmbulanceHIPAA
Title: AmbulanceHIPAA
Experimental: false
Description:
An emergency vehicle used for transporting patients to a health care facility after injury or illness. Types of ambulances used in the United States include ground (surface) ambulance, rotor-wing (helicopter), and fixed-wing aircraft (airplane).


Type: ValueSet
Id: v3-AssignedNonPersonLivingSubjectRoleType
Web: ValueSet-v3-AssignedNonPersonLivingSubjectRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-AssignedNonPersonLivingSubjectRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AssignedNonPersonLivingSubjectRoleType
Title: AssignedNonPersonLivingSubjectRoleType
Experimental: false
Description:
**Description:**A role type that is used to further qualify a non-person subject playing a role where the role class attribute is set to RoleClass AssignedEntity


Type: ValueSet
Id: v3-AuthorizedParticipationFunction
Web: ValueSet-v3-AuthorizedParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-AuthorizedParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AuthorizedParticipationFunction
Title: AuthorizedParticipationFunction
Experimental: false
Description:
This code is used to specify the exact function an actor is authorized to have in a service in all necessary detail.


Type: ValueSet
Id: v3-AuthorizedReceiverParticipationFunction
Web: ValueSet-v3-AuthorizedReceiverParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-AuthorizedReceiverParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AuthorizedReceiverParticipationFunction
Title: AuthorizedReceiverParticipationFunction
Experimental: false
Description:
This code is used to specify the exact function an actor is authorized to have as a receiver of information that is the subject of a consent directive or consent override.


Type: ValueSet
Id: v3-AutomobileInsurancePolicy
Web: ValueSet-v3-AutomobileInsurancePolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-AutomobileInsurancePolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: AutomobileInsurancePolicy
Title: AutomobileInsurancePolicy
Experimental: false
Description:
**Definition:** An insurance policy for losses sustained in an automobile accident that typically covers losses incurred by the named insured and parties who may be claimants for losses, such as pedestrians and passengers.


Type: ValueSet
Id: v3-BiotherapeuticNon-personLivingSubjectRoleType
Web: ValueSet-v3-BiotherapeuticNon-personLivingSubjectRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-BiotherapeuticNon-personLivingSubjectRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: BiotherapeuticNonPersonLivingSubjectRoleType
Title: BiotherapeuticNon-personLivingSubjectRoleType
Experimental: false
Description:
**Description:**Animals, including fish and insects, and microorganisms which may participate as assigned entities in biotherapies.


Type: ValueSet
Id: v3-BottleEntityType
Web: ValueSet-v3-BottleEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-BottleEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: BottleEntityType
Title: BottleEntityType
Experimental: false
Description:
A container, typically rounded, either glass or plastic with a narrow neck and capable of storing liquid.


Type: ValueSet
Id: v3-BuildingNumber
Web: ValueSet-v3-BuildingNumber.html
Url: http://terminology.hl7.org/ValueSet/v3-BuildingNumber
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: BuildingNumber
Title: BuildingNumber
Experimental: false
Description:
The number of a building, house or lot alongside the street. Also known as "primary street number". This does not number the street but rather the building.


Type: ValueSet
Id: v3-CUI
Web: ValueSet-v3-CUI.html
Url: http://terminology.hl7.org/ValueSet/v3-CUI
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: CUI
Title: CUI
Experimental: false
Description:
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.

Purpose: Supports the selection of the entire ControlledUnclassifiedInformation value set for e.g., rules engine policy set purposes.


Type: ValueSet
Id: v3-CUILabel
Web: ValueSet-v3-CUILabel.html
Url: http://terminology.hl7.org/ValueSet/v3-CUILabel
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: CUILabel
Title: CUILabel
Experimental: false
Description:
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

Purpose: Supports the selection of ControlledUnclassifiedInformation leaf concepts for use, e.g., in security labels.


Type: ValueSet
Id: v3-CVDiagTherPracticeSetting
Web: ValueSet-v3-CVDiagTherPracticeSetting.html
Url: http://terminology.hl7.org/ValueSet/v3-CVDiagTherPracticeSetting
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CVDiagTherPracticeSetting
Title: CVDiagTherPracticeSetting
Experimental: false
Description:
A practice setting where cardiovascular diagnostic procedures or therapeutic interventions are performed (e.g., cardiac catheterization lab, echocardiography suite)


Type: ValueSet
Id: v3-CapsuleDrugForm
Web: ValueSet-v3-CapsuleDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-CapsuleDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CapsuleDrugForm
Title: CapsuleDrugForm
Experimental: false
Description:
A solid dosage form in which the drug is enclosed within either a hard or soft soluble container or "shell" made from a suitable form of gelatin.


Type: ValueSet
Id: v3-CaseTransmissionMode
Web: ValueSet-v3-CaseTransmissionMode.html
Url: http://terminology.hl7.org/ValueSet/v3-CaseTransmissionMode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CaseTransmissionMode
Title: CaseTransmissionMode
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ChronicCareFacility
Web: ValueSet-v3-ChronicCareFacility.html
Url: http://terminology.hl7.org/ValueSet/v3-ChronicCareFacility
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ChronicCareFacility
Title: ChronicCareFacility
Experimental: false
Description:
(1) A hospital including a physical plant and personnel that provides multidisciplinary diagnosis and treatment for diseases that have one or more of the following characteristics: is permanent; leaves residual disability; is caused by nonreversible pathological alteration; requires special training of the patient for rehabilitation; and/or may be expected to require a long period of supervision or care. In addition, patients require the safety, security, and shelter of these specialized inpatient or partial hospitalization settings. (2) A hospital that provides medical and skilled nursing services to patients with long-term illnesses who are not in an acute phase but who require an intensity of services not available in nursing homes


Type: ValueSet
Id: v3-CitizenRoleType
Web: ValueSet-v3-CitizenRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-CitizenRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CitizenRoleType
Title: CitizenRoleType
Experimental: false
Description:
A role type used to qualify a person's legal status within a country or nation.

**Examples:**

 *  Full citizen
 *  Asylum seeker
 *  Permit card holder


Type: ValueSet
Id: v3-ClaimantCoveredPartyRoleType
Web: ValueSet-v3-ClaimantCoveredPartyRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-ClaimantCoveredPartyRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ClaimantCoveredPartyRoleType
Title: ClaimantCoveredPartyRoleType
Experimental: false
Description:
**Description**A role recognized through the eligibility of a party play a claimant for benefits covered or provided under an insurance policy.


Type: ValueSet
Id: v3-ClassNullFlavor
Web: ValueSet-v3-ClassNullFlavor.html
Url: http://terminology.hl7.org/ValueSet/v3-ClassNullFlavor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ClassNullFlavor
Title: ClassNullFlavor
Experimental: false
Description:
**Description:** Subset of null flavors, used for associations as needed for the ITS, and used in InfrastructureRoot.


Type: ValueSet
Id: v3-ClinicalResearchObservationReason
Web: ValueSet-v3-ClinicalResearchObservationReason.html
Url: http://terminology.hl7.org/ValueSet/v3-ClinicalResearchObservationReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ClinicalResearchObservationReason
Title: ClinicalResearchObservationReason
Experimental: false
Description:
**Definition:**SSpecifies the reason that a test was performed or observation collected in a clinical research study.

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


Type: ValueSet
Id: v3-Compartment
Web: ValueSet-v3-Compartment.html
Url: http://terminology.hl7.org/ValueSet/v3-Compartment
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Compartment
Title: Compartment
Experimental: false
Description:
A named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System)

*Usage Note:* This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field.

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."


Type: ValueSet
Id: v3-CompliancePackageEntityType
Web: ValueSet-v3-CompliancePackageEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-CompliancePackageEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CompliancePackageEntityType
Title: CompliancePackageEntityType
Experimental: false
Description:
A container intended to contain sufficient material for more than one use, but grouped or organized to provide individual access to sufficient material for a single use. Often used to ensure that the proper type and amount of material is consumed/expended for each use.


Type: ValueSet
Id: v3-CompositeMeasureScoring
Web: ValueSet-v3-CompositeMeasureScoring.html
Url: http://terminology.hl7.org/ValueSet/v3-CompositeMeasureScoring
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: CompositeMeasureScoring
Title: CompositeMeasureScoring
Experimental: false
Description:
Observation values that communicate the method used in a quality measure to combine the component measure results that are included in a composite measure.

*Steward:* CQI WG


Type: ValueSet
Id: v3-ConditionDetectedIssueCode
Web: ValueSet-v3-ConditionDetectedIssueCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ConditionDetectedIssueCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ConditionDetectedIssueCode
Title: ConditionDetectedIssueCode
Experimental: false
Description:
Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis


Type: ValueSet
Id: v3-Conditional
Web: ValueSet-v3-Conditional.html
Url: http://terminology.hl7.org/ValueSet/v3-Conditional
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Conditional
Title: Conditional
Experimental: false
Description:
Some conditions may be attached to an allowable substitution. An allowable substitution is based on a match to any other attributes that may be specified.


Type: ValueSet
Id: v3-Confidentiality
Web: ValueSet-v3-Confidentiality.html
Url: http://terminology.hl7.org/ValueSet/v3-Confidentiality
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Confidentiality
Title: Confidentiality
Experimental: false
Description:
Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".


Type: ValueSet
Id: v3-ConfidentialityModifiers
Web: ValueSet-v3-ConfidentialityModifiers.html
Url: http://terminology.hl7.org/ValueSet/v3-ConfidentialityModifiers
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ConfidentialityModifiers
Title: ConfidentialityModifiers
Experimental: false
Description:
Modifiers of role based access rights (multiple allowed)

*Usage Note:* All codes that are referenced by this value set were retired as of the November 2013 Harmonization cycle. Guidance for what to use instead of the v:ConfidentialityModifers leaf concepts: celebrity, sensitive, and taboo: These codes have been revised and are now included under v:ActCode at:

 *  V:ActInformationSensitivityPolicy:2.16.840.1.113883.1.11.20429 - taboo
 *  V:InformationSensitivityPolicy:2.16.840.1.113883.1.11.20428 - celebrity/VIP and patient requested sensitivity


Type: ValueSet
Id: v3-ConsenterParticipationFunction
Web: ValueSet-v3-ConsenterParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-ConsenterParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ConsenterParticipationFunction
Title: ConsenterParticipationFunction
Experimental: false
Description:
This code is used to specify the exact function an actor is authorized to have in authoring a consent directive.


Type: ValueSet
Id: v3-ContextControlAdditive
Web: ValueSet-v3-ContextControlAdditive.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlAdditive
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlAdditive
Title: ContextControlAdditive
Experimental: false
Description:
The association adds to the existing context associated with the Act. Both this association and any associations propagated from ancestor Acts are interpreted as being related to this Act.


Type: ValueSet
Id: v3-ContextControlAdditiveNon-propagating
Web: ValueSet-v3-ContextControlAdditiveNon-propagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlAdditiveNon-propagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlAdditiveNonPropagating
Title: ContextControlAdditiveNon-propagating
Experimental: false
Description:
The association adds to the existing context associated with the Act, but will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Non-Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts for the purpose of this Act. However only the previously propagated authors will propagate to any child Acts that allow context to be propagated.


Type: ValueSet
Id: v3-ContextControlAdditivePropagating
Web: ValueSet-v3-ContextControlAdditivePropagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlAdditivePropagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlAdditivePropagating
Title: ContextControlAdditivePropagating
Experimental: false
Description:
The association adds to the existing context associated with the Act, and will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Additive, Propagating" it means that the author will be added to the set of author participations that have propagated from ancestor Acts, and will itself propagate with the other authors to any child Acts that allow context to be propagated.


Type: ValueSet
Id: v3-ContextControlNonPropagating
Web: ValueSet-v3-ContextControlNonPropagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlNonPropagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlNonPropagating
Title: ContextControlNonPropagating
Experimental: false
Description:
The association applies only to the current Act and will not propagate to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd).


Type: ValueSet
Id: v3-ContextControlOverriding
Web: ValueSet-v3-ContextControlOverriding.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlOverriding
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlOverriding
Title: ContextControlOverriding
Experimental: false
Description:
The association adds to the existing context associated with the Act, but replaces associations propagated from ancestor Acts whose typeCodes are the same.


Type: ValueSet
Id: v3-ContextControlOverridingNon-propagating
Web: ValueSet-v3-ContextControlOverridingNon-propagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlOverridingNon-propagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlOverridingNonPropagating
Title: ContextControlOverridingNon-propagating
Experimental: false
Description:
The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. However, this overriding association will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Non-Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts. Furthermore, no author participations whatsoever will propagate to any child Acts that allow context to be propagated.


Type: ValueSet
Id: v3-ContextControlOverridingPropagating
Web: ValueSet-v3-ContextControlOverridingPropagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlOverridingPropagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlOverridingPropagating
Title: ContextControlOverridingPropagating
Experimental: false
Description:
The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. This overriding association will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as "Overriding, Propagating" it means that the author will replace the set of author participations that have propagated from ancestor Acts, and will itself be the only author to propagate to any child Acts that allow context to be propagated.


Type: ValueSet
Id: v3-ContextControlPropagating
Web: ValueSet-v3-ContextControlPropagating.html
Url: http://terminology.hl7.org/ValueSet/v3-ContextControlPropagating
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ContextControlPropagating
Title: ContextControlPropagating
Experimental: false
Description:
The association propagates to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd).


Type: ValueSet
Id: v3-ControlActNullificationReasonCode
Web: ValueSet-v3-ControlActNullificationReasonCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ControlActNullificationReasonCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ControlActNullificationReasonCode
Title: ControlActNullificationReasonCode
Experimental: false
Description:
**Description:**Identifies reasons for nullifying (retracting) a particular control act.

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


Type: ValueSet
Id: v3-ControlledSubstanceMonitoringProtocol
Web: ValueSet-v3-ControlledSubstanceMonitoringProtocol.html
Url: http://terminology.hl7.org/ValueSet/v3-ControlledSubstanceMonitoringProtocol
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ControlledSubstanceMonitoringProtocol
Title: ControlledSubstanceMonitoringProtocol
Experimental: false
Description:
A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction.


Type: ValueSet
Id: v3-CoverageEligibilityReason
Web: ValueSet-v3-CoverageEligibilityReason.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageEligibilityReason
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageEligibilityReason
Title: CoverageEligibilityReason
Experimental: false
Description:
**Description:**Identifies the reason or rational for why a person is eligible for benefits under an insurance policy or program.

**Examples:** A new employee is eligible for health insurance as an employment benefit. A person meets eligibility criteria for government program coverage based on financial, age or health status.


Type: ValueSet
Id: v3-CoverageLevelObservationValue
Web: ValueSet-v3-CoverageLevelObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageLevelObservationValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageLevelObservationValue
Title: CoverageLevelObservationValue
Experimental: false
Description:
**Description:**Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status.


Type: ValueSet
Id: v3-CoverageLimitObservationValue
Web: ValueSet-v3-CoverageLimitObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageLimitObservationValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageLimitObservationValue
Title: CoverageLimitObservationValue
Experimental: false
Description:
**Description:**Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program.


Type: ValueSet
Id: v3-CoverageParticipationFunction
Web: ValueSet-v3-CoverageParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageParticipationFunction
Title: CoverageParticipationFunction
Experimental: false
Description:
**Definition:** Set of codes indicating the manner in which sponsors, underwriters, and payers participate in a policy or program.


Type: ValueSet
Id: v3-CoverageRoleType
Web: ValueSet-v3-CoverageRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageRoleType
Title: CoverageRoleType
Experimental: false
Description:
Role recognized through the issuance of insurance coverage to an identified covered party who has this relationship with the policy holder such as the policy holder themselves (self), spouse, child, etc


Type: ValueSet
Id: v3-CoverageSponsorRoleType
Web: ValueSet-v3-CoverageSponsorRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-CoverageSponsorRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoverageSponsorRoleType
Title: CoverageSponsorRoleType
Experimental: false
Description:
**Description:**Codes that indicate a specific type of sponsor. Used when the sponsor's role is only either as a fully insured sponsor or only as a self-insured sponsor. NOTE: Where a sponsor may be either, use the SponsorParticipationFunction.code (fully insured or self insured) to indicate the type of responsibility. (CO6-0057)


Type: ValueSet
Id: v3-CoveredPartyRoleType
Web: ValueSet-v3-CoveredPartyRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-CoveredPartyRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CoveredPartyRoleType
Title: CoveredPartyRoleType
Experimental: false
Description:
A role recognized through the eligibility of an identified living subject for benefits covered under an insurance policy or a program. Eligibility as a covered party may be conditioned on a relationship with (1) the policy holder such as the policy holder who is covered as an individual under a poliy or as a party sponsored for coverage by the policy holder.

**Example:**An employee as a subscriber; or (2) on being scoped another covered party such as the subscriber, as in the case of a dependent.

**Discussion:** The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". Other codes in the Abstract Value Set CoveredPartyRoleType domain can be "post-coordinated" with the EligiblePartyRoleType codes to denote comparable concepts. Decoupling the concepts is intended to support a wider range of concepts and semantic comparability of coded concepts.


Type: ValueSet
Id: v3-CreamDrugForm
Web: ValueSet-v3-CreamDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-CreamDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: CreamDrugForm
Title: CreamDrugForm
Experimental: false
Description:
A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable.


Type: ValueSet
Id: v3-DedicatedClinicalLocationRoleType
Web: ValueSet-v3-DedicatedClinicalLocationRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-DedicatedClinicalLocationRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DedicatedClinicalLocationRoleType
Title: DedicatedClinicalLocationRoleType
Experimental: false
Description:
A role of a place that further classifies the clinical setting (e.g., cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) in which care is delivered during an encounter.


Type: ValueSet
Id: v3-DedicatedNonClinicalLocationRoleType
Web: ValueSet-v3-DedicatedNonClinicalLocationRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-DedicatedNonClinicalLocationRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DedicatedNonClinicalLocationRoleType
Title: DedicatedNonClinicalLocationRoleType
Experimental: false
Description:
A role of a place that further classifies a setting that is intended to house the provision of non-clinical services.


Type: ValueSet
Id: v3-DedicatedServiceDeliveryLocationRoleType
Web: ValueSet-v3-DedicatedServiceDeliveryLocationRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-DedicatedServiceDeliveryLocationRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DedicatedServiceDeliveryLocationRoleType
Title: DedicatedServiceDeliveryLocationRoleType
Experimental: false
Description:
A role of a place that further classifies a setting that is intended to house the provision of services.


Type: ValueSet
Id: v3-DeliveryAddressLine
Web: ValueSet-v3-DeliveryAddressLine.html
Url: http://terminology.hl7.org/ValueSet/v3-DeliveryAddressLine
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DeliveryAddressLine
Title: DeliveryAddressLine
Experimental: false
Description:
A delivery address line is frequently used instead of breaking out delivery mode, delivery installation, etc. An address generally has only a delivery address line or a street address line, but not both.


Type: ValueSet
Id: v3-DentistHIPAA
Web: ValueSet-v3-DentistHIPAA.html
Url: http://terminology.hl7.org/ValueSet/v3-DentistHIPAA
Version: 4.0.0
Status: retired
Date: 2014-03-26
Name: DentistHIPAA
Title: DentistHIPAA
Experimental: false
Description:
A dentist is a person qualified by a doctorate in dental surgery (D.D. S.) or dental medicine (D.M.D.). licensed by the state to practice dentistry, and practicing within the scope of that license. Many dentists are general practitioners who handle a wide variety of dental needs. Other dentists practice in one of eight specialty areas recognized by the American Dental Association: oral and maxillofacial surgery, orthodontics, periodontics, prosthodontics, endodontics, public health, oral pathology and pediatric dentistry.


Type: ValueSet
Id: v3-DependentCoveredPartyRoleType
Web: ValueSet-v3-DependentCoveredPartyRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-DependentCoveredPartyRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DependentCoveredPartyRoleType
Title: DependentCoveredPartyRoleType
Experimental: false
Description:
**Description:** A role recognized through the eligibility of a party to play a dependent for benefits covered or provided under a health insurance policy because of an association with the subscriber that is recognized by the policy underwriter.


Type: ValueSet
Id: v3-DiseaseProgram
Web: ValueSet-v3-DiseaseProgram.html
Url: http://terminology.hl7.org/ValueSet/v3-DiseaseProgram
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DiseaseProgram
Title: DiseaseProgram
Experimental: false
Description:
**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.


Type: ValueSet
Id: v3-DocumentSectionType
Web: ValueSet-v3-DocumentSectionType.html
Url: http://terminology.hl7.org/ValueSet/v3-DocumentSectionType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: DocumentSectionType
Title: DocumentSectionType
Experimental: false
Description:
The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc.


Type: ValueSet
Id: v3-EPSG-GeodeticParameterDataset
Web: ValueSet-v3-EPSG-GeodeticParameterDataset.html
Url: http://terminology.hl7.org/ValueSet/v3-EPSG-GeodeticParameterDataset
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EPSGGeodeticParameterDataset
Title: EPSG-GeodeticParameterDataset
Experimental: false
Description:
**Description:** The EPSG (European Petroleum Survey Group) dataset represents all Datums, coordinate references (projected and 2D geographic) and coordinate systems (including Cartesian coordinate systems) used in surveying worldwide. Each record includes a 4-8 digit unique identifier. The current version is available from http://www.epsg.org/. The database contains over 4000 records covering spatial data applications worldwide.


Type: ValueSet
Id: v3-ERPracticeSetting
Web: ValueSet-v3-ERPracticeSetting.html
Url: http://terminology.hl7.org/ValueSet/v3-ERPracticeSetting
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ERPracticeSetting
Title: ERPracticeSetting
Experimental: false
Description:
The section of a health care facility for providing rapid treatment to victims of sudden illness or trauma.


Type: ValueSet
Id: v3-EmergencyMedicalServiceProviderHIPAA
Web: ValueSet-v3-EmergencyMedicalServiceProviderHIPAA.html
Url: http://terminology.hl7.org/ValueSet/v3-EmergencyMedicalServiceProviderHIPAA
Version: 4.0.0
Status: retired
Date: 2014-03-26
Name: EmergencyMedicalServiceProviderHIPAA
Title: EmergencyMedicalServiceProviderHIPAA
Experimental: false
Description:
Broad category for individuals who complete additional training and education in the area of pre-hospital emergency services and are licensed and/or practice within the scope of that training.


Type: ValueSet
Id: v3-EmergencyPharmacySupplyType
Web: ValueSet-v3-EmergencyPharmacySupplyType.html
Url: http://terminology.hl7.org/ValueSet/v3-EmergencyPharmacySupplyType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EmergencyPharmacySupplyType
Title: EmergencyPharmacySupplyType
Experimental: false
Description:
A supply action where there is no 'valid' order for the supplied medication. E.g. Emergency vacation supply, weekend supply (when prescriber is unavailable to provide a renewal prescription)


Type: ValueSet
Id: v3-EncounterSpecialCourtesy
Web: ValueSet-v3-EncounterSpecialCourtesy.html
Url: http://terminology.hl7.org/ValueSet/v3-EncounterSpecialCourtesy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EncounterSpecialCourtesy
Title: EncounterSpecialCourtesy
Experimental: false
Description:
A code identifying special courtesies extended to the patient. For example, no courtesies, extended courtesies, professional courtesy, VIP courtesies.


Type: ValueSet
Id: v3-EntityClass
Web: ValueSet-v3-EntityClass.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClass
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClass
Title: EntityClass
Experimental: false
Description:
Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable.

The value sets beneath are encoded in Entity.code and are drawn from multiple, frequently external, domains that reflect much more fine-grained typing.


Type: ValueSet
Id: v3-EntityClassChemicalSubstance
Web: ValueSet-v3-EntityClassChemicalSubstance.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassChemicalSubstance
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassChemicalSubstance
Title: EntityClassChemicalSubstance
Experimental: false
Description:
A substance that is fully defined by an organic or inorganic chemical formula, includes mixtures of other chemical substances. Refine using, e.g., IUPAC codes.


Type: ValueSet
Id: v3-EntityClassDevice
Web: ValueSet-v3-EntityClassDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassDevice
Title: EntityClassDevice
Experimental: false
Description:
A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind of device is identified by the code attribute inherited from Entity.

*Usage:* This includes durable (reusable) medical equipment as well as disposable equipment.


Type: ValueSet
Id: v3-EntityClassFood
Web: ValueSet-v3-EntityClassFood.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassFood
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassFood
Title: EntityClassFood
Experimental: false
Description:
Naturally occurring, processed or manufactured entities that are primarily used as food for humans and animals.


Type: ValueSet
Id: v3-EntityClassGroup
Web: ValueSet-v3-EntityClassGroup.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassGroup
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassGroup
Title: EntityClassGroup
Experimental: false
Description:
A grouping of resources (personnel, material, or places) to be used for scheduling purposes. May be a pool of like-type resources, a team, or combination of personnel, material and places.


Type: ValueSet
Id: v3-EntityClassHealthChartEntity
Web: ValueSet-v3-EntityClassHealthChartEntity.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassHealthChartEntity
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassHealthChartEntity
Title: EntityClassHealthChartEntity
Experimental: false
Description:
A health chart included to serve as a document receiving entity in the management of medical records.


Type: ValueSet
Id: v3-EntityClassLivingSubject
Web: ValueSet-v3-EntityClassLivingSubject.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassLivingSubject
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassLivingSubject
Title: EntityClassLivingSubject
Experimental: false
Description:
Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.)


Type: ValueSet
Id: v3-EntityClassPlace
Web: ValueSet-v3-EntityClassPlace.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassPlace
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassPlace
Title: EntityClassPlace
Experimental: false
Description:
A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant.


Type: ValueSet
Id: v3-EntityClassPublicInstitution
Web: ValueSet-v3-EntityClassPublicInstitution.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassPublicInstitution
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassPublicInstitution
Title: EntityClassPublicInstitution
Experimental: false
Description:
An agency of the people of a state often assuming some authority over a certain matter. Includes government, governmental agencies, associations.


Type: ValueSet
Id: v3-EntityClassState
Web: ValueSet-v3-EntityClassState.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityClassState
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityClassState
Title: EntityClassState
Experimental: false
Description:
A politically organized body of people bonded by territory, culture, or ethnicity, having sovereignty (to a certain extent) granted by other states (enclosing or neighboring states). This includes countries (nations), provinces (e.g., one of the United States of America or a French departement), counties or municipalities. Refine using, e.g., ISO country codes, FIPS-PUB state codes, etc.


Type: ValueSet
Id: v3-EntityCode
Web: ValueSet-v3-EntityCode.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityCode
Title: EntityCode
Experimental: false
Description:
A value representing the specific kind of Entity the instance represents.

*Examples:* A medical building, a Doberman Pinscher, a blood collection tube, a tissue biopsy.

*Rationale:* For each Entity, the value for this attribute is drawn from one of several coding systems depending on the Entity classCode, such as living subjects (animal and plant taxonomies), chemical substance (e.g., IUPAC code), organizations, insurance company, government agency, hospital, park, lake, syringe, etc. It is possible that Entity.code may be so fine grained that it represents a single instance. An example is the CDC vaccine manufacturer code, modeled as a concept vocabulary, when in fact each concept refers to a single instance.


Type: ValueSet
Id: v3-EntityDeterminerDescribedGroup
Web: ValueSet-v3-EntityDeterminerDescribedGroup.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityDeterminerDescribedGroup
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityDeterminerDescribedGroup
Title: EntityDeterminerDescribedGroup
Experimental: false
Description:
A standard value set allowing reference to all EntityDeterminer codes that are equal to or specializations of GROUPKIND. This is the value set used when a model indicates that the binding is to "<= GROUPKIND".


Type: ValueSet
Id: v3-EntityDeterminerDescribedQuantified
Web: ValueSet-v3-EntityDeterminerDescribedQuantified.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityDeterminerDescribedQuantified
Version: 3.0.0
Status: retired
Date: 2012-03-15
Name: EntityDeterminerDescribedQuantified
Title: EntityDeterminerDescribedQuantified
Experimental: false
Description:
The described quantified determiner indicates that the given Entity is taken as a general description of a specific amount of a thing. For example, QUANTIFIED\_KIND of syringe (quantity = 3,) stands for exactly three syringes.


Type: ValueSet
Id: v3-EntityDeterminerDetermined
Web: ValueSet-v3-EntityDeterminerDetermined.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityDeterminerDetermined
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityDeterminerDetermined
Title: EntityDeterminerDetermined
Experimental: false
Description:
The described determiner is used to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples.


Type: ValueSet
Id: v3-EntityDeterminerSpecific
Web: ValueSet-v3-EntityDeterminerSpecific.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityDeterminerSpecific
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityDeterminerSpecific
Title: EntityDeterminerSpecific
Experimental: false
Description:
The specific determiner indicates that the given Entity is taken as one specific thing instance. For example, a human INSTANCE (quantity = 1,) stands for exactly one human being.


Type: ValueSet
Id: v3-EntityDeterminerSpecificGroup
Web: ValueSet-v3-EntityDeterminerSpecificGroup.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityDeterminerSpecificGroup
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityDeterminerSpecificGroup
Title: EntityDeterminerSpecificGroup
Experimental: false
Description:
A standard value set allowing reference to all EntityDeterminer codes that are equal to or specializations of GROUP. This is the value set used when a model indicates that the binding is to "<= GROUP".


Type: ValueSet
Id: v3-EntityInformationSensitivityPolicy
Web: ValueSet-v3-EntityInformationSensitivityPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityInformationSensitivityPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityInformationSensitivityPolicy
Title: EntityInformationSensitivityPolicy
Experimental: false
Description:
EntitySensitivity codes are used to convey a policy that is applicable to sensitive information conveyed by an entity attribute. May be used to bind a Role.confidentialityCode associated with an Entity per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity."


Type: ValueSet
Id: v3-EntityStatusNormal
Web: ValueSet-v3-EntityStatusNormal.html
Url: http://terminology.hl7.org/ValueSet/v3-EntityStatusNormal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: EntityStatusNormal
Title: EntityStatusNormal
Experimental: false
Description:
The 'typical' state. Excludes "nullified" which represents the termination state of an Entity record instance that was created in error.


Type: ValueSet
Id: v3-Ethnicity
Web: ValueSet-v3-Ethnicity.html
Url: http://terminology.hl7.org/ValueSet/v3-Ethnicity
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Ethnicity
Title: Ethnicity
Experimental: false
Description:
In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.


Type: ValueSet
Id: v3-ExpectedSubset
Web: ValueSet-v3-ExpectedSubset.html
Url: http://terminology.hl7.org/ValueSet/v3-ExpectedSubset
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ExpectedSubset
Title: ExpectedSubset
Experimental: false
Description:
An occurrence that is scheduled to occur in the future. An Act whose effective time is greater than 'now', where 'now' is the time the instance is authored.


Type: ValueSet
Id: v3-ExtendedReleaseCapsule
Web: ValueSet-v3-ExtendedReleaseCapsule.html
Url: http://terminology.hl7.org/ValueSet/v3-ExtendedReleaseCapsule
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ExtendedReleaseCapsule
Title: ExtendedReleaseCapsule
Experimental: false
Description:
A solid dosage form in which the drug is enclosed within either a hard or soft soluble container made from a suitable form of gelatin, and which releases a drug (or drugs) in such a manner to allow a reduction in dosing frequency as compared to that drug (or drugs) presented as a conventional dosage form.


Type: ValueSet
Id: v3-ExtendedReleaseTablet
Web: ValueSet-v3-ExtendedReleaseTablet.html
Url: http://terminology.hl7.org/ValueSet/v3-ExtendedReleaseTablet
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ExtendedReleaseTablet
Title: ExtendedReleaseTablet
Experimental: false
Description:
A solid dosage form containing a drug which allows at least a reduction in dosing frequency as compared to that drug presented in conventional dosage form.


Type: ValueSet
Id: v3-FosterChild
Web: ValueSet-v3-FosterChild.html
Url: http://terminology.hl7.org/ValueSet/v3-FosterChild
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: FosterChild
Title: FosterChild
Experimental: false
Description:
The player of the role is a child receiving parental care and nurture from the scoping person (parent) but not related to him or her through legal or blood ties.


Type: ValueSet
Id: v3-GTIN
Web: ValueSet-v3-GTIN.html
Url: http://terminology.hl7.org/ValueSet/v3-GTIN
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GTIN
Title: GTIN
Experimental: false
Description:
**Description:**Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council).


Type: ValueSet
Id: v3-GTSAbbreviationHolidaysUSNational
Web: ValueSet-v3-GTSAbbreviationHolidaysUSNational.html
Url: http://terminology.hl7.org/ValueSet/v3-GTSAbbreviationHolidaysUSNational
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GTSAbbreviationHolidaysUSNational
Title: GTSAbbreviationHolidaysUSNational
Experimental: false
Description:
United States National Holidays (public holidays for federal employees established by U.S. Federal law 5 U.S.C. 6103.)


Type: ValueSet
Id: v3-GTSAbbreviationOther
Web: ValueSet-v3-GTSAbbreviationOther.html
Url: http://terminology.hl7.org/ValueSet/v3-GTSAbbreviationOther
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GTSAbbreviationOther
Title: GTSAbbreviationOther
Experimental: false
Description:
**Description:**Other, more specific, abbreviations defined for the General timing Specification data type, that are specializations of one of the Base concepts.


Type: ValueSet
Id: v3-GasDrugForm
Web: ValueSet-v3-GasDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-GasDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GasDrugForm
Title: GasDrugForm
Experimental: false
Description:
Any elastic aeriform fluid in which the molecules are separated from one another and have free paths.


Type: ValueSet
Id: v3-GelDrugForm
Web: ValueSet-v3-GelDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-GelDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GelDrugForm
Title: GelDrugForm
Experimental: false
Description:
A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid.


Type: ValueSet
Id: v3-GeneticObservationInterpretation
Web: ValueSet-v3-GeneticObservationInterpretation.html
Url: http://terminology.hl7.org/ValueSet/v3-GeneticObservationInterpretation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GeneticObservationInterpretation
Title: GeneticObservationInterpretation
Experimental: false
Description:
Codes that specify interpretation of genetic analysis, such as "positive", "negative", "carrier", "responsive", etc.


Type: ValueSet
Id: v3-GeneticObservationMethod
Web: ValueSet-v3-GeneticObservationMethod.html
Url: http://terminology.hl7.org/ValueSet/v3-GeneticObservationMethod
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GeneticObservationMethod
Title: GeneticObservationMethod
Experimental: false
Description:
A code that provides additional detail about the means or technique used to ascertain the genetic analysis. Example, PCR, Micro Array


Type: ValueSet
Id: v3-GeneticObservationValue
Web: ValueSet-v3-GeneticObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-GeneticObservationValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: GeneticObservationValue
Title: GeneticObservationValue
Experimental: false
Description:
**Description:** The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc.


Type: ValueSet
Id: v3-HL7AccommodationCode
Web: ValueSet-v3-HL7AccommodationCode.html
Url: http://terminology.hl7.org/ValueSet/v3-HL7AccommodationCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: HL7AccommodationCode
Title: HL7AccommodationCode
Experimental: false
Description:
**Description:**Accommodation type. In Intent mood, represents the accommodation type requested. In Event mood, represents accommodation assigned/used. In Definition mood, represents the available accommodation type.


Type: ValueSet
Id: v3-HL7FormatCodes
Web: ValueSet-v3-HL7FormatCodes.html
Url: http://terminology.hl7.org/ValueSet/v3-HL7FormatCodes
Version: 2.1.0
Status: active
Date: 2024-02-16
Name: HL7FormatCodes
Title: HL7 ValueSet of Format Codes for use with Document Sharing
Experimental: false
Description:
The HL7-FormatCodes value set is defined to be the set of FormatCode(s) defined by implementation guides published by HL7 and other SDOs. The use of a formatCode from the FormatCodes value set specifies the technical format that a document conforms to. The formatCode is a further specialization more detailed than the mime-type. The formatCode provides sufficient information to allow any potential document content consumer to know if it can process and/or display the content of the document based on the document encoding, structure and template conformance indicated by the formatCode. The set of formatCodes is intended to be extensible. The Content Logical Description is defined intentionally to permit formatCodes defined by other Standards Development Organizations to be added by inclusion of additional formatCode Code Systems.


Type: ValueSet
Id: v3-HL7StandardVersionCode
Web: ValueSet-v3-HL7StandardVersionCode.html
Url: http://terminology.hl7.org/ValueSet/v3-HL7StandardVersionCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: HL7StandardVersionCode
Title: HL7StandardVersionCode
Experimental: false
Description:
This is the domain of HL7 version codes for the Version 3 standards. Values are to be determined by HL7 and added with each new version of the HL7 Standard.


Type: ValueSet
Id: v3-HealthCareCommonProcedureCodingSystem
Web: ValueSet-v3-HealthCareCommonProcedureCodingSystem.html
Url: http://terminology.hl7.org/ValueSet/v3-HealthCareCommonProcedureCodingSystem
Version: 4.0.0
Status: active
Date: 2023-10-11
Name: HealthCareCommonProcedureCodingSystem
Title: HealthCareCommonProcedureCodingSystem
Experimental: false
Description: This value set includes all HCPCS Level II codes.
Copyright:
This material derives from the HL7 Terminology THO. THO is copyright  1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html


Type: ValueSet
Id: v3-HealthcareServiceLocation
Web: ValueSet-v3-HealthcareServiceLocation.html
Url: http://terminology.hl7.org/ValueSet/v3-HealthcareServiceLocation
Version: 4.0.0
Status: active
Date: 2014-03-26
Name: HealthcareServiceLocation
Title: HealthcareServiceLocation
Experimental: false
Description:
A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the CMS Place of Service code set NHSN location code system that has been developed over a number of years through CDCaTMs interaction with a variety of healthcare facilities and is intended to serve a variety of reporting needs where coding of healthcare service locations is required.  Excluded codes are those that do not represent an actual location where health care services can be delivered, IE: Float, or a location aggregation.


Type: ValueSet
Id: v3-HospitalPracticeSetting
Web: ValueSet-v3-HospitalPracticeSetting.html
Url: http://terminology.hl7.org/ValueSet/v3-HospitalPracticeSetting
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: HospitalPracticeSetting
Title: HospitalPracticeSetting
Experimental: false
Description:
An acute care institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured.


Type: ValueSet
Id: v3-IndividualInsuredCoveredPartyRoleType
Web: ValueSet-v3-IndividualInsuredCoveredPartyRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-IndividualInsuredCoveredPartyRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: IndividualInsuredCoveredPartyRoleType
Title: IndividualInsuredCoveredPartyRoleType
Experimental: false
Description:
**Description**A role recognized through the eligibility of a party to play an individual insured for benefits covered or provided under an insurance policy where the party is also the policy holder.


Type: ValueSet
Id: v3-InformationSensitivityPolicy
Web: ValueSet-v3-InformationSensitivityPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-InformationSensitivityPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: InformationSensitivityPolicy
Title: InformationSensitivityPolicy
Experimental: false
Description:
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" 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 Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.title.


Type: ValueSet
Id: v3-InhalerMedicalDevice
Web: ValueSet-v3-InhalerMedicalDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-InhalerMedicalDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: InhalerMedicalDevice
Title: InhalerMedicalDevice
Experimental: false
Description:
A small device used for inhaling medicine in the form of a vapour or gas in order to ease a respiratory condition such as asthma or to relieve nasal congestion.


Type: ValueSet
Id: v3-InvoiceElementAdjudicated
Web: ValueSet-v3-InvoiceElementAdjudicated.html
Url: http://terminology.hl7.org/ValueSet/v3-InvoiceElementAdjudicated
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: InvoiceElementAdjudicated
Title: InvoiceElementAdjudicated
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-InvoiceElementPaid
Web: ValueSet-v3-InvoiceElementPaid.html
Url: http://terminology.hl7.org/ValueSet/v3-InvoiceElementPaid
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: InvoiceElementPaid
Title: InvoiceElementPaid
Experimental: false
Description:
Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date.


Type: ValueSet
Id: v3-InvoiceElementSubmitted
Web: ValueSet-v3-InvoiceElementSubmitted.html
Url: http://terminology.hl7.org/ValueSet/v3-InvoiceElementSubmitted
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: InvoiceElementSubmitted
Title: InvoiceElementSubmitted
Experimental: false
Description:
Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included.


Type: ValueSet
Id: v3-IrrigationSolution
Web: ValueSet-v3-IrrigationSolution.html
Url: http://terminology.hl7.org/ValueSet/v3-IrrigationSolution
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: IrrigationSolution
Title: IrrigationSolution
Experimental: false
Description:
A sterile solution intended to bathe or flush open wounds or body cavities; they're used topically, never parenterally.


Type: ValueSet
Id: v3-IssueFilterCode
Web: ValueSet-v3-IssueFilterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-IssueFilterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: IssueFilterCode
Title: IssueFilterCode
Experimental: false
Description:
**Description:**Indicates how result sets should be filtered based on whether they have associated issues.


Type: ValueSet
Id: v3-KitEntityType
Web: ValueSet-v3-KitEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-KitEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: KitEntityType
Title: KitEntityType
Experimental: false
Description:
A container for a diverse collection of products intended to be used together for some purpose (e.g. Medicinal kits often contain a syringe, a needle and the injectable medication).


Type: ValueSet
Id: v3-KnowledgeSubjectObservationValue
Web: ValueSet-v3-KnowledgeSubjectObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-KnowledgeSubjectObservationValue
Version: 5.0.0
Status: active
Date: 2010-03-16
Name: KnowledgeSubjectObservationValue
Title: KnowledgeSubjectObservationValue
Experimental: false
Description:
Observation values used to indicate a knowledge subject of interest for which knowledge content is requested (e.g., a medication, a laboratory test, a medical condition).


Type: ValueSet
Id: v3-KnowledgeSubtopicObservationValue
Web: ValueSet-v3-KnowledgeSubtopicObservationValue.html
Url: http://terminology.hl7.org/ValueSet/v3-KnowledgeSubtopicObservationValue
Version: 4.0.0
Status: active
Date: 2010-03-16
Name: KnowledgeSubtopicObservationValue
Title: KnowledgeSubtopicObservationValue
Experimental: false
Description:
Observation values used to indicate a knowledge subtopic of interest for which knowledge content is requested (e.g., treatment, etiology, prognosis).


Type: ValueSet
Id: v3-LOINCObservationActContextAgeDefinitionCode
Web: ValueSet-v3-LOINCObservationActContextAgeDefinitionCode.html
Url: http://terminology.hl7.org/ValueSet/v3-LOINCObservationActContextAgeDefinitionCode
Version: 3.0.0
Status: active
Date: 2010-03-16
Name: LOINCObservationActContextAgeDefinitionCode
Title: LOINCObservationActContextAgeDefinitionCode
Experimental: false
Description:
Identifies a type of observation that captures the age of an entity involved in an act with no implied method of determination.


Type: ValueSet
Id: v3-LOINCObservationActContextAgeType
Web: ValueSet-v3-LOINCObservationActContextAgeType.html
Url: http://terminology.hl7.org/ValueSet/v3-LOINCObservationActContextAgeType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LOINCObservationActContextAgeType
Title: LOINCObservationActContextAgeType
Experimental: false
Description:
**Definition:**The set of LOINC codes for the act of determining the period of time that has elapsed since an entity was born or created.


Type: ValueSet
Id: v3-LaboratoryObservationSubtype
Web: ValueSet-v3-LaboratoryObservationSubtype.html
Url: http://terminology.hl7.org/ValueSet/v3-LaboratoryObservationSubtype
Version: 2.0.0
Status: active
Date: 2021-03-24T00:00:00.000-06:00
Name: LaboratoryObservationSubType
Title: Laboratory Observation Sub-Type
Experimental: false
Description:
Value Set of codes specifying an observation sub-type used with observation type code RSLT (Result).


Type: ValueSet
Id: v3-LanguageAbilityMode
Web: ValueSet-v3-LanguageAbilityMode.html
Url: http://terminology.hl7.org/ValueSet/v3-LanguageAbilityMode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LanguageAbilityMode
Title: LanguageAbilityMode
Experimental: false
Description:
A value representing the method of expression of the language.

*Example:*Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.


Type: ValueSet
Id: v3-LanguageAbilityProficiency
Web: ValueSet-v3-LanguageAbilityProficiency.html
Url: http://terminology.hl7.org/ValueSet/v3-LanguageAbilityProficiency
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LanguageAbilityProficiency
Title: LanguageAbilityProficiency
Experimental: false
Description:
A value representing the level of proficiency in a language.

*Example:*Excellent, good, fair, poor.


Type: ValueSet
Id: v3-LifeInsurancePolicy
Web: ValueSet-v3-LifeInsurancePolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-LifeInsurancePolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LifeInsurancePolicy
Title: LifeInsurancePolicy
Experimental: false
Description:
**Definition:** A policy under which the insurer agrees to pay a sum of money upon the occurrence of the covered partys death. In return, the policyholder agrees to pay a stipulated amount called a premium at regular intervals. Life insurance indemnifies the beneficiary for the loss of the insurable interest that a beneficiary has in the life of a covered party. For persons related by blood, a substantial interest established through love and affection, and for all other persons, a lawful and substantial economic interest in having the life of the insured continue. An insurable interest is required when purchasing life insurance on another person. Specific exclusions are often written into the contract to limit the liability of the insurer; for example claims resulting from suicide or relating to war, riot and civil commotion.

*Discussion:*A life insurance policy may be used by the covered party as a source of health care coverage in the case of a viatical settlement, which is the sale of a life insurance policy by the policy owner, before the policy matures. Such a sale, at a price discounted from the face amount of the policy but usually in excess of the premiums paid or current cash surrender value, provides the seller an immediate cash settlement. Generally, viatical settlements involve insured individuals with a life expectancy of less than two years. In countries without state-subsidized healthcare and high healthcare costs (e.g. United States), this is a practical way to pay extremely high health insurance premiums that severely ill people face. Some people are also familiar with life settlements, which are similar transactions but involve insureds with longer life expectancies (two to fifteen years).


Type: ValueSet
Id: v3-Liquid
Web: ValueSet-v3-Liquid.html
Url: http://terminology.hl7.org/ValueSet/v3-Liquid
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Liquid
Title: Liquid
Experimental: false
Description:
A state of substance that is an intermediate one entered into as matter goes from solid to gas; liquids are also intermediate in that they have neither the orderliness of a crystal nor the randomness of a gas. (Note: This term should not be used to describe solutions, only pure chemicals in their liquid state.)


Type: ValueSet
Id: v3-LiquidLiquidEmulsion
Web: ValueSet-v3-LiquidLiquidEmulsion.html
Url: http://terminology.hl7.org/ValueSet/v3-LiquidLiquidEmulsion
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LiquidLiquidEmulsion
Title: LiquidLiquidEmulsion
Experimental: false
Description:
A two-phase system in which one liquid is dispersed throughout another liquid in the form of small droplets.


Type: ValueSet
Id: v3-LiquidSolidSuspension
Web: ValueSet-v3-LiquidSolidSuspension.html
Url: http://terminology.hl7.org/ValueSet/v3-LiquidSolidSuspension
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LiquidSolidSuspension
Title: LiquidSolidSuspension
Experimental: false
Description:
A liquid preparation which consists of solid particles dispersed throughout a liquid phase in which the particles are not soluble.


Type: ValueSet
Id: v3-LogicalObservationIdentifierNamesAndCodes
Web: ValueSet-v3-LogicalObservationIdentifierNamesAndCodes.html
Url: http://terminology.hl7.org/ValueSet/v3-LogicalObservationIdentifierNamesAndCodes
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LogicalObservationIdentifierNamesAndCodes
Title: LogicalObservationIdentifierNamesAndCodes
Experimental: false
Description:
The LOINC database provides a set of universal names and ID codes for identifying laboratory and clinical test results. The purpose is to facilitate the exchange and pooling of results, such as blood hemoglobin, serum potassium, or vital signs, for clinical care, outcomes management, and research. The LOINC codes are not intended to transmit all possible information about a test or observation. They are only intended to identify the test result or clinical observation. http://www.regenstrief.org/LOINC/LOINC.htm


Type: ValueSet
Id: v3-LoincDocumentOntologyInternational
Web: ValueSet-v3-LoincDocumentOntologyInternational.html
Url: http://terminology.hl7.org/ValueSet/v3-LoincDocumentOntologyInternational
Version: 3.0.0
Status: active
Date: 2014-03-14
Name: LoincDocumentOntologyInternational
Title: LoincDocumentOntologyInternational
Experimental: false
Description:
The LOINC Document Ontology constrained for usage in the Universal Realm by removal of "regional" Document Types such as the "VA Compensation and Pension" codes.


Type: ValueSet
Id: v3-LotionDrugForm
Web: ValueSet-v3-LotionDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-LotionDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: LotionDrugForm
Title: LotionDrugForm
Experimental: false
Description:
The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin.


Type: ValueSet
Id: v3-ManagedCarePolicy
Web: ValueSet-v3-ManagedCarePolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ManagedCarePolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ManagedCarePolicy
Title: ManagedCarePolicy
Experimental: false
Description:
**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 by the medical profession to be cost effective, also known as medical practice guidelines. Providers are typically reimbursed for covered services by a capitated amount on a per member per month basis that may reflect difference in the health status and level of services anticipated to be needed by the member.


Type: ValueSet
Id: v3-ManagedParticipationStatusNormal
Web: ValueSet-v3-ManagedParticipationStatusNormal.html
Url: http://terminology.hl7.org/ValueSet/v3-ManagedParticipationStatusNormal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ManagedParticipationStatusNormal
Title: ManagedParticipationStatusNormal
Experimental: false
Description:
The 'typical' state. Excludes "nullified" which represents the termination state of a participation instance that was created in error.


Type: ValueSet
Id: v3-ManufacturerModelNameExample
Web: ValueSet-v3-ManufacturerModelNameExample.html
Url: http://terminology.hl7.org/ValueSet/v3-ManufacturerModelNameExample
Version: 2.0.0
Status: active
Date: 2022-10-11
Name: ManufacturerModelNameExample
Title: Manufacturer Model Name Example
Experimental: true
Description:
An example value set representing the ManufacturerModelName concept domain used  to convey a coded name for the software used to author content.


Type: ValueSet
Id: v3-MaritalStatus
Web: ValueSet-v3-MaritalStatus.html
Url: http://terminology.hl7.org/ValueSet/v3-MaritalStatus
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MaritalStatus
Title: MaritalStatus
Experimental: false
Description:
The domestic partnership status of a person.

*Example:*Married, separated, divorced, widowed, common-law marriage.


Type: ValueSet
Id: v3-MaterialDangerInfectious
Web: ValueSet-v3-MaterialDangerInfectious.html
Url: http://terminology.hl7.org/ValueSet/v3-MaterialDangerInfectious
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MaterialDangerInfectious
Title: MaterialDangerInfectious
Experimental: false
Description:
Material known to be infectious with human pathogenic microorganisms. Those who handle this material must take precautions for their protection.


Type: ValueSet
Id: v3-MaterialDangerInflammable
Web: ValueSet-v3-MaterialDangerInflammable.html
Url: http://terminology.hl7.org/ValueSet/v3-MaterialDangerInflammable
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MaterialDangerInflammable
Title: MaterialDangerInflammable
Experimental: false
Description:
Material is highly inflammable and in certain mixtures (with air) may lead to explosions. Keep away from fire, sparks and excessive heat.


Type: ValueSet
Id: v3-MedicalDevice
Web: ValueSet-v3-MedicalDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-MedicalDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MedicalDevice
Title: MedicalDevice
Experimental: false
Description:
A device with direct or indirect therapeutic purpose. Values for EntityCode when EntityClass = "DEV"


Type: ValueSet
Id: v3-MedicationGeneralizationRoleType
Web: ValueSet-v3-MedicationGeneralizationRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-MedicationGeneralizationRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MedicationGeneralizationRoleType
Title: MedicationGeneralizationRoleType
Experimental: false
Description:
Identifies the specific hierarchical relationship between the playing and scoping medications.

*Examples:* Generic, Generic Formulation, Therapeutic Class, etc.


Type: ValueSet
Id: v3-MedicationOrderReleaseReasonCode
Web: ValueSet-v3-MedicationOrderReleaseReasonCode.html
Url: http://terminology.hl7.org/ValueSet/v3-MedicationOrderReleaseReasonCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MedicationOrderReleaseReasonCode
Title: MedicationOrderReleaseReasonCode
Experimental: false
Description:
**Definition:**A collection of concepts that indicate why the prescription should be released from suspended state.


Type: ValueSet
Id: v3-MemberRoleType
Web: ValueSet-v3-MemberRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-MemberRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MemberRoleType
Title: MemberRoleType
Experimental: false
Description:
A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClassMember.


Type: ValueSet
Id: v3-MessageWaitingPriority
Web: ValueSet-v3-MessageWaitingPriority.html
Url: http://terminology.hl7.org/ValueSet/v3-MessageWaitingPriority
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MessageWaitingPriority
Title: MessageWaitingPriority
Experimental: false
Description:
Indicates the highest importance level of the set of messages the acknowledging application has waiting on a queue for the receiving application.

*Discussion:* These messages would need to be retrieved via a query. This facilitates receiving applications that cannot receive unsolicited messages (i.e. polling). The specific code specified identifies how important the most important waiting message is (and may govern how soon the receiving application is required to poll for the message).

Priority may be used by local agreement to determine the timeframe in which the receiving application is expected to retrieve the messages from the queue.


Type: ValueSet
Id: v3-MilitaryRoleType
Web: ValueSet-v3-MilitaryRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-MilitaryRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MilitaryRoleType
Title: MilitaryRoleType
Experimental: false
Description:
**Definition:** A person playing the role of program eligible under a program based on military status.

**Discussion:** This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria


Type: ValueSet
Id: v3-MultiUseContainerEntityType
Web: ValueSet-v3-MultiUseContainerEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-MultiUseContainerEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: MultiUseContainerEntityType
Title: MultiUseContainerEntityType
Experimental: false
Description:
A container intended to contain sufficient material for more than one use. (I.e. Material is intended to be removed from the container at more than one discrete time period.)


Type: ValueSet
Id: v3-NUCCProviderCodes
Web: ValueSet-v3-NUCCProviderCodes.html
Url: http://terminology.hl7.org/ValueSet/v3-NUCCProviderCodes
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NUCCProviderCodes
Title: NUCCProviderCodes
Experimental: false
Description:
In the absence of an all-encompassing Provider Classification System, both X12N and the National Provider System Workgroup from the Centers for Medicare and Medicaid Services (CMS) commenced work on identifying and coding an external provider table that would be able to codify provider type and provider area of specialization for all medical related providers. CMS' intent was to provide a single coding structure to support work on the National Provider System, while X12N needed a single common table for trading partner use. The two projects worked independently to some extent until April 1996 when the lists were coordinated and a single taxonomy was proposed. A sub-group of the X12N TG2 WG 15 was charged with resolving differences in the two proposed taxonomies. Their work resulted in a single taxonomy that both CMS and members of X12N found meaningful, easy to use, and functional for electronic transactions.

The sub-group initially started with the CMS draft taxonomy. This list incorporated all types of providers associated with medical care in various ways. Many of the providers listed, such as technologists or technicians, support or repair equipment/machinery. A number of the providers offer medical services, in concert with others, and do not or cannot bill independently for their portion. The amount of research to validate and classify all providers using the proposed hierarchical structure was enormous. The X12N sub-group focused on medical providers who are licensed practitioners, those who bill for health-related services rendered, and those who appeared on the Medicare CMS Provider Specialty listing. This included providers who were licensed to practice medicine via state licensure agencies. In addition, a very broad definition of "areas of specialization" was used, which included nationally recognized specialties, provider self-designated specialties, areas of practice focus, and any request by any agency or trading partner submitted before the first taxonomy release. This level of detail captured specialty information in categories detailed enough to support those trading credentialing information, yet broad enough to support those wishing to trade directory level specialization information.

In 2001, ANSI ASC X12N asked the NUCC to become the official maintainer of the Health Care Provider Taxonomy List. The NUCC has a formal operating protocol and its membership includes representation from key provider and payer organizations, as well as state and federal agencies, standard development organizations and the National Uniform Billing Committee (NUBC). Criteria for membership includes a national scope and representation of a unique constituency affected by health care electronic commerce, with an emphasis on maintaining a provider/payer balance.


Type: ValueSet
Id: v3-NationEntityType
Web: ValueSet-v3-NationEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-NationEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NationEntityType
Title: NationEntityType
Experimental: false
Description:
Codes identifying nation states. Allows for finer grained specification of Entity with classcode <= NAT

*Example:*ISO3166 country codes.


Type: ValueSet
Id: v3-NativeEntityAlaska
Web: ValueSet-v3-NativeEntityAlaska.html
Url: http://terminology.hl7.org/ValueSet/v3-NativeEntityAlaska
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NativeEntityAlaska
Title: NativeEntityAlaska
Experimental: false
Description:
NATIVE ENTITIES WITHIN THE STATE OF ALASKA RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS


Type: ValueSet
Id: v3-NieceNephew
Web: ValueSet-v3-NieceNephew.html
Url: http://terminology.hl7.org/ValueSet/v3-NieceNephew
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NieceNephew
Title: NieceNephew
Experimental: false
Description:
The player of the role is a child of scoping person's brother or sister or of the brother or sister of the scoping person's spouse.


Type: ValueSet
Id: v3-NoInformation
Web: ValueSet-v3-NoInformation.html
Url: http://terminology.hl7.org/ValueSet/v3-NoInformation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NoInformation
Title: NoInformation
Experimental: false
Description:
**Description:**The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value.


Type: ValueSet
Id: v3-NonRigidContainerEntityType
Web: ValueSet-v3-NonRigidContainerEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-NonRigidContainerEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: NonRigidContainerEntityType
Title: NonRigidContainerEntityType
Experimental: false
Description:
A container having dimensions that adjust somewhat based on the amount and shape of the material placed within it.


Type: ValueSet
Id: v3-ObligationPolicy
Web: ValueSet-v3-ObligationPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-ObligationPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObligationPolicy
Title: ObligationPolicy
Experimental: false
Description:
Conveys the mandated workflow action that an information custodian, receiver, or user must perform.

**Examples:**

 *  encrypt

*Usage Note:* Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.


Type: ValueSet
Id: v3-ObservationActContextAgeGroupType
Web: ValueSet-v3-ObservationActContextAgeGroupType.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationActContextAgeGroupType
Version: 3.0.0
Status: active
Date: 2010-03-16
Name: ObservationActContextAgeGroupType
Title: ObservationActContextAgeGroupType
Experimental: false
Description:
Identifies a type of observation that captures the age of a person in terms of age group concept codes.


Type: ValueSet
Id: v3-ObservationActContextAgeType
Web: ValueSet-v3-ObservationActContextAgeType.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationActContextAgeType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationActContextAgeType
Title: ObservationActContextAgeType
Experimental: false
Description:
**Definition:**The ways the age of an entity involved in an act can be measured, calculated or otherwise expressed in order to provide context for another act.


Type: ValueSet
Id: v3-ObservationAssetValue
Web: ValueSet-v3-ObservationAssetValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationAssetValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationAssetValue
Title: ObservationAssetValue
Experimental: false
Description:
Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program.


Type: ValueSet
Id: v3-ObservationCategory
Web: ValueSet-v3-ObservationCategory.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationCategory
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationCategory
Title: ObservationCategory
Experimental: false
Description:
High level observation categories for the general type of observation being made.

*Steward:* OO WG


Type: ValueSet
Id: v3-ObservationDetectedIssueCode
Web: ValueSet-v3-ObservationDetectedIssueCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationDetectedIssueCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationDetectedIssueCode
Title: ObservationDetectedIssueCode
Experimental: false
Description:
Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient


Type: ValueSet
Id: v3-ObservationEligibilityIndicatorValue
Web: ValueSet-v3-ObservationEligibilityIndicatorValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationEligibilityIndicatorValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationEligibilityIndicatorValue
Title: ObservationEligibilityIndicatorValue
Experimental: false
Description:
Code specifying eligibility indicators used to assess or establish eligibility for coverage under a policy or program eligibility status, e.g., certificates of creditable coverage; student enrollment; adoption, marriage or birth certificate.


Type: ValueSet
Id: v3-ObservationHealthStatusValue
Web: ValueSet-v3-ObservationHealthStatusValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationHealthStatusValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationHealthStatusValue
Title: ObservationHealthStatusValue
Experimental: false
Description:
Code specifying non-clinical indicators related to health status used to assess or establish eligibility for coverage under a policy or program, e.g., pregnancy, disability, drug use, mental health issues.


Type: ValueSet
Id: v3-ObservationInterpretation
Web: ValueSet-v3-ObservationInterpretation.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretation
Title: ObservationInterpretation
Experimental: false
Description:
One or more codes providing a rough qualitative interpretation of the observation,such as "normal" / "abnormal", "low" / "high", "better" / "worse", "resistant" / "susceptible", "expected" / "not expected". The value set is intended to be for ANY use where coded representation of an interpretation is needed.

*Usage Note:* This is being communicated in v2.x in OBX-8, in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used.


Type: ValueSet
Id: v3-ObservationInterpretationChange
Web: ValueSet-v3-ObservationInterpretationChange.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationChange
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationChange
Title: ObservationInterpretationChange
Experimental: false
Description:
Interpretations of change of quantity and/or severity, such as "better", "worse", "increased", etc. At most one of B or W and one of U or D allowed.


Type: ValueSet
Id: v3-ObservationInterpretationDetected
Web: ValueSet-v3-ObservationInterpretationDetected.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationDetected
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationDetected
Title: ObservationInterpretationDetected
Experimental: false
Description:
Interpretations of the presence or absence of a component / analyte or organism in a test or of a sign in a clinical observation. In keeping with laboratory data processing practice, these concepts provide a categorical interpretation of the "meaning" of the quantitative value for the same observation.


Type: ValueSet
Id: v3-ObservationInterpretationExceptions
Web: ValueSet-v3-ObservationInterpretationExceptions.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationExceptions
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationExceptions
Title: ObservationInterpretationExceptions
Experimental: false
Description:
Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity.


Type: ValueSet
Id: v3-ObservationInterpretationExpectation
Web: ValueSet-v3-ObservationInterpretationExpectation.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationExpectation
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationInterpretationExpectation
Title: ObservationInterpretationExpectation
Experimental: false
Description:
Observation interpretation codes for expected results based on additional information (contraindicators) about the patient's situation.


Type: ValueSet
Id: v3-ObservationInterpretationNormality
Web: ValueSet-v3-ObservationInterpretationNormality.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationNormality
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationNormality
Title: ObservationInterpretationNormality
Experimental: false
Description:
Interpretation of normality or degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed.


Type: ValueSet
Id: v3-ObservationInterpretationNormalityAbnormal
Web: ValueSet-v3-ObservationInterpretationNormalityAbnormal.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationNormalityAbnormal
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationNormalityAbnormal
Title: ObservationInterpretationNormalityAbnormal
Experimental: false
Description:
Interpretation of degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed.


Type: ValueSet
Id: v3-ObservationInterpretationNormalityCriticallyAbnormal
Web: ValueSet-v3-ObservationInterpretationNormalityCriticallyAbnormal.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationNormalityCriticallyAbnormal
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: ObservationInterpretationNormalityCriticallyAbnormal
Title: ObservationInterpretationNormalityCriticallyAbnormal
Experimental: false
Description:
Interpretation of a critical (or "alert") degree of abnormality. Concepts in this category are mutually exclusive, i.e., at most one is allowed.


Type: ValueSet
Id: v3-ObservationInterpretationNormalityHigh
Web: ValueSet-v3-ObservationInterpretationNormalityHigh.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationNormalityHigh
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationNormalityHigh
Title: ObservationInterpretationNormalityHigh
Experimental: false
Description:
Interpretation for a quantitative observation of degree of abnormality (including critical or "alert" level) above the upper limit of the reference range.


Type: ValueSet
Id: v3-ObservationInterpretationNormalityLow
Web: ValueSet-v3-ObservationInterpretationNormalityLow.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationNormalityLow
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationNormalityLow
Title: ObservationInterpretationNormalityLow
Experimental: false
Description:
Interpretation for a quantitative observation of degree of abnormality (including critical or "alert" level) below the lower limit of the reference range.


Type: ValueSet
Id: v3-ObservationInterpretationOustsideThreshold
Web: ValueSet-v3-ObservationInterpretationOustsideThreshold.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationOustsideThreshold
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationOustsideThreshold
Title: ObservationInterpretationOustsideThreshold
Experimental: false
Description:
The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.

**Example:** A positive result on a Hepatitis screening test.

*Open Issue:* We are not deprecating this value set at this time, but instead are leaving open the consideration of deprecation in the future. \[Note: The concepts included in this value set have also been suggested for future deprecation, and there are no associated concept subdomains or bindings. Note also that the name of the value set appears to have a typo in it from the old cycle when it was originally added.\]


Type: ValueSet
Id: v3-ObservationInterpretationProtocolInclusion
Web: ValueSet-v3-ObservationInterpretationProtocolInclusion.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationProtocolInclusion
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationProtocolInclusion
Title: ObservationInterpretationProtocolInclusion
Experimental: false
Description:
The observation/test result is interpreted as being outside the inclusion range for a particular protocol within which the result is being reported.

**Example:** A positive result on a Hepatitis screening test.

*Open Issue:* We are not deprecating this value set at this time, but instead are leaving open the consideration of deprecation in the future. \[Note: The concepts included in this value set have also been suggested for future deprecation, and there are no associated concept subdomains or bindings.\]


Type: ValueSet
Id: v3-ObservationInterpretationSusceptibility
Web: ValueSet-v3-ObservationInterpretationSusceptibility.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationInterpretationSusceptibility
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationInterpretationSusceptibility
Title: ObservationInterpretationSusceptibility
Experimental: false
Description:
Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed.


Type: ValueSet
Id: v3-ObservationIssueTriggerCodedObservationType
Web: ValueSet-v3-ObservationIssueTriggerCodedObservationType.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationIssueTriggerCodedObservationType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationIssueTriggerCodedObservationType
Title: ObservationIssueTriggerCodedObservationType
Experimental: false
Description:
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.


Type: ValueSet
Id: v3-ObservationLivingDependencyValue
Web: ValueSet-v3-ObservationLivingDependencyValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationLivingDependencyValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationLivingDependencyValue
Title: ObservationLivingDependencyValue
Experimental: false
Description:
Continued living in private residence requires functional and health care assistance from spouse or life partner.


Type: ValueSet
Id: v3-ObservationLivingExpenseValue
Web: ValueSet-v3-ObservationLivingExpenseValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationLivingExpenseValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationLivingExpenseValue
Title: ObservationLivingExpenseValue
Experimental: false
Description:
Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program.


Type: ValueSet
Id: v3-ObservationMeasureCountableItems
Web: ValueSet-v3-ObservationMeasureCountableItems.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationMeasureCountableItems
Version: 3.0.0
Status: active
Date: 2010-03-22
Name: ObservationMeasureCountableItems
Title: ObservationMeasureCountableItems
Experimental: false
Description:
A collection of items that can be counted by a quality measure (e.g., patients, encounters, procedures, etc.) for Observation.value used in the HQMF R2 MeasureAttribute class.


Type: ValueSet
Id: v3-ObservationMethod
Web: ValueSet-v3-ObservationMethod.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationMethod
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationMethod
Title: ObservationMethod
Experimental: false
Description:
A code that provides additional detail about the means or technique used to ascertain the observation.

*Examples:* Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc.

*Constraints:* In all observations the method is already partially specified by the Act.code. In this case, the methodCode NEED NOT be used at all. The methodCode MAY still be used to identify this method more clearly in addition to what is implied from the Act.code. However, an information consumer system or process SHOULD NOT depend on this methodCode information for method detail that is implied by the Act.code.

If the methodCode is used to express method detail that is also implied by the Act.code, the methodCode MUST NOT be in conflict with the implied method of the Act.code.


Type: ValueSet
Id: v3-ObservationMethodAggregate
Web: ValueSet-v3-ObservationMethodAggregate.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationMethodAggregate
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationMethodAggregate
Title: ObservationMethodAggregate
Experimental: false
Description:
A set of codes that defines how a set of values are summarized in an aggregated computation, for use with sets of values do describe which aggregated statistic functions are to be applied (e.g., average, mode, min, max, standard deviation, variance).


Type: ValueSet
Id: v3-ObservationNonAllergyIntoleranceType
Web: ValueSet-v3-ObservationNonAllergyIntoleranceType.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationNonAllergyIntoleranceType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationNonAllergyIntoleranceType
Title: ObservationNonAllergyIntoleranceType
Experimental: false
Description:
Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure


Type: ValueSet
Id: v3-ObservationSocioEconomicStatusValue
Web: ValueSet-v3-ObservationSocioEconomicStatusValue.html
Url: http://terminology.hl7.org/ValueSet/v3-ObservationSocioEconomicStatusValue
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ObservationSocioEconomicStatusValue
Title: ObservationSocioEconomicStatusValue
Experimental: false
Description:
Code specifying observations or indicators related to socio-economic status used to assess to assess for services, e.g., discharge planning, or to establish eligibility for coverage under a policy or program.


Type: ValueSet
Id: v3-OilDrugForm
Web: ValueSet-v3-OilDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-OilDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: OilDrugForm
Title: OilDrugForm
Experimental: false
Description:
An unctuous, combustible substance which is liquid, or easily liquefiable, on warming, and is soluble in ether but insoluble in water. Such substances, depending on their origin, are classified as animal, mineral, or vegetable oils.


Type: ValueSet
Id: v3-Other
Web: ValueSet-v3-Other.html
Url: http://terminology.hl7.org/ValueSet/v3-Other
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Other
Title: Other
Experimental: false
Description:
The actual value is not an element in the value domain of a variable. (e.g., concept not provided by required code system).


Type: ValueSet
Id: v3-OverriderParticipationFunction
Web: ValueSet-v3-OverriderParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-OverriderParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: OverriderParticipationFunction
Title: OverriderParticipationFunction
Experimental: false
Description:
This code is used to specify the exact function an actor is authorized to have in authoring a consent override.


Type: ValueSet
Id: v3-Parent
Web: ValueSet-v3-Parent.html
Url: http://terminology.hl7.org/ValueSet/v3-Parent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Parent
Title: Parent
Experimental: false
Description:
one that begets or brings forth offspring or a person who brings up and cares for another (Webster's Collegiate Dictionary)


Type: ValueSet
Id: v3-ParticipationAncillary
Web: ValueSet-v3-ParticipationAncillary.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationAncillary
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationAncillary
Title: ParticipationAncillary
Experimental: false
Description:
Participations related, but not primary to an act. The Referring, Admitting, and Discharging practitioners must be the same person as those authoring the ControlAct event for their respective trigger events.


Type: ValueSet
Id: v3-ParticipationAttender
Web: ValueSet-v3-ParticipationAttender.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationAttender
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationAttender
Title: ParticipationAttender
Experimental: false
Description:
The practitioner that has responsibility for overseeing a patient's care during a patient encounter.


Type: ValueSet
Id: v3-ParticipationAuthenticator
Web: ValueSet-v3-ParticipationAuthenticator.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationAuthenticator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationAuthenticator
Title: ParticipationAuthenticator
Experimental: false
Description:
A verifier who attests to the accuracy of an act, but who does not have privileges to legally authenticate the act. An example would be a resident physician who sees a patient and dictates a note, then later signs it. Their signature constitutes an authentication.


Type: ValueSet
Id: v3-ParticipationAuthorOriginator
Web: ValueSet-v3-ParticipationAuthorOriginator.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationAuthorOriginator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationAuthorOriginator
Title: ParticipationAuthorOriginator
Experimental: false
Description:
**Definition:** A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.

**Example:** the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship.

Examples of such policies might include:

 *  The author and anyone they explicitly delegate may update the report;
 *  All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;

A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party.


Type: ValueSet
Id: v3-ParticipationBeneficiary
Web: ValueSet-v3-ParticipationBeneficiary.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationBeneficiary
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationBeneficiary
Title: ParticipationBeneficiary
Experimental: false
Description:
Target on behalf of whom the service happens, but that is not necessarily present in the service. Can occur together with direct target to indicate that a target is both, as in the case where the patient is the indirect beneficiary of a service rendered to a family member, e.g. counseling or given home care instructions. This concept includes a participant, such as a covered party, who derives benefits from a service act covered by a coverage act.

Note that the semantic role of the intended recipient who benefits from the happening denoted by the verb in the clause. Thus, a patient who has no coverage under a policy or program may be a beneficiary of a health service while not being the beneficiary of coverage for that service.


Type: ValueSet
Id: v3-ParticipationCallbackContact
Web: ValueSet-v3-ParticipationCallbackContact.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationCallbackContact
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationCallbackContact
Title: ParticipationCallbackContact
Experimental: false
Description:
A person or organization who should be contacted for follow-up questions about the act in place of the author.


Type: ValueSet
Id: v3-ParticipationCausativeAgent
Web: ValueSet-v3-ParticipationCausativeAgent.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationCausativeAgent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationCausativeAgent
Title: ParticipationCausativeAgent
Experimental: false
Description:
Definition: A factor, such as a microorganism, chemical substance, or form of radiation, whose presence, excessive presence, or (in deficiency diseases) relative absence is essential, in whole or in part, for the occurrence of a condition.

Constraint: The use of this participation is limited to observations.


Type: ValueSet
Id: v3-ParticipationCoverageTarget
Web: ValueSet-v3-ParticipationCoverageTarget.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationCoverageTarget
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationCoverageTarget
Title: ParticipationCoverageTarget
Experimental: false
Description:
The target participation for an individual in a health care coverage act in which the target role is either the policy holder of the coverage, or a covered party under the coverage.


Type: ValueSet
Id: v3-ParticipationCustodian
Web: ValueSet-v3-ParticipationCustodian.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationCustodian
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationCustodian
Title: ParticipationCustodian
Experimental: false
Description:
An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.).


Type: ValueSet
Id: v3-ParticipationDataEntryPerson
Web: ValueSet-v3-ParticipationDataEntryPerson.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationDataEntryPerson
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationDataEntryPerson
Title: ParticipationDataEntryPerson
Experimental: false
Description:
A person entering the data into the originating system. The data entry person is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text.


Type: ValueSet
Id: v3-ParticipationDestination
Web: ValueSet-v3-ParticipationDestination.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationDestination
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationDestination
Title: ParticipationDestination
Experimental: false
Description:
The destination for services. May be a static building (or room therein) or a movable facility (e.g., ship).


Type: ValueSet
Id: v3-ParticipationDonor
Web: ValueSet-v3-ParticipationDonor.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationDonor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationDonor
Title: ParticipationDonor
Experimental: false
Description:
In some organ transplantation services and rarely in transfusion services a donor will be a target participant in the service. However, in most cases transplantation is decomposed in three services: explantation, transport, and implantation. The identity of the donor (recipient) is often irrelevant for the explantation (implantation) service.


Type: ValueSet
Id: v3-ParticipationExposureagent
Web: ValueSet-v3-ParticipationExposureagent.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationExposureagent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationExposureagent
Title: ParticipationExposureagent
Experimental: false
Description:
**Description:** The entity playing the associated role is the physical (including energy), chemical or biological substance that is participating in the exposure. For example in communicable diseases, the associated playing entity is the disease causing pathogen.


Type: ValueSet
Id: v3-ParticipationExposureparticipation
Web: ValueSet-v3-ParticipationExposureparticipation.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationExposureparticipation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationExposureparticipation
Title: ParticipationExposureparticipation
Experimental: false
Description:
**Description:**Direct participation in an exposure act where it is unknown that the participant is the source or subject of the exposure. If the participant is known to be the contact of an exposure then the EXPTRGT participation type should be used. If the participant is known to be the source then the EXSRC participation type should be used.


Type: ValueSet
Id: v3-ParticipationGuarantorParty
Web: ValueSet-v3-ParticipationGuarantorParty.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationGuarantorParty
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationGuarantorParty
Title: ParticipationGuarantorParty
Experimental: false
Description:
The target person or organization contractually recognized by the issuer as a participant who has assumed fiscal responsibility for another personaTMs financial obligations by guaranteeing to pay for amounts owed to a particular account

*Example:*The subscriber of the patientaTMs health insurance policy signs a contract with the provider to be fiscally responsible for the patient billing account balance amount owed.


Type: ValueSet
Id: v3-ParticipationHolder
Web: ValueSet-v3-ParticipationHolder.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationHolder
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationHolder
Title: ParticipationHolder
Experimental: false
Description:
Participant who posses an instrument such as a financial contract (insurance policy) usually based on some agreement with the author.


Type: ValueSet
Id: v3-ParticipationIndirectTarget
Web: ValueSet-v3-ParticipationIndirectTarget.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationIndirectTarget
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationIndirectTarget
Title: ParticipationIndirectTarget
Experimental: false
Description:
Target that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act.


Type: ValueSet
Id: v3-ParticipationInformant
Web: ValueSet-v3-ParticipationInformant.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationInformant
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationInformant
Title: ParticipationInformant
Experimental: false
Description:
A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject.


Type: ValueSet
Id: v3-ParticipationInformationGenerator
Web: ValueSet-v3-ParticipationInformationGenerator.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationInformationGenerator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationInformationGenerator
Title: ParticipationInformationGenerator
Experimental: false
Description:
Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness).


Type: ValueSet
Id: v3-ParticipationInformationRecipient
Web: ValueSet-v3-ParticipationInformationRecipient.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationInformationRecipient
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationInformationRecipient
Title: ParticipationInformationRecipient
Experimental: false
Description:
A party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood." Rationale: this is a generalization of a too diverse family that the definition can't be any more specific, and the concept is abstract so one of the specializations should be used.


Type: ValueSet
Id: v3-ParticipationInformationTranscriber
Web: ValueSet-v3-ParticipationInformationTranscriber.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationInformationTranscriber
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationInformationTranscriber
Title: ParticipationInformationTranscriber
Experimental: false
Description:
An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.


Type: ValueSet
Id: v3-ParticipationLegalAuthenticator
Web: ValueSet-v3-ParticipationLegalAuthenticator.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationLegalAuthenticator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationLegalAuthenticator
Title: ParticipationLegalAuthenticator
Experimental: false
Description:
A verifier who legally authenticates the accuracy of an act. An example would be a staff physician who sees a patient and dictates a note, then later signs it. Their signature constitutes a legal authentication.


Type: ValueSet
Id: v3-ParticipationNon-reuseableDevice
Web: ValueSet-v3-ParticipationNon-reuseableDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationNon-reuseableDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationNonReuseableDevice
Title: ParticipationNon-reuseableDevice
Experimental: false
Description:
A device that changes ownership due to the service, e.g., a pacemaker, a prosthesis, an insulin injection equipment (pen), etc. Such material may need to be restocked after he service.


Type: ValueSet
Id: v3-ParticipationOrigin
Web: ValueSet-v3-ParticipationOrigin.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationOrigin
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationOrigin
Title: ParticipationOrigin
Experimental: false
Description:
The location of origin for services. May be a static building (or room therein) or a movable facility (e.g., ship).


Type: ValueSet
Id: v3-ParticipationParticipation
Web: ValueSet-v3-ParticipationParticipation.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationParticipation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationParticipation
Title: ParticipationParticipation
Experimental: false
Description:
Indicates that the target of the participation is involved in some manner in the act, but does not qualify how.

This should **not** be used except when no more specific participation type is known or when the participation type is further clarified elsewhere. It should not be used lightly, and should never be used as a "placeholder" when a more appropriate specific type does not yet exist.


Type: ValueSet
Id: v3-ParticipationPhysicalPerformer
Web: ValueSet-v3-ParticipationPhysicalPerformer.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationPhysicalPerformer
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationPhysicalPerformer
Title: ParticipationPhysicalPerformer
Experimental: false
Description:
A person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.


Type: ValueSet
Id: v3-ParticipationPrimaryInformationRecipient
Web: ValueSet-v3-ParticipationPrimaryInformationRecipient.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationPrimaryInformationRecipient
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationPrimaryInformationRecipient
Title: ParticipationPrimaryInformationRecipient
Experimental: false
Description:
Information recipient to whom an act statement is primarily directed. E.g., a primary care provider receiving a discharge letter from a hospitalist, a health department receiving information on a suspected case of infectious disease. Multiple of these participations may exist on the same act without requiring that recipients be ranked as primary vs. secondary.


Type: ValueSet
Id: v3-ParticipationProduct
Web: ValueSet-v3-ParticipationProduct.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationProduct
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationProduct
Title: ParticipationProduct
Experimental: false
Description:
A material target that is brought forth (produced) in the service (e.g., specimen in a specimen collection, access or drainage in a placement service, medication package in a dispense service). It doesn't matter whether the material produced had existence prior to the service, or whether it is created in the service (e.g., in supply services the product is taken from a stock).


Type: ValueSet
Id: v3-ParticipationRecordTarget
Web: ValueSet-v3-ParticipationRecordTarget.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationRecordTarget
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationRecordTarget
Title: ParticipationRecordTarget
Experimental: false
Description:
The record target indicates whose medical record holds the documentation of this act. This is especially important when the subject of a service is not the patient himself.


Type: ValueSet
Id: v3-ParticipationReferredBy
Web: ValueSet-v3-ParticipationReferredBy.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationReferredBy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationReferredBy
Title: ParticipationReferredBy
Experimental: false
Description:
A participant (e.g. provider) who has referred the subject of an act (e.g. patient).

Typically, a referred by participant will provide a report (e.g. referral).


Type: ValueSet
Id: v3-ParticipationReferrer
Web: ValueSet-v3-ParticipationReferrer.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationReferrer
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationReferrer
Title: ParticipationReferrer
Experimental: false
Description:
A person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.


Type: ValueSet
Id: v3-ParticipationRemote
Web: ValueSet-v3-ParticipationRemote.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationRemote
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationRemote
Title: ParticipationRemote
Experimental: false
Description:
Some services take place at multiple concurrent locations (e.g., telemedicine, telephone consultation). The location where the principal performing actor is located is taken as the primary location (LOC) while the other location(s) are considered "remote."


Type: ValueSet
Id: v3-ParticipationResponsibleParty
Web: ValueSet-v3-ParticipationResponsibleParty.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationResponsibleParty
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationResponsibleParty
Title: ParticipationResponsibleParty
Experimental: false
Description:
The person or organization that has primary responsibility for the act. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate, and the duty to review actions with the performing actor after the fact. This responsibility may be ethical, legal, contractual, fiscal, or fiduciary in nature.

*Example:* A person who is the head of a biochemical laboratory; a sponsor for a policy or government program.


Type: ValueSet
Id: v3-ParticipationReusableDevice
Web: ValueSet-v3-ParticipationReusableDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationReusableDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationReusableDevice
Title: ParticipationReusableDevice
Experimental: false
Description:
A device that does not change ownership due to the service, i.e., a surgical instrument or tool or an endoscope. The distinction between reuseable and non-reuseable must be made in order to know whether material must be re-stocked.


Type: ValueSet
Id: v3-ParticipationSecondaryPerformer
Web: ValueSet-v3-ParticipationSecondaryPerformer.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationSecondaryPerformer
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationSecondaryPerformer
Title: ParticipationSecondaryPerformer
Experimental: false
Description:
A person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be.


Type: ValueSet
Id: v3-ParticipationSignature
Web: ValueSet-v3-ParticipationSignature.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationSignature
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationSignature
Title: ParticipationSignature
Experimental: false
Description:
A code specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed.

*Examples:* A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)


Type: ValueSet
Id: v3-ParticipationSubset
Web: ValueSet-v3-ParticipationSubset.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationSubset
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationSubset
Title: ParticipationSubset
Experimental: false
Description:
Used to indicate that the participation is a filtered subset of the total participations of the same type owned by the Act.

Used when there is a need to limit the participations to the first, the last, the next or some other filtered subset.


Type: ValueSet
Id: v3-ParticipationTargetDevice
Web: ValueSet-v3-ParticipationTargetDevice.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTargetDevice
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTargetDevice
Title: ParticipationTargetDevice
Experimental: false
Description:
Something used in delivering the service without being substantially affected by the service (i.e. durable or inert with respect to that particular service.) Examples are: monitoring equipment, tools, but also access/drainage lines, prostheses, pace maker, etc.


Type: ValueSet
Id: v3-ParticipationTargetDirect
Web: ValueSet-v3-ParticipationTargetDirect.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTargetDirect
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTargetDirect
Title: ParticipationTargetDirect
Experimental: false
Description:
Target that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.).


Type: ValueSet
Id: v3-ParticipationTargetLocation
Web: ValueSet-v3-ParticipationTargetLocation.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTargetLocation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTargetLocation
Title: ParticipationTargetLocation
Experimental: false
Description:
The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.)


Type: ValueSet
Id: v3-ParticipationTargetSubject
Web: ValueSet-v3-ParticipationTargetSubject.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTargetSubject
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTargetSubject
Title: ParticipationTargetSubject
Experimental: false
Description:
The principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools for a service are not subjects. However, a device may be a subject of a maintenance service.


Type: ValueSet
Id: v3-ParticipationTracker
Web: ValueSet-v3-ParticipationTracker.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTracker
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTracker
Title: ParticipationTracker
Experimental: false
Description:
A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).


Type: ValueSet
Id: v3-ParticipationTypeCDASectionOverride
Web: ValueSet-v3-ParticipationTypeCDASectionOverride.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationTypeCDASectionOverride
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationTypeCDASectionOverride
Title: ParticipationTypeCDASectionOverride
Experimental: false
Description:
Identifies the set of participation types context that can be blocked (overridden) at the CDA section or sub-section level of a document.


Type: ValueSet
Id: v3-ParticipationUgentNotificationContact
Web: ValueSet-v3-ParticipationUgentNotificationContact.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationUgentNotificationContact
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationUgentNotificationContact
Title: ParticipationUgentNotificationContact
Experimental: false
Description:
An information recipient to notify for urgent matters about this Act. (e.g., in a laboratory order, critical results are being called by phone right away, this is the contact to call; or for an inpatient encounter, a next of kin to notify when the patient becomes critically ill).


Type: ValueSet
Id: v3-ParticipationVerifier
Web: ValueSet-v3-ParticipationVerifier.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationVerifier
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationVerifier
Title: ParticipationVerifier
Experimental: false
Description:
A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.


Type: ValueSet
Id: v3-ParticipationWitness
Web: ValueSet-v3-ParticipationWitness.html
Url: http://terminology.hl7.org/ValueSet/v3-ParticipationWitness
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ParticipationWitness
Title: ParticipationWitness
Experimental: false
Description:
Only with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.


Type: ValueSet
Id: v3-PastSubset
Web: ValueSet-v3-PastSubset.html
Url: http://terminology.hl7.org/ValueSet/v3-PastSubset
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PastSubset
Title: PastSubset
Experimental: false
Description:
An occurrence that occurred or was scheduled to occur in the past. An Act whose effective time is less than 'now'. ('now' is the time the instance is authored.)


Type: ValueSet
Id: v3-PatchDrugForm
Web: ValueSet-v3-PatchDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-PatchDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PatchDrugForm
Title: PatchDrugForm
Experimental: false
Description:
A drug delivery system that contains an adhesived backing and that permits its ingredients to diffuse from some portion of it (e.g., the backing itself, a reservoir, the adhesive, or some other component) into the body from the external site where it is applied.


Type: ValueSet
Id: v3-PayorParticipationFunction
Web: ValueSet-v3-PayorParticipationFunction.html
Url: http://terminology.hl7.org/ValueSet/v3-PayorParticipationFunction
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PayorParticipationFunction
Title: PayorParticipationFunction
Experimental: false
Description:
**Definition:** Set of codes indicating the manner in which payors participate in a policy or program.</


Type: ValueSet
Id: v3-PayorRoleType
Web: ValueSet-v3-PayorRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-PayorRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PayorRoleType
Title: PayorRoleType
Experimental: false
Description:
**Description:**PayorRoleType for a particular type of policy or program benefit package or plan where more detail about the coverage administration role of the Payor is required. The functions performed by a Payor qualified by a PayorRoleType may be specified by the PayorParticpationFunction value set.

**Examples:**A Payor that is a TPA may administer a managed care plan without underwriting the risk.


Type: ValueSet
Id: v3-PermanentDentition
Web: ValueSet-v3-PermanentDentition.html
Url: http://terminology.hl7.org/ValueSet/v3-PermanentDentition
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PermanentDentition
Title: PermanentDentition
Experimental: false
Description:
Permanent dentition, the natural teeth of adulthood that replace or are added to the deciduous teeth


Type: ValueSet
Id: v3-PersonalAndLegalRelationshipRoleType
Web: ValueSet-v3-PersonalAndLegalRelationshipRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-PersonalAndLegalRelationshipRoleType
Version: 3.0.0
Status: active
Date: 2023-06-02
Name: PersonalAndLegalRelationshipRoleType
Title: PersonalAndLegalRelationshipRoleType
Experimental: false
Description:
A â€˜personal and legalâ€™ relationship records the role of a person in relation to another person, or a person to himself or herself. This value set is to be used when recording relationships based on personal or family ties or through legal assignment of responsibility.


Type: ValueSet
Id: v3-PersonalRelationshipRoleType
Web: ValueSet-v3-PersonalRelationshipRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-PersonalRelationshipRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PersonalRelationshipRoleType
Title: PersonalRelationshipRoleType
Experimental: false
Description:
Types of personal relationships between two living subjects.

*Example:*Parent, sibling, unrelated friend, neighbor


Type: ValueSet
Id: v3-PharmacistHIPAA
Web: ValueSet-v3-PharmacistHIPAA.html
Url: http://terminology.hl7.org/ValueSet/v3-PharmacistHIPAA
Version: 4.0.0
Status: retired
Date: 2014-03-26
Name: PharmacistHIPAA
Title: PharmacistHIPAA
Experimental: false
Description:
An individual who is licensed to prepare and sell or dispense drugs and compounds and to make up prescriptions.


Type: ValueSet
Id: v3-PharmacySupplyRequestFulfillerRevisionRefusalReasonCode
Web: ValueSet-v3-PharmacySupplyRequestFulfillerRevisionRefusalReasonCode.html
Url: http://terminology.hl7.org/ValueSet/v3-PharmacySupplyRequestFulfillerRevisionRefusalReasonCode
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: PharmacySupplyRequestFulfillerRevisionRefusalReasonCode
Title: PharmacySupplyRequestFulfillerRevisionRefusalReasonCode
Experimental: false
Description:
**Definition:**Indicates why the request to transfer a prescription from one dispensing facility to another has been refused.


Type: ValueSet
Id: v3-PharmacySupplyRequestRenewalRefusalReasonCode
Web: ValueSet-v3-PharmacySupplyRequestRenewalRefusalReasonCode.html
Url: http://terminology.hl7.org/ValueSet/v3-PharmacySupplyRequestRenewalRefusalReasonCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PharmacySupplyRequestRenewalRefusalReasonCode
Title: PharmacySupplyRequestRenewalRefusalReasonCode
Experimental: false
Description:
**Definition:**A collection of concepts that identifies why a renewal prescription has been refused.


Type: ValueSet
Id: v3-PolicyOrProgramCoverageRoleType
Web: ValueSet-v3-PolicyOrProgramCoverageRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-PolicyOrProgramCoverageRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PolicyOrProgramCoverageRoleType
Title: PolicyOrProgramCoverageRoleType
Experimental: false
Description:
**Description:** A role recognized through the eligibility of an identified party for benefits covered under an insurance policy or a program based on meeting eligibility criteria.

Eligibility as a covered party may be conditioned on the party meeting criteria to qualify for coverage under a policy or program, which may be mandated by law. These criteria may be:

1.  The sole basis for coverage, e.g., being differently abled may qualify a person for disability coverage
2.  May more fully qualify a covered party role e.g, being differently abled may qualify an adult child as a dependent
3.  May impact the level of coverage for a covered party under a policy or program, e.g., being differently abled may qualify a program eligible for additional benefits.

**Discussion:** The Abstract Value Set "CoverageRoleType", which was developed for use in the Canadian realm "pre-coordinate" coverage roles with other roles that a covered party must play in order to be eligible for coverage, e.g., "handicapped dependent". These role.codes may only be used with COVPTY to avoid overlapping concepts that would result from using them to specify the specializations of COVPTY, e.g., the role.class DEPEN should not be used with the role.code family dependent because that relationship has overlapping concepts due to the role.code precoodination and is conveyed in FICO with the personal relationship role that has a PART role link to the covered party role. For the same reasons, the role.class DEPEN should not be used with the role.code HANDIC (handicapped dependent); the role.code DIFFABLE (differently abled) should be used instead.

In summary, the coded concepts in the Abstract Value Set "CoveredPartyRoleType" can be "post-coordinated" with the "RoleClassCoveredParty" Abstract Value Set. Decoupling these concepts is intended to support an expansive range of covered party concepts and their semantic comparability.


Type: ValueSet
Id: v3-PopulationInclusionObservationType
Web: ValueSet-v3-PopulationInclusionObservationType.html
Url: http://terminology.hl7.org/ValueSet/v3-PopulationInclusionObservationType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PopulationInclusionObservationType
Title: PopulationInclusionObservationType
Experimental: false
Description:
Observation types for specifying criteria used to assert that a subject is included in a particular population.


Type: ValueSet
Id: v3-PowderDrugForm
Web: ValueSet-v3-PowderDrugForm.html
Url: http://terminology.hl7.org/ValueSet/v3-PowderDrugForm
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PowderDrugForm
Title: PowderDrugForm
Experimental: false
Description:
An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use.


Type: ValueSet
Id: v3-PowerOfAttorney
Web: ValueSet-v3-PowerOfAttorney.html
Url: http://terminology.hl7.org/ValueSet/v3-PowerOfAttorney
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PowerOfAttorney
Title: PowerOfAttorney
Experimental: false
Description:
A relationship between two people in which one person authorizes another to act for him in a manner which is a legally binding upon the person giving such authority as if he or she personally were to do the acts.


Type: ValueSet
Id: v3-PrescriptionDispenseFilterCode
Web: ValueSet-v3-PrescriptionDispenseFilterCode.html
Url: http://terminology.hl7.org/ValueSet/v3-PrescriptionDispenseFilterCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PrescriptionDispenseFilterCode
Title: PrescriptionDispenseFilterCode
Experimental: false
Description:
A "helper" vocabulary used to construct complex query filters based on how and whether a prescription has been dispensed.


Type: ValueSet
Id: v3-PrivacyMark
Web: ValueSet-v3-PrivacyMark.html
Url: http://terminology.hl7.org/ValueSet/v3-PrivacyMark
Version: 3.0.0
Status: active
Date: 2019-03-20
Name: PrivacyMark
Title: PrivacyMark
Experimental: false
Description:
Codes used for human readable marks indicating, e.g., the level of confidentiality protection, an authorized compartment, the integrity, or the handling instruction required by applicable policy. Such markings must be displayed as directed by applicable policy on electronically rendered information content and any electronic transmittal envelope or container; or on hardcopy information and any physical transmittal envelope or container.

Purpose: Supports the selection of the entire PrivacyMark value set with head code for e.g., rules engine policy set purposes.


Type: ValueSet
Id: v3-ProgramEligibleCoveredPartyRoleType
Web: ValueSet-v3-ProgramEligibleCoveredPartyRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-ProgramEligibleCoveredPartyRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ProgramEligibleCoveredPartyRoleType
Title: ProgramEligibleCoveredPartyRoleType
Experimental: false
Description:
**Description:**A role recognized through the eligibility of a party to play a program eligible for benefits covered or provided under a program.


Type: ValueSet
Id: v3-ProvenanceEventCurrentState-AS
Web: ValueSet-v3-ProvenanceEventCurrentState-AS.html
Url: http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-AS
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ProvenanceEventCurrentStateAS
Title: ProvenanceEventCurrentState-AS
Experimental: false
Description:
Specifies the state change of a target Act, using ActStatus codes, from its previous state as a predecessor Act.

For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".


Type: ValueSet
Id: v3-ProvenanceEventCurrentState-DC
Web: ValueSet-v3-ProvenanceEventCurrentState-DC.html
Url: http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-DC
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ProvenanceEventCurrentStateDC
Title: ProvenanceEventCurrentState-DC
Experimental: false
Description:
Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act.

For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".


Type: ValueSet
Id: v3-ProvenanceEventCurrentState
Web: ValueSet-v3-ProvenanceEventCurrentState.html
Url: http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState
Version: 3.0.0
Status: active
Date: 2014-08-07
Name: ProvenanceEventCurrentState
Title: ProvenanceEventCurrentState
Experimental: false
Description:
Specifies the state change of a target Act, such as a document or an entry, from its previous state as a predecessor Act.

For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".


Type: ValueSet
Id: v3-PublicHealthcareProgram
Web: ValueSet-v3-PublicHealthcareProgram.html
Url: http://terminology.hl7.org/ValueSet/v3-PublicHealthcareProgram
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: PublicHealthcareProgram
Title: PublicHealthcareProgram
Experimental: false
Description:
**Definition:** A a public or governmental health program with 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. These programs are established by legislation with provisions for ongoing government oversight. Regulations mandate the structure of the program, the manner in which it is funded and administered, covered benefits, provider types, eligibility criteria and financial participation. A government agency may be charged with implementing the program in accordance to the regulation.

For example, A Canadian provincial or national health plan such as the BC MSP (British Columbia Medical Services Plan) OHIP (Ontario Health Insurance Plan), NHS (National Health Service). Examples of U.S. government funded health programs include those for maternity case management, behavioral health, and HIV-AIDs, such as the Ryan White program.


Type: ValueSet
Id: v3-QualityMeasureSectionType
Web: ValueSet-v3-QualityMeasureSectionType.html
Url: http://terminology.hl7.org/ValueSet/v3-QualityMeasureSectionType
Version: 3.0.0
Status: active
Date: 2014-03-14
Name: QualityMeasureSectionType
Title: QualityMeasureSectionType
Experimental: false
Description:
A type of document section within a health quality measure (aka eMeasure), used to cluster the various parts of the eMeasure into a more human navigable format.


Type: ValueSet
Id: v3-QualitySpecimenRoleType
Web: ValueSet-v3-QualitySpecimenRoleType.html
Url: http://terminology.hl7.org/ValueSet/v3-QualitySpecimenRoleType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: QualitySpecimenRoleType
Title: QualitySpecimenRoleType
Experimental: false
Description:
A specimen specifically used to verify the sensitivity, specificity, accuracy or other perfomance parameter of a diagnostic test.


Type: ValueSet
Id: v3-QueryRequestLimit
Web: ValueSet-v3-QueryRequestLimit.html
Url: http://terminology.hl7.org/ValueSet/v3-QueryRequestLimit
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: QueryRequestLimit
Title: QueryRequestLimit
Experimental: false
Description:
**Definition:** The number of matching instances (number of focal classes). The document header class is the focal class of a document, a record would therefore be equal to a document.


Type: ValueSet
Id: v3-Race
Web: ValueSet-v3-Race.html
Url: http://terminology.hl7.org/ValueSet/v3-Race
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: Race
Title: Race
Experimental: false
Description:
In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct in which an individual's own identification with one more race categories is preferred to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories.


Type: ValueSet
Id: v3-RadDiagTherPracticeSetting
Web: ValueSet-v3-RadDiagTherPracticeSetting.html
Url: http://terminology.hl7.org/ValueSet/v3-RadDiagTherPracticeSetting
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RadDiagTherPracticeSetting
Title: RadDiagTherPracticeSetting
Experimental: false
Description:
A practice setting where radiology services (diagnostic or therapeutic) are provided (X12N 261QR0200N)


Type: ValueSet
Id: v3-ReactionDetectedIssueCode
Web: ValueSet-v3-ReactionDetectedIssueCode.html
Url: http://terminology.hl7.org/ValueSet/v3-ReactionDetectedIssueCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ReactionDetectedIssueCode
Title: ReactionDetectedIssueCode
Experimental: false
Description:
Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product


Type: ValueSet
Id: v3-ReactivityObservationInterpretation
Web: ValueSet-v3-ReactivityObservationInterpretation.html
Url: http://terminology.hl7.org/ValueSet/v3-ReactivityObservationInterpretation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ReactivityObservationInterpretation
Title: ReactivityObservationInterpretation
Experimental: false
Description:
Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test.


Type: ValueSet
Id: v3-RefrainPolicy
Web: ValueSet-v3-RefrainPolicy.html
Url: http://terminology.hl7.org/ValueSet/v3-RefrainPolicy
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RefrainPolicy
Title: RefrainPolicy
Experimental: false
Description:
Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances.

**Examples:**

 *  prohibit redisclosure without consent directive


Type: ValueSet
Id: v3-RegulationPolicyActCode
Web: ValueSet-v3-RegulationPolicyActCode.html
Url: http://terminology.hl7.org/ValueSet/v3-RegulationPolicyActCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RegulationPolicyActCode
Title: RegulationPolicyActCode
Experimental: false
Description:
**Description:** A rule set by regulators of product that somehow constrain the use of products. Regulator may be any organization with a mandate to issue such rules, regardless of level, regional, country, state, and local (e.g., an institutional Pharmaceutical and Treatment Committee.)

**Examples:**

 *  Prescription Only
 *  Controlled Substance Schedule II
 *  Standard of Practice


Type: ValueSet
Id: v3-RelatedReactionDetectedIssueCode
Web: ValueSet-v3-RelatedReactionDetectedIssueCode.html
Url: http://terminology.hl7.org/ValueSet/v3-RelatedReactionDetectedIssueCode
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RelatedReactionDetectedIssueCode
Title: RelatedReactionDetectedIssueCode
Experimental: false
Description:
Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product.


Type: ValueSet
Id: v3-ResearchSubjectRoleBasis
Web: ValueSet-v3-ResearchSubjectRoleBasis.html
Url: http://terminology.hl7.org/ValueSet/v3-ResearchSubjectRoleBasis
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ResearchSubjectRoleBasis
Title: ResearchSubjectRoleBasis
Experimental: false
Description:
Specifies the administrative functionality within a formal experimental design for which the ResearchSubject role was established. Examples: screening - role is used for pre-enrollment evaluation portion of the design; enrolled - role is used for subjects admitted to the active treatment portion of the design.


Type: ValueSet
Id: v3-ResourceGroupEntityType
Web: ValueSet-v3-ResourceGroupEntityType.html
Url: http://terminology.hl7.org/ValueSet/v3-ResourceGroupEntityType
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: ResourceGroupEntityType
Title: ResourceGroupEntityType
Experimental: false
Description:
Codes to characterize a Resource Group using categories that typify its membership and/or function

.

*Example:* PractitionerGroup


Type: ValueSet
Id: v3-RoleClass
Web: ValueSet-v3-RoleClass.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClass
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClass
Title: RoleClass
Experimental: false
Description:
This table includes codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.

The role hierarchy stems from three core concepts, or abstract domains:

 *  **RoleClassOntological** is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.
 *  **RoleClassPartitive** collects roles in which the playing entity is in some sense a "part" of the scoping entity.
 *  **RoleClassAssociative** collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:
    
     *  **RoleClassPassive** which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.
     *  **RoleClassMutualRelationship** which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be *de facto* behavior. Thus, this sub-domain is further divided into:
        
         *  **RoleClassRelationshipFormal** in which the relationship is formally defined, frequently by a contract or agreement.
         *  **Personal relationship** which inks two people in a personal relationship.

The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept.


Type: ValueSet
Id: v3-RoleClassAccess
Web: ValueSet-v3-RoleClassAccess.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassAccess
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassAccess
Title: RoleClassAccess
Experimental: false
Description:
A role in which the playing entity (material) provides access to another entity. The principal use case is intravenous (or other bodily) access lines that preexist and need to be referred to for medication routing instructions.


Type: ValueSet
Id: v3-RoleClassActiveIngredient
Web: ValueSet-v3-RoleClassActiveIngredient.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassActiveIngredient
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassActiveIngredient
Title: RoleClassActiveIngredient
Experimental: false
Description:
A therapeutically active ingredient (player) in a mixture (scoper), where the mixture is typically a manufactured pharmaceutical.


Type: ValueSet
Id: v3-RoleClassActiveMoiety
Web: ValueSet-v3-RoleClassActiveMoiety.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassActiveMoiety
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassActiveMoiety
Title: RoleClassActiveMoiety
Experimental: false
Description:
The molecule or ion that is responsible for the intended pharmacological action of the drug substance, excluding those appended or associated parts of the molecule that make the molecule an ester, salt (including a salt with hydrogen or coordination bonds), or other noncovalent derivative (such as a complex, chelate, or clathrate).

Examples: heparin-sodium and heparin-potassium have the same active moiety, heparin; the active moiety of morphine-hydrochloride is morphine.


Type: ValueSet
Id: v3-RoleClassAdditive
Web: ValueSet-v3-RoleClassAdditive.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassAdditive
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassAdditive
Title: RoleClassAdditive
Experimental: false
Description:
An ingredient (player) that is added to a base (scoper), that amounts to a minor part of the overall mixture.


Type: ValueSet
Id: v3-RoleClassAffiliate
Web: ValueSet-v3-RoleClassAffiliate.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassAffiliate
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassAffiliate
Title: RoleClassAffiliate
Experimental: false
Description:
Player of the Affiliate role has a business/professional relationship with scoper. Player and scoper may be persons or organization. The Affiliate relationship does not imply membership in a group, nor does it exist for resource scheduling purposes.

*Example:* A healthcare provider is affiliated with another provider as a business associate.


Type: ValueSet
Id: v3-RoleClassAssignedEntity
Web: ValueSet-v3-RoleClassAssignedEntity.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassAssignedEntity
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassAssignedEntity
Title: RoleClassAssignedEntity
Experimental: false
Description:
An agent role in which the agent is an Entity acting in the employ of an organization. The focus is on functional role on behalf of the organization, unlike the Employee role where the focus is on the 'Human Resources' relationship between the employee and the organization.


Type: ValueSet
Id: v3-RoleClassBase
Web: ValueSet-v3-RoleClassBase.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassBase
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassBase
Title: RoleClassBase
Experimental: false
Description:
A base ingredient (player) is what comprises the major part of a mixture (scoper). E.g., Water in most i.v. solutions, or Vaseline in salves. Among all ingredients of a material, there should be only one base. A base substance can, in turn, be a mixture.


Type: ValueSet
Id: v3-RoleClassCaseSubject
Web: ValueSet-v3-RoleClassCaseSubject.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassCaseSubject
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassCaseSubject
Title: RoleClassCaseSubject
Experimental: false
Description:
A person, non-person living subject, or place that is the subject of an investigation related to a notifiable condition (health circumstance that is reportable within the applicable public health jurisdiction)


Type: ValueSet
Id: v3-RoleClassClaimant
Web: ValueSet-v3-RoleClassClaimant.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassClaimant
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassClaimant
Title: RoleClassClaimant
Experimental: false
Description:
**Description:** A role played by a party making a claim for coverage under a policy or program. A claimant must be either a person or organization, or a group of persons or organizations. A claimant is not a named insured or a program eligible.

**Discussion:** With respect to liability insurance such as property and casualty insurance, a claimant must file a claim requesting indemnification for a loss that the claimant considers covered under the policy of a named insured. The claims adjuster for the policy underwriter will review the claim to determine whether the loss meets the benefit coverage criteria under a policy, and base any indemnification or coverage payment on that review. If a third party is liable in whole or part for the loss, the underwriter may pursue third party liability recovery. A claimant may be involved in civil or criminal legal proceedings involving claims against a defendant party that is indemnified by an insurance policy or to protest the finding of a claims adjustor. With respect to life insurance, a beneficiary designated by a named insured becomes a claimant of the proceeds of coverage, as in the case of a life insurance policy. However, a claimant for coverage under life insurance is not necessarily a designated beneficiary.

**Note:** A claimant is not a named insured. However, a named insured may make a claim under a policy, e.g., an insured driver may make a claim for an injury under his or her comprehensive automobile insurance policy. Similarly, a program eligible may make a claim under program, e.g., an unemployed worker may claim benefits under an unemployment insurance program, but parties playing these covered party role classes are not, for purposes of this vocabulary and in an effort to clearly distinguish role classes, considered claimants.

In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that either a named insured or an individual insured has filed a claim for a loss. In the case of a program eligible, a role type code INJWKR (injured worker) subtypes the class to indicate that the covered party in a workers compensation program is an injured worker, and as such, has filed a "claim" under the program for benefits. Likewise, a covered role type code UNEMP (unemployed worker) subtypes the program eligible class to indicate that the covered party in an unemployment insurance program has filed a claim for unemployment benefits.

**Example:** A claimant under automobile policy that is not the named insured.


Type: ValueSet
Id: v3-RoleClassClinicalResearchInvestigator
Web: ValueSet-v3-RoleClassClinicalResearchInvestigator.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassClinicalResearchInvestigator
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassClinicalResearchInvestigator
Title: RoleClassClinicalResearchInvestigator
Experimental: false
Description:
A role played by a provider, always a person, who has agency authority from a Clinical Research Sponsor to direct the conduct of a clinical research trial or study on behalf of the sponsor.


Type: ValueSet
Id: v3-RoleClassClinicalResearchSponsor
Web: ValueSet-v3-RoleClassClinicalResearchSponsor.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassClinicalResearchSponsor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassClinicalResearchSponsor
Title: RoleClassClinicalResearchSponsor
Experimental: false
Description:
A role played by an entity, usually an organization, that is the sponsor of a clinical research trial or study. The sponsor commissions the study, bears the expenses, is responsible for satisfying all legal requirements concerning subject safety and privacy, and is generally responsible for collection, storage and analysis of the data generated during the trial. No scoper is necessary, as a clinical research sponsor undertakes the role on its own authority and declaration. Clinical research sponsors are usually educational or other research organizations, government agencies or biopharmaceutical companies.


Type: ValueSet
Id: v3-RoleClassCommissioningParty
Web: ValueSet-v3-RoleClassCommissioningParty.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassCommissioningParty
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassCommissioningParty
Title: RoleClassCommissioningParty
Experimental: false
Description:
An Entity that is authorized to issue or instantiate permissions, privileges, credentials or other formal/legal authorizations.


Type: ValueSet
Id: v3-RoleClassContact
Web: ValueSet-v3-RoleClassContact.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassContact
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassContact
Title: RoleClassContact
Experimental: false
Description:
A person or an organization (player) which provides or receives information regarding another entity (scoper). Examples; patient NOK and emergency contacts; guarantor contact; employer contact.


Type: ValueSet
Id: v3-RoleClassContent
Web: ValueSet-v3-RoleClassContent.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassContent
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassContent
Title: RoleClassContent
Experimental: false
Description:
Relates a material as the content (player) to a container (scoper). Unlike ingredients, the content and a container remain separate (not mixed) and the content can be removed from the container. A content is not part of an empty container.


Type: ValueSet
Id: v3-RoleClassCoverageSponsor
Web: ValueSet-v3-RoleClassCoverageSponsor.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassCoverageSponsor
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassCoverageSponsor
Title: RoleClassCoverageSponsor
Experimental: false
Description:
A role played by an entity, usually an organization that is the sponsor of an insurance plan or a health program. A sponsor is the party that is ultimately accountable for the coverage by employment contract or by law. A sponsor can be an employer, union, government agency, or association. Fully insured sponsors establish the terms of the plan and contract with health insurance plans to assume the risk and to administer the plan. Self-insured sponsors delegate coverage administration, but not risk, to third-party administrators. Program sponsors designate services to be covered in accordance with statute. Program sponsors may administer the coverage themselves, delegate coverage administration, but not risk to third-party administrators, or contract with health insurance plans to assume the risk and administrator a program. Sponsors qualify individuals who may become

1.  a policy holder of the plan;
2.  where the sponsor is the policy holder, who may become a subscriber or a dependent to a policy under the plan; or
3.  where the sponsor is a government agency, who may become program eligibles under a program.

The sponsor role may be further qualified by the SponsorRole.code. Entities playing the sponsor role may also play the role of a Coverage Administrator.

*Example:* An employer, union, government agency, or association.


Type: ValueSet
Id: v3-RoleClassCoveredParty
Web: ValueSet-v3-RoleClassCoveredParty.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassCoveredParty
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassCoveredParty
Title: RoleClassCoveredParty
Experimental: false
Description:
**Description:** A relationship between a party that receives benefit coverage under the terms of an insurance policy or program and the underwriter of the policy or program. The role is played by the party that receives benefit coverage under the terms of a particular insurance policy or program. The organization playing the underwriter of that policy or program is the scoping entity.

A covered party receives coverage under a policy because of some contractual or other relationship with the policy holder. In most cases, the policy holder has discretion over which parties may be covered under a policy, unless the policy holder assigns or is required by a court to assign this right.

A covered party receives coverage under a program by being determined eligible based on program eligibility criteria specified by the program sponsor.

**Discussion:** This reason for coverage is specified by use of a role type code from either of the abstract value sets beneath the PolicyOrProgramCoverageRoleType abstract value set.

The CoverageRoleType abstract value set can only be used when the role class is the concept code "covered party" (COVPTY) because this value set contains precoordinated coded concepts relating to coverage criteria that was developed for the Canadian realm. This is to avoid overlapping concepts, e.g., the DEPEN role.class cannot be used with the FAMDEP Role.code

The CoveredPartyRoleType abstract value set may be used with any of the covered party role class codes to support post coordination of coverage criteria. Where coverage under a policy depends on the concurrence of a policy holder, a relationship link with type code of indirect authority should be included using the policy holder role as the source, and the covered party role as the target.

**Note:** A particular policy may cover several parties, one of whom may be, but need not be, the policy holder. Thus the notion of covered party is a role that is distinct from that of the policy holder.

**Note:** The entity playing the role of covered party is an organization, a non-person living subject or a group of persons, the role class codes Subscriber and Dependent may not be used.


Type: ValueSet
Id: v3-RoleClassDedicatedServiceDeliveryLocation
Web: ValueSet-v3-RoleClassDedicatedServiceDeliveryLocation.html
Url: http://terminology.hl7.org/ValueSet/v3-RoleClassDedicatedServiceDeliveryLocation
Version: 3.0.0
Status: active
Date: 2014-03-26
Name: RoleClassDedicatedServiceDeliveryLocation
Title: RoleClassDedicatedServiceDeliveryLocation
Experimental: false
Description:
A role of a place (player) that is intended to house the provision of services. Scoper is the Entity (typically Organization) that provides these services. This is not synonymous with "ownership."


