This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Extension Definitions

These define constraints on FHIR data types that need to be complied with by conformant implementations

MIF concept relationship transitivity	Indicates whether the relationship always (transitive) or never (antitransitive) propagates such that if the association exists from A to B and from B to C that the relationship can be inferred to exist from A to C
MIF concept relationship is reflexivity	Indicates if the association always holds for a concept with itself (refexive), never holds for a concept with itself (irreflexive)
MIF concept relationship is navigable	Indicates whether the relationship is intended to be navigated when selecting a code
MIF concept relationship kind	Identifies a type of relationship between codes that is supported by this code system version
NamingSystem version	The business version associated with the Naming System
MIF concept relationship inverse name	Identifies the name of the relationship that references the inverse of the current relationship. Allows linking a relationship and its derived inverse.
MIF concept relationship symmetry	Indicates if the relationship always holds in the reverse direction as well (symetric), never holds in the reverse direction as well (antisymetric)
NamingSystem title	The human-readable descriptive name for the code or identifier system
MIF Associated concept property	Concept Properties that are associated with this Code System or Value Set Version

Terminology: Value Sets

These define sets of codes used by systems conforming with this implementation guide

chromosome-human	Chromosome number for human.
Special arrangements	This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.
Discharge disposition	This value set defines a set of codes that can be used to where the patient left the hospital.
USCLS Codes	This value set includes a smattering of USCLS codes.
StateChangeReason	Indicates why the state of the subject changed.
Coverage SelfPay Codes	This value set includes Coverage SelfPay codes.
Subscription Error Codes	Codes to represent subscription error details
QuestionnaireItemUsageMode	Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item.
ChargeItemCode	Example set of codes that can be used for billing purposes.
Medication knowledge characteristic codes	MedicationKnowledge Characteristic Codes
Example Diagnosis Related Group Codes	This value set includes example Diagnosis Related Group codes.
Service type	This value set defines an example set of codes of service-types.
Test script operation code	This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.
Validation-process	The primary process by which the target is validated
ResearchSubjectState	Indicates the progression of a study subject through a study.
Network Type Codes	This value set includes a smattering of Network type codes.
Immunization Funding Source	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example.
LibraryType	The type of knowledge asset this library contains.
AdjudicationError	This value set includes a smattering of adjudication codes.
Condition Clinical Status Codes	Preferred value set for Condition Clinical Status.
Claim Information Category Codes	This value set includes sample Information Category codes.
Missing Tooth Reason Codes	This value set includes sample Missing Tooth Reason codes.
Primary-source-type	Type of the validation primary source
MeasureType	The type of measure (includes codes from 2.16.840.1.113883.1.11.20368).
Audit Event Source Type	The type of process where the audit event originated from.
AlternativeCodeKind	Indicates the type of use for which the code is defined.
Validation-type	What the target is validated against
CommunicationNotDoneReason	Codes for the reason why a communication did not happen.
Goal category	Example codes for grouping goals to use for filtering or presentation.
GoalAcceptanceStatus	Codes indicating whether the goal has been accepted by a stakeholder.
Example Revenue Center Codes	This value set includes sample Revenue Center codes.
StatisticCertaintySubcomponentRating	The quality rating of the subcomponent of a quality of evidence rating.
Push-type-available	Type of alerts/updates the primary source can send
Forms	This value set includes a sample set of Forms codes.
Consent Scope Codes	This value set includes the four Consent scope codes.
ActionType	The type of action to be performed.
Process Priority Codes	This value set includes the financial processing priority codes.
Example Vision Prescription Product Codes	This value set includes a smattering of Prescription Product codes.
Goal priority	Indicates the level of importance associated with reaching or sustaining a goal.
Substance Category Codes	Substance category codes
Episode of care type	This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.
MeasureImprovementNotation	Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.
StatisticSynthesisType	Types of combining results from a body of evidence (eg. summary data meta-analysis).
Contract Signer Type Codes	This value set includes sample Contract Signer Type codes.
AdverseEventCausalityMethod	TODO.
Organization type	This example value set defines a set of codes that can be used to indicate a type of organization.
Appointment cancellation reason	This example value set defines a set of reasons for the cancellation of an appointment.
Risk Probability	Codes representing the likelihood of a particular outcome in a risk assessment.
ClaimPayeeResourceType	The type of Claim payee Resource.
StatisticStatisticType	The type of a specific statistic.
Example Diagnosis on Admission Codes	This value set includes example Diagnosis on Admission codes.
AllergyIntoleranceCertainty	Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.
FHIR Device Types	Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.
FamilyHistoryAbsentReason	Codes describing the reason why a family member's history is not available.
Medication request course of therapy codes	MedicationRequest Course of Therapy Codes
ReferralMethod	The methods of referral can be used when referring to a specific HealthCareService resource.
Reason Medication Given Codes	This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.
StandardsStatus	HL7 Ballot/Standards status of artifact.
GuideParameterCode	Code of parameter that is input to the guide.
QualityOfEvidenceRating	A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.
PayeeResourceType	The type of payee Resource.
CatalogType	The type of catalog.
Example Message Reason Codes	Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.
FHIRDeviceStatusReason	The availability status reason of the device.
SupplyRequestReason	The reason why the supply item was requested.
Flag Category	Example list of general categories for flagged issues. (Not complete or necessarily appropriate.)
Example Related Claim Relationship Codes	This value set includes sample Related Claim Relationship codes.
Adjudication Value Codes	This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc.
Encounter subject status	This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter
Admit source	This value set defines a set of codes that can be used to indicate from where the patient came in.
ConditionState	Enumeration indicating whether the condition is currently active, inactive, or has been resolved.
SubscriptionChannel Type Codes	Codes to represent subscription error details
Surface Codes	This value set includes a smattering of FDI tooth surface codes.
Claim Care Team Role Codes	This value set includes sample Claim Care Team Role codes.
SubscriptionTag	Tags to put on a resource after subscriptions have been sent.
ConformanceExpectation	Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.
Contact entity type	This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.
Location type	This example value set defines a set of codes that can be used to indicate the physical form of the Location.
Contract Term Type Codes	This value set includes sample Contract Term Type codes.
Test script profile destination type	This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript.
Encounter type	This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided.
CompositeMeasureScoring	The composite scoring method of the measure.
Service category	This value set defines an example set of codes that can be used to classify groupings of service-types/specialties.
Failure-action	The result if validation fails
CharacteristicMethod	The method used to determine the characteristic(s) of the variable.
ContractDataMeaning	How a resource reference is interpreted when evaluating contract offers.
Consent Action Codes	This value set includes sample Consent Action codes.
Condition Category Codes	Preferred value set for Condition Categories.
ResourceSecurityCategory	Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource.
Test script profile origin type	This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript.
Payment Status Codes	This value set includes a sample set of Payment Status codes.
Benefit cost applicability	Whether the cost applies to in-network or out-of-network providers.
MatchGrade	A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not.
Supply Type	This value sets refers to a Category of supply.
MedicationAdministrationLocation	Direction in which lists of possible answers should be displayed.
Medication dispense performer function codes	MedicationDispense Performer Function Codes
Oral Site Codes	This value set includes a smattering of FDI oral site codes.
MeasureScoring	The scoring type of the measure.
Consent PolicyRule Codes	This value set includes sample Regulatory consent policy types from the US and other regions.
Immunization Evaluation Dose Status codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example.
SubscriberPolicyholder Relationship Codes	This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).
Observation Reference Range Meaning Codes	This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population.
Validation-status	Status of the validation of the target against the primary source
Example Payment Type Codes	This value set includes example Payment Type codes.
RejectionCriterion	Criterion for rejection of the specimen by laboratory.
Contract Term Subtype Codes	This value set includes sample Contract Term SubType codes.
Coverage Class Codes	This value set includes Coverage Class codes.
Need	The frequency with which the target must be validated
Program	This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties.
AlternativeCodeKind	Indicates the type of use for which the code is defined.
Coverage Copay Type Codes	This value set includes sample Coverage Copayment Type codes.
CopyNumberEvent	Copy Number Event.
Example Claim SubType Codes	This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation.
MaxOccurs	Flags an element as having unlimited repetitions.
ConditionVerificationStatus	The verification status to support or decline the clinical status of the condition or diagnosis.
Basic Resource Types	This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts.
Example Procedure Type Codes	This value set includes example Procedure Type codes.
MeasureDataUsage	The intended usage for supplemental data elements in the measure.
Example Use Codes for List	Example use codes for the List resource - typical kinds of use.
Insurance plan type	This example value set defines a set of codes that can be used to indicate a type of insurance plan.
Example Diagnosis Type Codes	This value set includes example Diagnosis Type codes.
List Order Codes	Base values for the order of the items in a list resource.
StatisticStudyType	The type of study a statistic was derived from.
AdverseEventSeriousness	Overall seriousness of this event for the patient.
Exception Codes	This value set includes sample Exception codes.
AuditEventEntityRole	Code representing the role the entity played in the audit event.
StatisticCertaintySubcomponentType	The subcomponent classification of quality of evidence rating systems.
SubscriptionStatusAtEvent	A status code for the state of the Subscription.
StatisticsCode	The statistical operation parameter -"statistic" codes.
Structure Definition Use Codes / Keywords	Structure Definition Use Codes / Keywords
EvidenceDirectness	The quality of how direct the match is.
Modifier type Codes	This value set includes sample Modifier type codes.
Provenance participant type	The type of participation a provenance participant.
Adjudication Reason Codes	This value set includes smattering of Adjudication Reason codes.
CoverageEligibilityResponse Auth Support Codes	This value set includes CoverageEligibilityResponse Auth Support codes.
ResearchStudyReasonStopped	Codes for why the study ended prematurely.
Contract Type Codes	This value set includes sample Contract Type codes.
ResearchStudyPhase	Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.
Example Provider Qualification Codes	This value set includes sample Provider Qualification codes.
Nutrition intake category codes	NutritionIntake Category Codes
VerificationResult Communication Method	Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated.
CommunicationTopic	Codes describing the purpose or content of the communication.
Immunization Program Eligibility	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example.
Can-push-updates	Ability of the primary source to push updates/alerts
MeasurePopulationType	The type of population.
Consent Vefication Codes	This value set includes base Consent Verification codes.
Diet	This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.
UsageContextType	A code that specifies a type of context being specified by a usage context.
Benefit Category Codes	This value set includes examples of Benefit Category codes.
Claim Type Codes	This value set includes Claim Type codes.
Benefit Type Codes	This value set includes a smattering of Benefit type codes.
Medication request category codes	MedicationRequest Category Codes
AdverseEventSeverity	The severity of the adverse event itself, in direct relation to the subject.
DefinitionStatus	Codes identifying the lifecycle stage of a definition.
Supply Item Type	This value sets refers to a specific supply item.
AdverseEventCategory	Overall categorization of the event, e.g. product-related or situational.
Implant Status	A set codes that define the functional status of an implanted device.
Contract Actor Role Codes	This value set includes sample Contract Actor Role codes.
GoalRelationshipType	Types of relationships between two goals.
ExpansionParameterSource	Declares what the source of a parameter is.
ActivityDefinitionCategory	High-level categorization of the type of activity.
Contract Subtype Codes	This value set includes sample Contract Subtype codes.
Contract Action Codes	This value set includes sample Contract Action codes.
MedicationRequestAdministrationLocation	Direction in which lists of possible answers should be displayed.
Benefit Term Codes	This value set includes a smattering of Benefit Term codes.
Observation Category Codes	Observation Category codes.
Payment Type Codes	This value set includes sample Payment Type codes.
Example Coverage Financial Exception Codes	This value set includes Example Coverage Financial Exception Codes.
MedicationUsageAdministrationLocation	Direction in which lists of possible answers should be displayed.
Example Service Place Codes	This value set includes a smattering of Service Place codes.
HandlingConditionSet	Set of handling instructions prior testing of the specimen.
Financial Task Codes	This value set includes Financial Task codes.
DeviceDefinitionParameterGroup	Codes identifying groupings of parameters; e.g. Cardiovascular.
ResearchSubjectStateType	Identifies the kind of state being refered to.
ChoiceListOrientation	Direction in which lists of possible answers should be displayed.
EvidenceVariableRole	The role that the assertion variable plays.
StrengthOfRecommendationRating	A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.
Immunization Subpotent Reason	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example.
PayeeType	This value set includes sample Payee Type codes.
Audit Event Outcome	The type of process where the audit event originated from.
HL7Workgroup	An HL7 administrative unit that owns artifacts in the FHIR specification.
AdverseEventCausalityAssessment	Codes for the assessment of whether the entity caused the event.
DiagnosisRole	This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.
Medication knowledge status codes	MedicationKnowledge Status Codes
Designation Usage	Preferred value set for Condition Categories.
Medication administration performer function codes	MedicationAdministration Performer Function Codes
Immunization Recommendation Status Codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example.
SpecialValues	A set of generally useful codes defined so they can be included in value sets.
DefinitionTopic	High-level categorization of the definition, used for searching, sorting, and filtering.
Payment Adjustment Reason Codes	This value set includes smattering of Payment Adjustment Reason codes.
AllergyIntolerance Verification Status	The verification status to support or decline the clinical status of the allergy or intolerance.
ExpansionProcessingRule	Defines how concepts are processed into the expansion when it's for UI presentation.
Goal achievement status	Describes the progression, or lack thereof, towards the goal against the target.
Financial Task Input Type Codes	This value set includes Financial Task Input Type codes.
SmartCapabilities	Codes that define what the server is capable of.
Funds Reservation Codes	This value set includes sample funds reservation type codes.
Medication knowledge package type codes	MedicationKnowledge Package Type Codes
StatisticCertaintyRating	The relative quality of the statistic.
Common Tags	Common Tag Codes defined by FHIR project
Enteral Formula Additive Type Code	EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example.
Unit Type Codes	This value set includes a smattering of Unit type codes.
CommunicationCategory	Codes for general categories of communications such as alerts, instructions, etc.
ResearchSubjectMilestone	Indicates the progression of a study subject through the study milestones.
Endpoint Connection Type	This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.
AllergyIntoleranceSubstanceExposureRisk	The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products).
StatisticAttributeEstimateType	Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation.
sequenceStatus	Codes providing the status of the variant test result.
PlanDefinitionType	The type of PlanDefinition.
DoseAndRateType	The kind of dose or rate specified.
Contract Content Derivation Codes	This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.
Example Program Reason Codes	This value set includes sample Program Reason Span codes.
ContainerCap	Color of the container cap.
AllergyIntolerance Clinical Status Codes	Preferred value set for AllergyIntolerance Clinical Status.
List Empty Reasons	General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).
Immunization Evaluation Dose Status Reason codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example.
Medication request status reason codes	MedicationRequest Status Reason Codes
ResearchStudyObjectiveType	Codes for the kind of study objective.
ResearchStudyPrimaryPurposeType	Codes for the main intent of the study.
ServiceProvisionConditions	The code(s) that detail the conditions under which the healthcare service is available/offered.
MIF Concept Relationship Kind	Codes for use in the ext-mif-relationship-relationshipKind to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.relationshipKind values
MIF Concept Relationship Symmetry	Codes for use in the ext-mif-relationship-symmetry to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.symmetry values
MIF Concept Relationship Transitivity	Codes for use in the ext-mif-relationship-transitivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.transitivity values
MIF Concept Relationship Reflexivity	Codes for use in the ext-mif-relationship-reflexivity to capture V3 Model Interchange Format (MIF) SupportedConceptRelationship.reflexivity values
hl7VS-practitionerIdNumberType	Value Set of codes that specify the type of number used for the practitioner identification.
hl7VS-riskCodes	Value Set of codes that specify any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient.
hl7VS-queryFormatCode	Value Set of codes which specify which of several types of formats for data to be returned in response to a query.
hl7VS-employmentStatus	Value Set of codes that specify the guarantor's employment status.
hl7VS-cclValue	Value Set of codes that specify the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis.
hl7VS-armStick	Value Set of codes specifying the arm(s) receiving a stick.
hl7VS-intendedProcedureType	Value Set of codes specifying the type of intended procedure.
hl7VS-non-subjectConsenterReason	Value Set of codes that specify a reason consent was granted by a person other than the subject of the consent.
hl7VS-errorSeverity	Concepts documenting the severity of an application error as reported during acknowledgment of messages.
hl7VS-reportTypeCode	Value Set of codes that identify the kind of patient document.
hl7VS-relationshipModifier	Value Set of codes that an observation definition to describe the subject of an observation in relation to a patient.
hl7VS-informPersonCode	Value Set of codes that specify who (if anyone) shouldor should not be informed of an error.
hl7VS-documentCompletionStatus	Value Set of codes that record the state of a document in a workflow.
hl7VS-specialtyType	Value Set of codes that identify the specialty of the care professional who is supported when using this location definition.
hl7VS-sequenceResultsFlag	Value Set of codes that specify the sequencing relationship between the current service request and a related service request(s) specified in the same information model structure.
hl7VS-donationDurationUnits	Value Set of codes specifying the units of donation duration.
hl7VS-phlebotomyStatus	Value Set of codes specifying the status of a phlebotomy.
hl7VS-typeOfAgreement	Concepts which specify codes to further identify an insurance plan.
hl7VS-deferredResponseType	Value Set of codes which specify which type of deferred query resonse is desired, as specified with the query parameters.
hl7VS-specimenCollectionMethod	Concepts to document procedures or processes by which a specimen may be collected. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment.
hl7VS-advancedBeneficiaryNoticeCode	Status codes specifying a patient's or a patient's representative's consent for responsibility to pay for potentially uninsured services. Note that this set of codes is generally used in the US only.
hl7VS-personLocationType	Value Set of codes that specify the categorization of the person's location.
hl7VS-jobStatus	Value Set of codes that specify a next of kin/associated party's job status.
hl7VS-controlledSubstanceSchedule	Value Set of codes that specify the class of the drug or other substance if its usage is controlled by legislation.
hl7VS-chargeTypeReason	Value Set of codes that specify the choice of, and providing the clinical rationale for, a selected charge type.
hl7VS-sourceOfComment	Concepts which are used to specify the source of a comment, as used in HL7 Version 2.x messaging in the NTE segment.
hl7VS-subtypeOfReferencedData	A subset of the IANA media subtypes of binary data that are encoded in an ascii structure or stream.
hl7VS-accessRestrictionValue	Value Set of codes that specify the information to which access is restricted. Note that the new codes as of November 2018 have been temporarily loaded into the underlying V2 code system pending availability of the currently unavailable new tooling, at which time this value set will be retired and a value set based on the HL7 V3 ActCode code system will be used instead for this table, and the rendered URL will be valid at terminology.hl7.org.
hl7VS-actionCode	Concepts which specify actions to be taken with respect to the specimens that accompany or precede an order. The purpose of these are to further qualify (when appropriate) the general action indicated by the order control code (code system xxxx).
hl7VS-pcaType	Value Set of codes specifying a type of PCA.
hl7VS-volumeUnits	Value Set of codes of units of measure that are used to specify volume.
hl7VS-cumulativeDosageLimitUom	Value Set of codes specifying the unit of measure (UoM) for the cumulative dosage limit.
hl7VS-documentAvailabilityStatus	Value Set of codes that define whether a patient document is appropriate or available for use in patient care.
hl7VS-consentNon-disclosureReason	Value Set of codes that specify a reason the subject did not receive full disclosure.
hl7VS-daysOfTheWeek	Value Set of codes that identify the day(s) of the week when a location may be scheduled for appointments.
hl7VS-precision	Value Set of codes used to specify the degree of precision of a time stamp.
hl7VS-rangeType	Value Set of codes that specify whether a composite price range is experssed as a flat rate or a percentage.
hl7VS-encoding	Concept identifying the type of IETF encoding used to represent successive octets of binary data as displayable ASCII characters.
hl7VS-eventRelatedPeriod	Value Set of codes that specify a common (periodical) activity of daily living.
hl7VS-consentDisclosureLevel	Value Set of codes that specify how much information was disclosed to the subject as part of the informed consent process.
hl7VS-name-addressRepresentation	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
hl7VS-documentConfidentialityStatus	Value Set of codes that specify the degree to which special confidentiality protection should be applied to information. The assignment of data elements to these categories is left to the discretion of the healthcare organization.
hl7VS-transfusionAdverseReaction	Value Set of codes that specify the type of adverse reaction that the recipient of the blood product experienced.
hl7VS-phlebotomyIssue	Value Set of codes specifying a phlebotomy issue.
hl7VS-temperatureUnits	Value Set of codes specifying the units of transport temperature.
hl7VS-exclusiveTest	Concepts that define if a test should be a specific event with no other tests to be performed with this test, or not, or other special circumstances.
hl7VS-cycleType	Value Set of codes that specify the type of cycle that is being executed. A cycle type is a specific sterilization method used for a specific type of supply item.
hl7VS-sourceOfSpecimen	Value Set of codes which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in table 0487 Specimen Type and table
hl7VS-versionControlTable	Concepts which are used to identify an HL7 version in the Version 2.x family of published standards.
hl7VS-organizationUnitType-Org	Value Set of codes that specify the classification of the organization unit.
hl7VS-denialOrRejectionCode	Value Set of codes that specify the OCE status of the line item.
hl7VS-organDonor	Value Set of codes that specify whether the patient wants to donate his/her organs and whether an organ donor card or similar documentation is on file with the healthcare organization.
hl7VS-reimbursementTypeCode	Value Set of codes that specify the fee schedule reimbursement type applied to a line item.
hl7VS-medicalRoleExecutingPhysician	Value Set of codes specifying the role of the physician ("self-employed" or "employed").
hl7VS-allergySeverity	Value Set of codes that specify the general severity of an allergy.
hl7VS-whenToCharge	Value Set of codes that specify codes for an event precipitating/triggering a charge activity.
hl7VS-whatSubjectFilter	Value Set of codes which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry.
hl7VS-diagnosticServiceSectionId	Concepts which specify a section of a diagnostic service where the observation may be performed.
hl7VS-processInterruptionReason	Value Set of codes specifying the reason for a process interruption.
hl7VS-certificationTypeCode	Value Set of codes specifying the code for a certification type.
hl7VS-patientResultsReleaseCategorizationScheme	Value Set of codes specifying the scheme for the patient results release categorization.
hl7VS-institutionRelationshipType	Value Set of codes that specify the relationship the staff person has with the institution for whom he/she provides services.
hl7VS-bloodProductDispenseStatus	Value Set of codes that specify the current status of the specified blood product as indicated by the filler or placer. For example, the first status change of a product that may trigger a Blood Product Dispense Status Message occurs when it fir
hl7VS-appointmentReasonCodes	Value Set of codes that describe the kind of appointment or the reason why an appointment has been scheduled.
hl7VS-privacyLevel	Value Set of codes that identify the level of privacy a patient will be afforded when assigned to this location definition.
hl7VS-sequenceConditionCode	Value Set of codes that specify the relationship between the start/end of the related service request(s) and the current service request.
hl7VS-levelOfCare	Value Set of codes that identify the level of care a patient may be afforded when assigned to this location definition.
hl7VS-cyclicEntryExitIndicator	Value Set of codes that specify if this service request is the first or last service request in a cyclic series of service requests.
hl7VS-bpObservationStatusCodesInterpretation	Value Set of codes that specify the interpretation for the blood product observation status codes. A status is considered preliminary until a blood product has reached a final disposition for the patient. For example, when the product is first c
hl7VS-appointmentTypeCodes	Value Set of codes that an appointment request to describe the kind of appointment.
hl7VS-preferredSpecimen-AttributeStatus	Concepts that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen.
hl7VS-checkDigitScheme	Concepts used to identify the check digit scheme employed when a check digit is used in various HL7 Version 2.x datatypes.
hl7VS-telecommunicationExpirationReason	Value Set of codes specifying the reason this contact number/email was marked as "ended".
hl7VS-deviceDataState	Value Set of codes that specify the state of the data as provided from a device.
hl7VS-annotations	Value Set of codes that specify the coded entry associated with a given point in time during the waveform recording. Note codes beyond 9903 may exist; extensions to this table may be done by incrementing the code value.
hl7VS-name-addressRepresentation	Value Set of codes that specify an indication of the representation provided by the data item.
hl7VS-reimbursementActionCode	Value Set of codes that specify the action to be taken during reimbursement calculations.
hl7VS-quantityMethod	Value Set of codes that specify the method by which the quantity distributed is measured.
hl7VS-formularyStatus	Value Set of codes that specify whether or not the service (pharmaceutical) is in the formulary.
hl7VS-livingWill	Value Set of codes that specify whether or not the patient has a living will and, if so, whether a copy fo the living will is on file at the healthcare facility. If the patient does not have a living will, the value of this field indicates whether the
hl7VS-universalIdType	Types of UID (Universal Identifiers).
hl7VS-consentStatus	Value Set of codes that specify whether the consent has been sought and granted.
hl7VS-presentOnAdmission(poa)Indicator	Value Set of codes specifying the present on admission indicator for this particular diagnosis.
hl7VS-roleExecutingPhysician	Value Set of codes specifying the account role of the physician, for example, only billing for the professional part, the technical part or both.
hl7VS-lotControl	Value Set of codes that specify whether the sterilization load for a device is built in the sub-sterile area adjacent to an Operating Room or the Central Processing Department.
hl7VS-processingId	Value Set of codes that specify whether the message is part of a production, training or debugging system.
hl7VS-statusPatient	Value Set of codes that specify whether the length of stay is normal or respectively shorter or longer than normal.
hl7VS-relationship	Concepts specifying an actual personal relationship that the next of kin/associated party has to a patient. Used in HL7 Version 2.x messaging in the NK1 segment.
hl7VS-certificationCategoryCode	Value Set of codes specifying the code for a certification category.
hl7VS-VS-observationType	Value Set of codes that specify types of observations to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order.
hl7VS-observationResultHandling	Concepts regarding the handling of a result.
hl7VS-locationEquipment	Value Set of codes that identify the equipment available in a location definition identified as a room or bed.
hl7VS-documentStorageStatus	Value Set of codes that describe the availability of a document in relation to the type of storage.
hl7VS-bloodProductTransfusion-dispositionStatus	Value Set of codes that specify the current status of the specified blood product as indicated by the placer. For example, the placer may return the blood product to the transfusion service unused because an IV could not be started. The blood co
hl7VS-serviceRequestRelationship	Value Set of codes that specify an additional or alternate relationship between this service request and other service requests.
hl7VS-patientLocationType	Value Set of codes that identify the kind of location described in the location definition.
hl7VS-productSource	Value Set of codes that describe the evaluation state of a product identified in an incident.
hl7VS-VS-observationSubtype	Value Set of codes specifying an observation sub-type.
hl7VS-processInterruption	Value Set of codes specifying whether a process was interrrupted and whether a needle had been inserted in the donor's arm prior to the interruption.
hl7VS-messageType	Concepts which specify message types for HL7 Version 2.x messaging.
hl7VS-eventReason	Value Set of codes that specify the reason for an event.
hl7VS-delayedAcknowledgmentType	Concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging.
hl7VS-bedStatus	Value Set of codes that specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not.
hl7VS-sideOfBody	Value Set of codes specifying the side of the body ("left" or "right").
hl7VS-consentBypassReason	Value Set of codes that specify the reason the subject's consent was not sought.
hl7VS-ambulatoryPaymentClassificationCode	Value Set of codes that specify the derived Ambulatory Payment Classification (APC) code.
hl7VS-tqConjunctionId	Value Set of codes that specify that a second timing specification is to follow using the repeat delimiter.
hl7VS-drgTransferType	Value Set of codes that specify a type of hospital receiving a transfer patient, which affects how a facility is reimbursed under diagnosis related group (DRG's), for example, exempt or non-exempt.
hl7VS-treatment	Value Set of codes that identify the specimen treatment performed during lab processing.
hl7VS-alertLevel	Value Set of codes that identify the highest level of the alert state (e.g.,highest alert severity) that is associated with the indicated equipment (e.g. processing event, inventory event, QC event).
hl7VS-governmentReimbursementProgram	Value Set of codes that specify codes that indicate an agency that the practitioner is authorized to bill for medical services. Existing codes only for use in the United States.
hl7VS-productionClassCode	Value Set of codes specifying the code and/or text indicating the primary use for which the living subject was bred or grown.
hl7VS-continuationStyleCode	Value Set of codes identifying whether it is a fragmented message or part of an interactive continuation message.
hl7VS-addressUsage	Value Set of codes that specify how an address is intended to be used.
hl7VS-administrationMethod	Value Set of codes that specify the specific method requested for the administration of the drug or treatment to the patient.
hl7VS-dietType	Value Set of codes that specify the type of diet.
hl7VS-package	Value Set of codes specifying the packaging unit in which this inventory supply item can be ordered or issued when purchased from the vendor in the related vendor segment.
PHVS_Race_HL7_2x	This race value set is based upon CDC check-digit codes, but using the HL7 table 0005. HL7 adopted the CDC Race and Ethnicity codes in HL7 Table 0005 in 2005. This value set has been created for backward compatibility and some historic Implementation guides (E.g. Immunization). Recommend using Race Category value set based upon CDC Race & Ethnicity code system.
hl7VS-drgProcedureRelevance	Value Set of codes that specify the relevance of this particular procedure for the diagnosis related group (DRG) determination.
hl7VS-orderStatusModifier	Value Set of codes that further define an identified status.
hl7VS-product-servicesClarification	Value Set of codes that specify the Product/Service Code.
hl7VS-processingMode	Concepts that indicate an archival process or an initial load process.
hl7VS-purgeStatus	Value Set of codes that define the state of a visit relative to its place in a purge workflow.
hl7VS-signatory'sRelationshipToSubject	Value Set of codes that specify the relationship of the consenter to the subject.
hl7VS-quantityUnits	Value Set of codes that specify the adjustment quantity.
hl7VS-segmentActionCode	Concepts specifying actions to be applied for segments when an HL7 version 2 interface is operating in "action code mode" (a kind of update mode in the Standard).
hl7VS-ReasonForStudy	Value Set of codes that provide additional information to the universal service identifier on why a test, study or review was ordered.
HL7 Value Set for State/Province	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.
hl7VS-auto-DilutionType	Value Set of codes that specify the pre‑configured dilution to be applied on the instrument, which can be used instead of a numeric declaration.
hl7VS-orderStatus	Value Set of codes that specify the status of an order. The purpose of these values are to report the status of an order either upon request (solicited), or when the status changes (unsolicited). The values are not intended to initiate action. It is as
hl7VS-itemStatus	Value Set of codes that specify the status (useful for reporting and item usage purposes) that applies to an item.
hl7VS-patientClass	Concepts used by systems to categorize patients by sites.
hl7VS-date-timeSelectionQualifier	Value Set of codes that allow the specification of certain types of values within the date/time range.
hl7VS-administrationDevice	Value Set of codes that specify the mechanical device used to aid in the administration of the drug or other treatment. Common examples are IV-sets of different types.
hl7VS-derivedSpecimen	Value Set of codes that specify the parents and children for diagnostic studies, especially in microbiology, where the initial specimen (e.g., blood) is processed to produce results (e.g., the identity of the bacteria grown out of the culture). The pro
hl7VS-addressExpirationReason	Value Set of codes that specify the reason this address was marked as "ended".
hl7VS-incidentTypeCode	Value Set of codes specifying a classification of the incident type.
hl7VS-local-remoteControlState	Value Set of codes that identify the current state of control associated with the equipment. Equipment can either work autonomously ('Local' control state) or it can be controlled by another system, e.g., LAS computer ('Remote' control state)
hl7VS-specimenComponent	Value Set of codes that identify the specimen component, e.g., supernatant, sediment, etc.
hl7VS-schoolType	Value Set of codes that specify a categorization of an academic institution that grants a degree to a Staff Member.
hl7VS-commentType	Value Set of codes that identify the type of comment text being sent in the specific comment record.
hl7VS-containerStatus	Value Set of codes that identify the status of the unique container in which the specimen resides at the time the transaction was initiated.
hl7VS-procedureDrgType	Value Set of codes that specify a procedure's priority ranking relative to its DRG.
hl7VS-rxComponentType	Value Set of codes that specify the RX component type.
hl7VS-stockLocation	Value Set of codes that specify a stock location.
hl7VS-religion2	Value Set of codes that specify a person's religion.
hl7VS-relationalConjunction	Value Set of codes used with relational operator values to group more than one segment field name.
hl7VS-organizationalNameType	Concepts used to specify the type of name for an organization i.e., legal name, display name.
hl7VS-processingConsiderationCodes	Value Set of codes that specify special processing requested of Payer for this Product/Service Line Item (e.g., hold until paper supporting documentation is received by Payer).
hl7VS-eventSeriousness	Value Set of codes that a sender to designate an event as serious or significant.
hl7VS-eventExpected	Value Set of codes that communicate whether an event has been judged to be expected or unexpected.
hl7VS-priceType	Value Set of codes that identify the intent for the dollar amount on a pricing transaction.
hl7VS-alternateCharacterSets	Value Set of codes that identify one of a number of possible standard alternate character sets for a message, either single-byte or double-byte.
hl7VS-supplierType	Value Set of codes specifying the type of supplier that will distribute the supply items associated to a contract number.
Confidentiality	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).
hl7VS-drgGroupingStatus	Value Set of codes that specify the status of the use of the gender information for diagnosis related group (DRG) determination.
hl7VS-drgProcedureDeterminationStatus	Value Set of codes that specify the status of the use of this particular procedure for the diagnosis related group (DRG) determination.
hl7VS-admissionType	Value Set of codes that specify the circumstances under which the patient was or will be admitted.
hl7VS-userAuthenticationCredentialTypeCode	Value Set of codes that specify a type of user authentication credential.
hl7VS-coordinationOfBenefits	Value Set of codes that specify whether this insurance works in conjunction with other insurance plans or if it provides independent coverage and payment of benefits regardless of other insurance that might be available to the patient.
hl7VS-substitutionStatus	Value Set of codes that specify the substitution status.
hl7VS-diagnosisPriority	Concepts that identify the significance or priority of the diagnosis code. Note that the codes are numeric, and the number of the code represents the ordinal priority of the associated diagnosis. Used in the DG1 segment in Version 2 messaging.
hl7VS-additivePreservative	Concepts specifying any additive introduced to the specimen before or at the time of collection. These additives may be introduced in order to preserve, maintain or enhance the particular nature or component of the specimen. Used in Version 2 messaging in the SPM segment.
hl7VS-tissueTypeCode	Value Set of codes that specify the type of tissue removed from a patient during a procedure.
hl7VS-languageAbility	Value Set of codes that specify codes that indicate the ability that a Staff Member possesses with respect to the language.
hl7VS-equipmentState	Value Set of codes that identify the status the equipment was in at the time the transaction was initiated.
hl7VS-artificialBlood	Value Set of codes that identify the artificial blood identifier associated with the specimen.
hl7VS-administriveSite	Concepts that specify a body site from which a specimen is obtained.
hl7VS-confidentialityCode	Value Set of codes that specify the degree to which special confidentiality protection should be applied to the observation.
hl7VS-statusAdmission	Value Set of codes that specify the admission status for the diagnosis related group (DRG) determination.
hl7VS-transactionType	Value Set of codes that specify a type of financial transaction.
hl7VS-eventTypeCode	Concepts specifying the trigger event for Version 2.x interface messages.
V2 Table 0942 Version Master	Value Set of codes that specify the type of measurement of the state of an automated laboratory instrument.
hl7VS-publicityCode	Concepts specifying a level of publicity of information about a patient for a specific visit.
hl7VS-weightUnits	Value Set of codes of units of measure that are used to specify weight.
hl7VS-telecommunicationUseCode	Concepts for specifying a specific use of a telecommunication number.
hl7VS-bloodUnitType	Value Set of codes used to specify the type of blood unit
hl7VS-nameType	Concepts for types of names for persons.
hl7VS-specialProgramCode	Value Set of codes that record a health insurance program required for healthcare visit reimbursement.
hl7VS-taxStatus	Value Set of codes used to specify the tax status of a provider.
hl7VS-diagnosisClassification	Value Set of codes that classify whether a patient visit can be related to a diagnosis.
hl7VS-maritalStatus	Value Set of codes that specify a person's marital (civil/legal) status.
hl7VS-ethnicGroup	Concepts further defining a patient's ancestry. In the US, a current use is to use these codes to report ethnicity in line with US federal standards for Hispanic origin. Used for HL7 Version 2 messaging in the PID segment.
hl7VS-routeOfAdministration	Value Set of codes that specify the route of administration.
hl7VS-systemInducedContaminants	Value Set of codes that identify the specimen contaminant identifier associated with the specimen in the container.
hl7VS-degreeLicenseCertificate	Concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in Version 2 messaging; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7.
hl7VS-organizationUnitType	Value Set of codes that specify the environment in which the provider acts in the role associated with the provider type, and inludes codes for venues outside of formal organized healthcare settings, such as Home. The provider environment is no
hl7VS-allergyClinicalStatus	Value Set of codes specifying the verification status for the allergy.
hl7VS-specialHandlingConsiderations	Concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in Version 2 messaging in the SPM segment.
hl7VS-languageProficiency	Value Set of codes which specify the level of knowledge a person possesses with respect to a language ability identified.
hl7VS-analyteRepeatStatus	Value Set of codes identifying the repeat status for the analyte/result (e.g. original, rerun, repeat, reflex). The following are assumptions regarding the table values: Repeated without dilution — performed usually to confirm correctness of r
hl7VS-penaltyType	Value Set of codes that specify whether the amount is currency or a percentage.
hl7VS-natureOfServiceTestObservation	Concepts specifying an identification of a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations, typically used as an indicator for Master Files.
hl7VS-trayType	Value Set of codes that specify the type of dietary tray.
hl7VS-payeeRelationshipToInvoice	Value Set of codes used to specify the relationship to the invoice for Person Payee Types.
hl7VS-telecommunicationEquipmentType	Concepts for specifying a type of telecommunication equipment.
hl7VS-adjustmentCategoryCode	Value Set of codes used to specify the category of adjustment and is used to assist in determining which table is used for Adjustment Reason.
hl7VS-paymentMethodCode	Value Set of codes used to specify the method for the movement of payment.
hl7VS-patientStatusCode	Value Set of codes that define the state of a care episode for a patient.
hl7VS-invoiceProcessingResultsStatus	Value Set of codes used to specify the processing status for an Invoice Processing Result.
hl7VS-visitPriorityCode	Value Set of codes that define a relative level of urgency applied to a patient visit.
hl7VS-identifierType	Concepts specifying types of identififiers, as used in person and organization identification datatypes in HL7 Version 2 standards.
hl7VS-providerAdjustmentReasonCode	Value Set of codes used to specify the reason for this adjustment.
hl7VS-product-serviceStatus	Value Set of codes that specify the processing status for the Product/Service Code.
hl7VS-VS-limitationTypeCode	Value Set of codes specifying a type of limitation.
hl7VS-administrativeSex	Concepts specifying a patient's sex for administrative purposes.
hl7VS-mimeTypes	Value Set of codes specifying the general type of data.
hl7VS-allowSubstitution	Value Set of codes that specify whether substitutions are allowed and, if so, the type of substitutions allowed.
hl7VS-masterFileIdentifierCode	Concepts which are represented by codes identifying HL7Versions 2.x Master Files.
hl7VS-dayType	Value Set of codes that specify whether the days are denied, pending or approved.
hl7VS-processingType	Value Set of codes identifying the processing type that applies to the test code. If this attribute is omitted, then regular production is the default.
hl7VS-otherEnvironmentalFactors	Value Set of codes that identify the other environmental factors associated with the specimen in a specific container, e.g., atmospheric exposure.
hl7VS-patientConditionCode	Value Set of codes specifying the patient's current medical condition for the purpose of communicating to non-medical outside parties, e.g. family, employer, religious minister, media, etc.
hl7VS-segmentGroup	Value Set of codes that specify the optional segment groups which are to be included in a response.
hl7VS-precertificationPatientType	Value Set of codes that specify the category or type of patient for which this certification is requested.
hl7VS-eligibilitySource	Value Set of codes that specify the source of information about the insured's eligibility for benefits.
hl7VS-file-levelEventCode	Concepts specifying file-level events for master files. Used in HL7 Version 2 messaging in the MFI segment.
hl7VS-amountClass	Value Set of codes that specify the amount quantity class.
hl7VS-providerBilling	Value Set of codes that specify how provider services are billed.
hl7VS-drgStatusFinancialCalculation	Value Set of codes that specify the status of the diagnosis related group (DRG) calculation regarding the financial aspects.
workClassificationODH	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.).
hl7VS-onlineVerificationResultErrorCodes	V2 Table 0971 Version Master (Online Verification Result Error Code)
hl7VS-inactiveReasonCode	Value Set of codes that specify the reason the staff member is inactive.
hl7VS-insuranceCompanyContactReason	Value Set of codes that describe why an insurance company has been contacted.
hl7VS-invoiceReasonCodes	Value Set of codes that specify the reason for an invoice.
hl7VS-volumeUnits	Value Set of codes of units of measure that are used to specify volume.
hl7VS-adjustmentAction	Value Set of codes used to specify the action requested of a party that receives an adjustment.
hl7VS-invoiceType	Value Set of codes that specify the type of invoice.
PHVS_ManufacturersOfVaccinesMVX_CDC_NIP	Value Set of codes that specify the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control. Note that the source of truth for these code values are maintained by the CDC, and the code system may be acce
hl7VS-onlineVerificationResult	Code values used to indicate the result of an online verification of insurance data.
hl7VS-statusRespirationMinutes	Value Set of codes that specify the status of the use of the respiration minutes information for diagnosis related group (DRG) determination.
hl7VS-countryCode-3alpha	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.
hl7VS-responseLevel	Concepts specifying application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type) for application-level acknowledgment paradigms for Master Files transactions.
hl7VS-roomType	Value Set of codes that specify the room type.
hl7VS-substanceType	Value Set of codes identifying the type of substance.
hl7VS-applicationChangeType	Value Set of codes that specify a type of change being requested (if NMR query) or announced (if NMD unsolicited update).
hl7VS-severityOfIllnessCode	Value Set of codes specifying the severity ranking of a patient's illness.
hl7VS-advanceDirectiveCode	Value Set of codes specifying the patient's instructions to the healthcare facility.
hl7VS-cweStatuses	Concepts that represent an exception identifier code; that is, a code that is not defined in the value set (either model or site-extended). These are occationsally referred to a 'flavors of null' although this set of concepts is specific to the CWE datatype used in Version 2 messaging, and the codes may be used in the 'identifier' component of the 'triplets' in that datatype.
hl7VS-caseCategoryCode	Value Set of codes specifying the reason a non-urgent patient presents to the emergency room for treatment instead of a clinic or physican office.
hl7VS-occurrenceSpan	Concepts drawn from the National Uniform Billing Committee (NUBC) code that identifies an event that relates to the payment of a claim. Used in Version 2 messaging in the Occurrence Span Code and Date (OSP) value.
hl7VS-alertDeviceCode	Value Set of codes specifying any type of allergy alert device the patient may be carrying or wearing.
hl7VS-matchReason	Value Set of codes identifying what search components (e.g., name, birthdate, social security number) of the record returned matched the original query where the responding system does not assign numeric match weights or confidence levels. It
hl7VS-policyType	Value Set of codes that specify the policy type.
hl7VS-addressType	Concepts specifying types or kinds of addresses.
hl7VS-sterilizationType	Value Set of codes specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment.
hl7VS-route	Value Set of codes that are used to indicate a means of administrating a medication dose.
hl7VS-statusWeightAtBirth	Value Set of codes that specify the status of the use of the weight at birth for diagnosis related group (DRG) determination.
hl7VS-priority	Value Set of codes that specify the allowed priorities for obtaining the specimen.
hl7VS-payeeType	Value Set of codes that specify the type of payee (e.g., organization, person).
hl7VS-studentStatus	Value Set of codes that designate whether a guarantor is a full or part time student.
hl7VS-escortRequired	Value Set of codes indicating whether a patient must be accompanied while travelling to a diagnostic service department.
hl7VS-transportArranged	Value Set of codes defining whether patient transportation preparations are in place.
hl7VS-benefitGroup	Value Set of codes that specify the benefit group.
hl7VS-procedureFunctionalType	Value Set of codes that classify a procedure.
hl7VS-typeOfData	Concepts declaring the general type of media data that is encoded.
hl7VS-preferredMethodOfContrct	Value Set of codes that specify which of a group of multiple phone numbers is the preferred method of contact for this person.
hl7VS-itemImportanceCodes	Value Set of codes that denote a level or importance of an inventory item within the context of an inventory location.
hl7VS-amountType	Value Set of codes that specify amount quantity type.
hl7VS-matchAlgorithms	Value Set of codes identifying the name or identity of the specific search algorithm to which the RCP-5 Search Confidence Threshold and the QRI-1 Candidate Confidence refer.
hl7VS-commandResponse	Value Set of codes identifying the response of the previously issued command.
hl7VS-occurrenceCode	Concepts drawn from the National Uniform Billing Committee (NUBC) code for the event or occurrence relating to a bill that may affect payer processing. Used in Version 2 messaging in the Occurrence Code and Date (OCD) value.
hl7VS-sensitivityToCausativeAgentCode	Value Set of codes specifying the reason the patient should not be exposed to a substance.
hl7VS-triageCode	Value Set of codes specifying a patient's prioritization within the context of this abstract.
hl7VS-patient’sRelationshipToInsured	Value Set of codes that specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies.
hl7VS-remoteControlCommand	Value Set of codes that identify the comment the component is to initiate.
hl7VS-bloodProductCode	Value Set of codes specifying the blood product code.
hl7VS-admissionLevelOfCareCode	Value Set of codes specifying the acuity level assigned to the patient at the time of admission.
hl7VS-messageStructure	HL7 abstract message structure codes.
hl7VS-substanceStatus	Value Set of codes identifying the status of the inventoried item. The status indicates the current status of the substance.
hl7VS-sequencing	Value Set of codes identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not.
hl7VS-protectionCode	Value Set of codes that specify that an address needs to be treated with special care or sensitivity.
hl7VS-militaryStatus	Value Set of codes that specify the military status of the patient. This field is defined by CMS or other regulatory agencies.
hl7VS-whichDate-timeQualifier	Value Set of codes that specify the type of date referred to in the other date fields in the QRF segment.
hl7VS-mfnRecode-levelErrorReturn	Concepts which code status values for requested master file record update operations.
hl7VS-itemType	Value Set of codes that specify a classification of material items into like groups as defined and utilized within an operating room setting for charting procedures.
DeviceSafety	Codes used to identify medical devices safety characteristics. These codes are taken from the [NCI Thesaurus](https://ncit.nci.nih.gov/ncitbrowser/pages/home.jsf) and are provided here as a suggestive example.
hl7VS-rulingAct	Value Set of codes that specify an act containing a rule that the item is legally required to be included in notification reporting.
hl7VS-queryResponseStatus	Concepts defining precise response status concepts in support of HL7 Version 2 query messaging.
hl7VS-reportTiming	Value Set of codes that identify the time span of a report or the reason for a report sent to a regulatory agency.
hl7VS-livingArrangement	Concepts characterizing the situation that patient-associated parties live in at their residential address.
hl7VS-jurisdictionalBreadth	Value Set of codes that specify the breadth/extent of the jurisdiction where the qualification is valid.
hl7VS-reportSource	Value Set of codes that identify where a report sender learned about an event.
hl7VS-invoiceControlCode	Value Set of codes that specify what invoice action is being performed by this message.
hl7VS-relationalOperator	Value Set of codes that define the relationship between HL7 segment field names identified in a query construct.
FHIRdeviceStatus	The availability status of the device.
hl7VS-masterfileActionCode	Concepts specifying an action for a master file record. Used in HL7 V2.x messaging in the MFE segment.
hl7VS-whichDate-timeStatusQualifier	Value Set of codes that specify the status type of objects selected in date range defined by QRF-2 and QRF-3.
hl7VS-itemStatusCodes	Value Set of codes that specify the state of an inventory item within the context of an inventory location.
hl7VS-codingSystem	Names of coding systems. Each coding system is assigned a unique identifier, which is generally a short mnemonic derived from the full name of the coding system.
hl7VS-precautionCode	Value Set of codes specifying non-clincal precautions that need to be taken with the patient.
hl7VS-primaryKeyValueType	Value Set of codes that specify the type for the master file record identifier.
hl7VS-riskManagementIncidentCode	Value Set of codes specifying the incident that occurred during a patient's stay.
hl7VS-specimenRole	Value Set of codes that identify the role of a sample.
hl7VS-messageErrorConditionCodes	HL7 (communications) error codes, as transmitted in a message acknowledgement.
hl7VS-recreationalDrugUseCode	Value Set of codes specifying what recreational drugs the patient uses.
hl7VS-newbornCode	Value Set of codes specifying whether the baby was born in or out of the facility.
hl7VS-responseModality	Value Set of codes identifying the timing and grouping of the response message(s).
hl7VS-reportingPriority	Value Set of codes that specify the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority.
hl7VS-accept-applicationAcknowledgmentConditions	Concepts which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode.
hl7VS-ambulatoryStatus	Value Set of codes that specify permanent or transient handicapped conditions of a person.
dataAbsentReason	Used to specify why the normally expected content of the data element is missing.
hl7VS-relationshipType	Value Set of codes that specify the type of relationship that is established between the instances of Source Information and Target Information.
hl7VS-approvingRegulatoryAgency	Value Set of codes that specify the regulatory agency by which the item has been approved, such as the FDA or AMA.
hl7VS-livingDependency	Value Set of codes identifying specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient's healthcare needs.
hl7VS-eventQualification	Value Set of codes that qualify an event related to a product experience.
hl7VS-bodyParts	Value Set of codes that specify the part of the body.
hl7VS-eventReportedTo	Value Set of codes that identify the type of entity to which the event has been reported.
hl7VS-containerCondition	Value Set of codes that specify at each receipt the status of the container in which the specimen is shipped in chain of custody cases where specimens are moved from lab to lab. If the container is compromised in any way (seal broken, container
hl7VS-orderControlCodeReason	Value Set of codes that describe reasons for the chosen order control codes.
DeviceType	Codes used to identify medical devices.
hl7VS-siteAdministered	Value Set of codes that specify a location on the body where a dose is to be administered, e.g., IV, IM, Subcutaneous.
hl7VS-acknowledgmentCode	Concepts specifying acknowledgment codes used in Version 2.x message. For details of usage, see message processing rules in the published Standard.
hl7VS-active-inactive	Value Set of codes that specify whether a person is currently a valid staff member.
hl7VS-militaryService	Value Set of codes that specify the military branch. This field is defined by CMS or other regulatory agencies.
hl7VS-processingPriority	Value Set of codes that specify one or more available priorities for performing the observation or test.
hl7VS-modifyIndicator	Value Set of codes identifying whether the subscription is new or is being modified.
hl7VS-gestationCategoryCode	Value Set of codes specifying the status of the birth in relation to the gestation
hl7VS-alternateCharacterSetHandlingScheme	Concepts that specify the scheme used when any alternative character sets are specified in the second or later iterations of MSH-18 Character Set, and if any special handling scheme is needed.
hl7VS-modeOfArrivalCode	Value Set of codes specifying how the patient was brought to the healthcare facility.
hl7VS-procedurePriority	Value Set of codes specifying a number that identifies the significance or priority of the procedure code.
hl7VS-facilityType	Value Set of codes that specify the type of facility.
hl7VS-overallClaimDispositionCode	Value Set of codes specifying the final status of the claim.
hl7VS-providerRole	Value Set of codes that specify the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.).
hl7VS-locationRelationshipId	Value Set of codes that specify an identifier code to show which relationship is being communicated with the segment.
hl7VS-specimenChildRole	Value Set of codes that specify for child specimens the relationship between this specimen and the parent specimen.
hl7VS-pharmacyOrderTypes	Value Set of codes that specify the general category of pharmacy order which may be used to determine the processing path the order will take.
hl7VS-procedurePractitionerType	Value Set of codes of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete.
hl7VS-allergyType	Value Set of codes that specify classification of general allergy categories (drug, food, pollen, etc.).
hl7VS-loadStatus	Value Set of codes that specify the status of the information provided in a device sterilization or decontamination cycle.
hl7VS-deviceStatus	Value Set of codes that specify the state of a device.
hl7VS-actpriority	Value Set of codes specifying the priority for a shipment.
hl7VS-participation	Concepts that represent functional involvement of a caregiver or member of a care team with an activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.)
hl7VS-computationType	Value Set of codes that specify if the change is computed as a percent change or as an absolute change.
hl7VS-actionTakenInResponseToTheEvent	Value Set of codes that define the action taken as a result of an event related to a product issue.
hl7VS-allowSubstitutionCodes	Value Set of codes that indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment.
hl7VS-providerRole	Value Set of codes that define the relationship between a referral recipient and a patient or between a referral initiator and a patient.
PHVS_VaccinesAdministeredCVX_CDC_NIP	Value Set of codes that specify the administered vaccines. The values are maintained by the US Centers of Disease Control.. The code system is maintained by the CDC, and may be found at URL; https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.1
hl7VS-actionCode	Concepts used in Patient Care for the intent of a problem or goal. Used in Version 2 messaging in the GOL segment.
hl7VS-fillerStatusCodes	Value Set of codes that describe an appointment status from the perspective of the entity assigned to fulfill the appointment.
hl7VS-certificateStatus	Value Set of codes that specify the status of the certificate held by a health professional.
hl7VS-relatednessAssessment	Value Set of codes that provide an estimate of whether an issue with a product was the cause of an event.
hl7VS-confidentiality	Value Set of codes specifying the confidentiality for a shipment.
hl7VS-queryPriority	Concepts which specify a time frame in which a querry response is expected.
hl7VS-observationResultStatus	Concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier.
hl7VS-diagnosisType	Concepts specifying a type of diagnosis being sent in HL7 Version 2.x messages.
hl7VS-grouperStatus	Value Set of codes that specify the status of a grouper in general.
hl7VS-quantityLimitedRequest	Concepts which specify the maximum length of a query response that can be accepted by a requesting system, and are expressed as units of mesaure of query response objects.
hl7VS-bodySiteModifier	Value Set of codes that specify the modifier for the body site.
hl7VS-locationServiceCode	Value Set of codes specifying the types of services provided by the location.
hl7VS-locationCharacteristicId	Value Set of codes that specify an identifier code to show which characteristic is being communicated with the segment.
hl7VS-marketingBasis	Value Set of codes that specify the basis for marketing approval.
hl7VS-revenueCode	Value Set of codes specifying a revenue code as specified in the National Uniform Billing Committee (NUBC) UB-04 manual, UB form locator 42, the service line revenue code. These are claim codes indicating the identifying number for the product or service provided. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html.
hl7VS-visitIndicator	Value Set of codes that specify the level on which data are being sent. It is the indicator used to send data at two levels, visit and account. HL7 recommends sending an "A" or no value when the data in the message are at the account level or "V" to i
hl7VS-dataTypes	Value Set of codes specifying the data type.
hl7VS-networkSourceType	Value Set of codes that indicate (in certain systems) whether a lower level source identifier is an initiate or accept type.
hl7VS-paymentAdjustmentCode	Value Set of codes that specify any payment adjustment due to drugs or medical devices.
hl7VS-authorizationMode	Concepts of forms of authorization a recorder may receive from the responsible practitioner to create or change an order. Used in Version 2 messaging for orders in the ORC segment.
hl7VS-consentMode	Value Set of codes that specify the method in which a subject provides consent.
hl7VS-reorderTheoryCodes	Value Set of codes that specify the calculation method used to determine the resupply schedule.
hl7VS-transportationMode	Value Set of codes that specify how (or whether) to transport a patient, when applicable, for an ordered service.
hl7VS-visitUserCode	Value Set of codes that specify categories of a patient's visit with respect to an individual institution's needs, and is expected to be different on a site-specific basis.
hl7VS-supplyRiskCodes	Value Set of codes specifying any known or suspected hazard associated with this material item.
hl7VS-interpretationCode	A categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: 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. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version.
hl7VS-VS-communicationLocation	Value Set of codes specifying a communication location.
hl7VS-shipmentStatus	Value Set of codes specifying the status of a shipment.
hl7VS-causalityObservations	Value Set of codes that record event observations regarding what may have caused a product related event.
hl7VS-notifyClergyCode	Value Set of codes that specify whether the clergy should be notified.
hl7VS-messageWaitingPriority	Value Set of codes that specify how important the most important waiting mesasge is. For example, if there are 3 low priority messages, 1 medium priority message and 1 high priority message, the message waiting priority would be "high", because
hl7VS-bloodProductProcessingRequirements	Value Set of codes that specify additional information about the blood component class associated with the Universal Service ID. The placer of the order can specify any required processing of the blood product that must be completed prior to t
hl7VS-referralCategory	Value Set of codes that describe the patient care setting where a referral should take place.
hl7VS-mimeBase64EncodingCharacters	Value Set of codes that are used for base64 MIME encoding. Base64 is defined as follows (adapted from MIME Internet standard RFC 1521).
hl7VS-startOfEvaluation	Value Set of codes that describes the status of product evaluation.
hl7VS-indirectExposureMechanism	Value Set of codes that identify the mechanism of product transmission when the product has not been directly applied to the patient.
hl7VS-signatureCode	Concepts that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider.
hl7VS-securityCheckScheme	Value Set of codes specifying the scheme for a security check.
hl7VS-acquisitionModality	Value Set of codes specifying the modality for the acquisition of an image.
hl7VS-VS-collectionEvent	Value Set of codes specifying the limit for a collection event or process step.
hl7VS-re-admissionIndicator	Value Set of codes which are used to specify that a patient is being re-admitted to a healthcare facility from which they were discharged, and indicates the circumstances around such re-admission.
hl7VS-orderControl	Concepts which are used to determine the function of the order segment. Depending on the message, the action specifies by one of these control codes may refer to an order or an individual service.
hl7VS-contactRole2	Concepts which specify a relationship role that the next of kin/associated parties plays with regard to the patient. Built on the updated code system. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral.
hl7VS-deviceType	Value Set of codes that specify the kind of device as defined by the manufacturer.
hl7VS-valueType	Concepts which specify the data type of OBX-5, Observation Value, and are a subset of the datatypes defined in HL7 Version 2.x.
hl7VS-consentType	Value Set of codes that specify to what the subject is consenting, i.e. what type of service, surgical procedure, information access/release or other event.
hl7VS-orderType	Value Set of codes that specify whether the order is to be executed in an inpatient setting or an outpatient setting.
hl7VS-packagingStatusCode	Value Set of codes that specify the packaging status of the service.
hl7VS-immunizationRegistryStatus	Immunization registry status codes of a patient. Used in Version 2 messaging in the PD1 segment.
hl7VS-identityReliabilityCode	Value Set of codes that specify the reliability of patient/person identifying data transmitted via a transaction.
hl7VS-actionCode	Status codes of record operations.
hl7VS-certificationStatus	Value Set of codes that specify the status of the practitioner's speciality certification.
hl7VS-specimenAppropriateness	Value Set of codes that specify the suitability of the specimen for the particular planned use as determined by the filler.
hl7VS-reportPriority	Value Set of codes which specify the priority associated with a report or update run using a query.
hl7VS-responseFlag	Value Set of codes allowing the placer (sending) application to determine the amount of information to be returned from the filler.
hl7VS-dateFormat	Value Set of codes that specify the date format for a decontamination/sterilization instance.
hl7VS-assignmentOfBenefits	Value Set of codes which indicate whether an insured person agreed to assign the insurance benefits to a healthcare provider. If so, the insurance will pay the provider directly.
hl7VS-hospitalService	Value Set of codes that specify the treatment or type of surgery the patient is scheduled to receive.
hl7VS-rootCause	Value Set of codes specifying a root cause.
hl7VS-natureOfChallenge	Value Set of codes that further describe an observation definition that is characterized as a challenge observation.
hl7VS-identityMayBeDivulged	Value Set of codes that define whether the primary observer has given permission for their identification information to be provided to a product manufacturer.
hl7VS-timeSelectionCriteriaParameterClassCodes	Value Set of codes that describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling.
hl7VS-referralPriority	Value Set of codes that designate the urgency of a referral.
hl7VS-referralType	Value Set of codes that identify the general category of healthcare professional desired to satisfy a referral.
hl7VS-primaryObserver'sQualification	Value Set of codes that provide a general description of the kind of health care professional who provided the primary observation.
hl7VS-sequenceCondition	Value Set of codes that identify whether sequence conditions or a repeating cycle of orders is defined, as part of the Order Sequence Definition.
hl7VS-organization-Agency-Department	Value Set of codes that specify the agency or department that assigned a specified identifier.
hl7VS-timeDelayPostChallenge	Value Set of codes that classify an observation definition as being a component of a challenge test.
hl7VS-overrideType	Value Set of codes that specify what type of override can be used to override the specific error identified.
hl7VS-outlierType	Value Set of codes that specify the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid.
hl7VS-weightUnits	Value Set of codes of units of measure that are used to specify weight.
hl7VS-queryResultsLevel	Value Set of codes which are used to control level of detail in query results.
hl7VS-specimenCondition	Concepts of modes or states of being that describe the nature of a specimen. Used in Version 2 messaging in the SPM segment.
hl7VS-specimenType	Concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system xxxx) which conflated specimen types and specimen collection methods. Used in Version 2 messaging in the SPM segment.
hl7VS-referralReason	Value Set of codes that specify the reason for which the referral will take place.
hl7VS-eventType	Value Set of codes specifying the type of event of the message.
hl7VS-nameAssemblyOrder	Value Set of codes specifying the preferred display order of the components of this person name.
hl7VS-completionStatus	Status codes used in the workflow of treatment administration events.
hl7VS-formularyStatus	Value Set of codes that specify whether or not the pharmaceutical substance is part of the local formulary.
hl7VS-disabledPerson	Value Set of codes that specify to which person the disability information relates in the message. For example, if the value is PT, the disability information relates to the patient.
hl7VS-specimenQuality	Value Set of codes that specify the degree or grade of excellence of the specimen at receipt.
hl7VS-extendedPriorityCodes	Concepts describing the urgency of a request carried in an order. Used in Version 2 messaging in timing/quantity; in older versions of the Standard was used in the TQ datatype, but in later versions it is used in the TQ1 segment (which replaced the TQ datatype which has been withdrawn). Many of the codes are widely recognized values used in healthcare settings in the english-speaking world.
hl7VS-yes-no-Indicator	Codes specifying either Yes or No used in fields containing binary answers generally user-specified.
hl7VS-chargeType	Value Set of codes that specify someone or something other than the patient to be billed for a service.
hl7VS-bolusType	Value Set of codes specifying a type of bolus.
hl7VS-override	Value Set of codes that define whether a Charge Description Master description may be overridden or if it must be overridden.
hl7VS-eventConsequence	Value Set of codes that describe the impact of an event on a patient.
hl7VS-kindOfQuantity	Value Set of codes that describe the underlying kind of property represented by an observation. The categories distinguish concentrations from total amounts, molar concentrations from mass concentrations, partial pressures from colors, and so
hl7VS-expandedYes-NoIndicator	Value Set of codes that specify an expansion on the original Yes/No indicator table by including "flavors of null". It is intended to be applied to fields where the response is not limited to "yes" or "no".
hl7VS-referralStatus	Value Set of codes that define the state of a referral.
hl7VS-referralDisposition	Value Set of codes that identify the expected response from the healthcare professional receiving a referral.
hl7VS-durationCategories	Value Set of codes that classify an observation definition as intended to measure a patient's state at a point in time.
hl7VS-calendarAlignment	Value Set of codes that specify an alignment of the repetition to a calendar (e.g., to distinguish every 30 days from "the 5th of every month").
hl7VS-patientOutcome	Value Set of codes that describe the overall state of a patient as a result of patient care.
hl7VS-chargeOnIndicator	Value Set of codes that define the event upon which a charge should be generated.
hl7VS-natureOfAbnormalTesting	Value Set of codes that specify the nature of an abnormal test.
hl7VS-relevantClincialInformation	Value Set of codes that specify additional clinical information about the patient or specimen to report the supporting and/or suspected diagnosis and clinical findings on requests for interpreted diagnostic studies.
hl7VS-drgDiagnosisDeterminationStatus	Value Set of codes that specify the status of a diagnosis for a diagnosis related group (DRG) determination.
hl7VS-moodCodes	Value Set of codes that specify the functional state of an order.
InformationSensitivityPolicy	Value Set of codes that specify the reason for the restricted access. 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.titleValue Set of codes that specify the reason for the restricted access.
hl7VS-resultStatus-Obr	Concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment.
hl7VS-mailClaimParty	Value Set of codes that specify a party to which a claim should be mailed when claims are sent by mail.
hl7VS-laborCalculationType	Value Set of codes that specify the method used to calculate employee labor and measure employee productivity.
hl7VS-dispenseType	Value Set of codes that specify the type of dispensing event that occurred.
hl7VS-specimenRejectReason	Reasons a specimen may be rejected for a specified observation/result/analysis. Used in Version 2 messaging in the SPM segment.
hl7VS-dispenseMethod	Value Set of codes that specify the method by which treatment is dispensed.
hl7VS-repeatPattern	Value Set of codes that specify the interval between repeated services. See the Comment/Usage Note in the table below, as the table contains both precoordinated codes that may be used in an HL7 field or component and also explanatory patterns i
hl7VS-coverageType	Note that this set of codes is used generally in the US only.
OregonAthapaskan
PerineuralRoute	Perineural
NullFlavor
RoleClassSubsumer	An entity that subsumes the identity of another. Used in the context of merging documented entity instances. Both the player and scoper must have the same classCode. The use of this code is **deprecated** in favor of the term SUBY which is its inverse and is more ontologically correct.
ObservationInterpretationNormalityHigh	Interpretation for a quantitative observation of degree of abnormality (including critical or "alert" level) above the upper limit of the reference range.
x_RoleClassCoverage	An abstract domain that encompasses the roles that arise in the context of providing, purchasing, and managing health care coverage and insurance.
LingualRoute	Lingual
ParticipationCallbackContact	A person or organization who should be contacted for follow-up questions about the act in place of the author.
ClinicalNurseSpecialistHIPAA	A registered nurse who, through a graduate degree program in nursing, or through a formal post-basic education program or continuing education courses and clinical experience, is expert in a specialty area of nursing practice within one or more of the components of direct patient/client care, consultation, education, research and administration.
RoleClassIdentifiedEntity	Roles played by entities and scoped by entities that identify them for various purposes.
EntityClassHealthChartEntity	A health chart included to serve as a document receiving entity in the management of medical records.
TableRules	These values are defined within the XHTML 4.0 Table Model
ActCoverageAssessmentObservationValue	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.
ActMoodProposal	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.
x_ActClassCareProvisionObservation
ParticipationDistributor	Distributes material used in or generated during the act.
TrustPolicy	A mandate, obligation, requirement, rule, or expectation conveyed as security metadata between senders and receivers required to establish the reliability, authenticity, and trustworthiness of their transactions. Trust security metadata are observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain’s trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. \[Based on ISO IEC 10181-1 and NIST SP 800-63-2\]
ActRelationshipHasSubject	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.
x_AdministeredSubstance	A type of Manufactured Material that is administered to a living subject, either by a healthcare professional or auto-administered, within a healthcare context.
CoveredPartyRoleType	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.
RespiratoryTherapistHIPAA	A respiratory therapist is a person who has graduated from a respiratory therapy program accredited by the Committee on Allied Health Education and Accreditation, and where applicable, is licensed by the state and is practicing within the scope of that license. A respiratory therapist administers oxygen and other gases and provides assistance with equipment to patients with either acute or chronic breathing difficulties, often within the home.
SuppositoryRoute	Suppository
ActClassSpecimenObservation	An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation
AnnotationType
x_InformationRecipient	Used to represent participant(s) who should receive a copy of a document.
RoleClassRelationshipFormal	A relationship between two entities that is formally recognized, frequently by a contract or similar agreement.
RoleClassIndividual	**Description:** A role played by a party covered under a policy as the policy holder. An individual may be either a person or an organization. **Note:** The party playing the role of an individual insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a named insured may make a claim under a policy, e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy if injured in an automobile accident and there is no liable third party. In the case of an individual insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that an individual insured has filed a claim for a loss. **Example:** The individual insured under a comprehensive automobile, disability, or property and casualty policy that is the policy holder.
LifeInsurancePolicy	**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).
RoleClassRegulatedProduct	A product regulated by some governmentatl orgnization. The role is played by Material and scoped by Organization. Rationale: To support an entity clone used to identify the NDC number for a drug product.
LaryngealRoute	Laryngeal
ParticipationResponsibleParty	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.
SecurityControlObservationType	Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata conveys instructions for secure distribution, transmission, storage or use.
ActCoverageLimitCode	Criteria that are applicable to the authorized coverage.
x_ActEncounterReason	Administrative reasons for patient encounters. *Example:*Medical necessity, patient request and dependency.
ManagedParticipationStatusCancelled	The terminal state resulting from cancellation of the Participation prior to activation.
ParticipationAttender	The practitioner that has responsibility for overseeing a patient's care during a patient encounter.
StreetName
MedicalDevice	A device with direct or indirect therapeutic purpose. Values for EntityCode when EntityClass = "DEV"
EPSG-GeodeticParameterDataset	**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.
ParentInLaw	The player of the role is the parent of scoping person's husband or wife.
ObservationInterpretationChange	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.
x_ActMoodDefEvnRqo
HL7SearchUse
ActRelationshipCheckpoint	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.
x_DocumentEntrySubject	Used to represent the role(s) of those who can serve as subjects of the contents of a clinical document.
ObservationIncomeValue	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.
GenericUpdateReasonCode	**Description:**Identifies why a change is being made to a record.
Yukian
Yaqui
ActClassLocus	**Description:**The position of a gene (or other significant sequence) on the genome.
ActClassStateTransitionControl	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.
CountryEntityType	A set of codes identifying specific countries.
ActClassDetectedIssue	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).
ActClassGrouper
RegulationPolicyActCode	**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
ActConditionList	List of condition observations.
Race	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.
IntrabursalRoute	Intrabursal
EskimoAleut
DocumentSectionType	The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc.
RefrainPolicy	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
x_ActMoodEvnOrdPrmsPrp
ActClassComposition	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.
x_ActClassCareProvisionProcedure
RoleClassClaimant	**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.
RoleClassCaregiver	A person responsible for the primary care of a patient at home.
ActEncounterCode	Domain provides codes that qualify the ActEncounterClass (ENC)
ActPriority	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.
RefusalReasonCode
RouteByMethod	Route of substance administration classified by administration method.
EntityClassPerson	A living subject of the species homo sapiens.
DoseDurationDetectedIssueCode	Proposed length of therpay differs from standard practice
ActResearchInformationAccess	**Definition:** Consent to have healthcare information in an electronic health record accessed for research purposes.
RoleClassIngredientEntity	Relates a component (player) to a mixture (scoper). E.g., Glucose and Water are ingredients of D5W, latex may be an ingredient in a tracheal tube.
x_RoleClassPayeePolicyRelationship	The specification of the relationship of the Payee to the invoice. Can be used in cases when an insurer is not directly paying the healthcare provider (as payee) but reimbursing the party that paid the invoice/claim.
EntericCoatedTablet
ContainerEntityType	Material intended to hold another material for purpose of storage or transport.
EligibilityActReasonCode	**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.
x_VeryBasicConfidentialityKind	**Description:**Limits confidentiality to effectively a yes/no decision. *Usage Note:*x\_VeryBasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.
PadDrugForm
ActAdministrativeAuthorizationDetectedIssueCode
ICUPracticeSetting
Chew	Chew
RaceAmericanIndianNavajo
RoleClassDistributedMaterial	A material (player) distributed by a distributor (scoper) who functions between a manufacturer and a buyer or retailer.
ActRelationshipHasPreviousInstance	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.
ActClassAccommodation	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.
ActClassClinicalTrialTimepointEvent	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.
RaceAlaskanNativeYupikEskimo
CapsuleDrugForm	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.
ExpectedSubset	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.
BehavioralHealthAndOrSocialServiceProviderHIPAA	Broad classification aggregating providers who are trained and educated to perform services related to behavioral health, mental health, and counseling and may be licensed or practice within the scope or licensure or training.
NonRigidContainerEntityType	A container having dimensions that adjust somewhat based on the amount and shape of the material placed within it.
RoleClassInvestigationSubject	An entity that is the subject of an investigation. This role is scoped by the party responsible for the investigation.
RaceAmericanIndianIroquois
RefillPharmacySupplyType	A fill against an order that has already been filled (or partially filled) at least once.
SubscriberCoveredPartyRoleType	**Description:** A role recognized through the eligibility of a party to play a subscriber for benefits covered or provided under a health insurance policy.
HospitalUnitPracticeSetting
OralInhalation	Inhalation, oral
ActRelationshipHasOption	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.
OtherPhysicianProviderHIPAA	A State licensed provider in allopathic or osteopathic medicine who performs services in a role defined independently of the scope of medical practice.
SeverityObservation	Potential values for observations of severity.
RacePacificIslandMelanesian
AddressLine	**Description:** An address line is for either an additional locator, a delivery address or a street address.
UpdateRefusalReasonCode
ClinicalResearchEventReason	**Definition:**Specifies the reason that an event occurred in a clinical research study.
VaginalFoam
LiquidLiquidEmulsion	A two-phase system in which one liquid is dispersed throughout another liquid in the form of small droplets.
InformationSensitivityPolicy	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.
RaceAmericanIndianCreek
RaceAlaskanNativeInupiatEskimo
ContextControl	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).
OptometristHIPAA	An optometrist is a person qualified by a Doctor of Optometry (O.D. ) degree, licensed by the state and practicing within the scope of that license. Optometrists examine the eyes and related structures to determine the presence of any abnormality and prescribe and adapt lenses or optical aids. They use drugs for diagnosis in all states and for treatment in some states. They do not perform surgery.
GenitourinaryRoute	Genitourinary
EntityRisk	The vocabulary table for the Entity.riskCode attribute
ActRelationshipExcerpt	The source is an excerpt from the target.
RoleStatusPending	The state representing that fact that the role has not yet become active.
PsychoanalystHIPAA	(1) A practitioner of psychoanalysis: methods of eliciting from patients their past emotional experiences and their role in influencing their current mental life, in order to discover the conflicts and mechanisms by which their pathologic mental state has been produced and to furnish hints for psychotherapeutic procedures, the method employs free association, recall and interpretation of dreams and interpretation of transference and resistance phenomena; (2) An individual who is educated with a doctor's degree in psychoanalysis or psychology, trained at an established psychoanalytic institute, and practices or adheres to the principles of psychoanalysis. Psychoanalysis is a form of psychotherapy and a system of investigation for determining and understanding mental processes, which was originally conceived by Sigmund Freud. Psychoanalysis involves the analysis and interpretation of dreams, resistances, and transferences, and uses free association and catharsis. Clinical practice requires licensure.
ActRelationshipCostTracking	Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act.
RoleClassAdjuvant
ActClassCareProvision	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.
PayorParticipationFunction	**Definition:** Set of codes indicating the manner in which payors participate in a policy or program.</
ActControlVariable	An observation form that determines parameters or attributes of an Act. Examples are the settings of a ventilator machine as parameters of a ventilator treatment act; the controls on dillution factors of a chemical analyzer as a parameter of a laboratory observation act; the settings of a physiologic measurement assembly (e.g., time skew) or the position of the body while measuring blood pressure. Control variables are forms of observations because just as with clinical observations, the Observation.code determines the parameter and the Observation.value assigns the value. While control 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).
ObservationMethodAggregate	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).
TransplacentalRoute	Transplacental
RoleStatusActive	The state representing the fact that the Entity is currently active in the Role.
RaceAmericanIndianArapaho
PrimaryDentition	Primary dentition, the first teeth to errupt and usually replaced with permanent dentition
ActClassElectronicHealthRecord	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.
ProvenanceEventCurrentState	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".
RadDiagTherPracticeSetting	A practice setting where radiology services (diagnostic or therapeutic) are provided (X12N 261QR0200N)
ROIOverlayShape	Shape of the region on the object being referenced
ActClassIncident	An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident.
RaceAmericanIndianChippewaCree
PedsClinPracticeSetting
ActClassDiet
KitEntityType	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).
RoleClassManufacturedProduct	Scoped by the manufacturer
ActExposureCode	Concepts that identify the type or nature of exposure interaction. Examples include "household", "care giver", "intimate partner", "common space", "common substance", etc. to further describe the nature of interaction.
ParticipationReferredBy	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).
ActClassSemiFowlers	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
SecurityAlterationIntegrityObservationValue
GTSAbbreviation
EasternMiwok
ActInvoiceDetailGenericCode	The detail item codes to identify charges or changes to the total billing of a claim due to insurance rules and payments.
ObservationInterpretationNormalityCriticallyAbnormal	Interpretation of a critical (or "alert") degree of abnormality. Concepts in this category are mutually exclusive, i.e., at most one is allowed.
SecurityClassificationObservationValue	Security observation values used to indicate security classification metadata.
ActClassCompositeOrder
ActDetectedIssueManagementCode	Codes dealing with the management of Detected Issue observations
ActCareProvisionCode	**Description:**The type and scope of responsibility taken-on by the performer of the Act for a specific subject of care.
IntratympanicRoute	Intratympanic
Apachean
WorkPlace
GeneralAcuteCareHospital	(X12N 282N00000N)
Yokuts
x_DeterminerInstanceKind
EntityClassCertificateRepresentation	A physical artifact that stores information about the granting of authorization.
RaceAmericanIndianShawnee
ActClassSubstitution	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.
ActClassProcedure	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.
PatientImmunizationRelatedObservationType	**Description:** Reporting codes that are related to an immunization event.
x_PhoneURLScheme	Restricts scheme to phone numbers at which a human can be reached
RoleClassCoveredParty	**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.
ActRelationshipSplitInclusiveTryOnce	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.
RoleClassAgent	An entity (player) that acts or is authorized to act on behalf of another entity (scoper).
materialForm	A value representing the state (solid, liquid, gas) and nature of the material.
RaceAmericanIndianYuman
LOINCObservationActContextAgeDefinitionCode	Identifies a type of observation that captures the age of an entity involved in an act with no implied method of determination.
ActSpecimenTreatmentCode	Set of codes related to specimen treatments
SecurityTrustAssuranceObservationValue	Values for security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.
ActTaskClinicalNoteReviewCode	A person reviews a clinical note of a given patient.
ActContainerRegistrationCode	Constrains the ActCode to the domain of Container Registration
PaymentTerms	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.
OtherTechnologistOrTechnicianProviderHIPAA	A collective term for persons with specialized training in various narrow fields of expertise whose occupations require training and skills in specific technical processes and procedures; and where further classification is deemed unnecessary by the user.
ActMoodPromise	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.
RaceAmericanIndianWinnebago
ActClassDeterminantPeptide	**Description:**A determinant peptide in a polypeptide as described by polypeptide.
ResidentialTreatmentPracticeSetting
RoleLinkStatusCancelled
IntracoronaryRoute	Intracoronary
x_SubstitutionConditionNoneOrUnconditional	Restricts substitution to effectively a yes/no decision
ParticipationCoverageTarget	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.
ActRelationshipSymptomaticRelief	Used in the diagnosis of the indicated disease.
RoleLinkIsBackupFor	This relationship indicates the source Role is available to the target Role as a backup. An entity in a backup role will be available as a substitute or replacement in the event that the entity assigned the role is unavailable. In medical roles where it is critical that the function be performed and there is a possibility that the individual assigned may be ill or otherwise indisposed, another individual is assigned to cover for the individual originally assigned the role. A backup may be required to be identified, but unless the backup is actually used, he/she would not assume the assigned entity role.
ActRelationshipHasPre-condition	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.
ActPolicyType	**Description:**Types of policies that further specify the ActClassPolicy value set.
RaceAmericanIndianSioux
WesternMuskogean
RaceWhiteMiddleEast
RoleClassHeldEntity	Entity that is currently in the possession of a holder (scoper), who holds, or uses it, usually based on some agreement with the owner.
RaceAmericanIndianIowa
OticRoute	Otic
EntericCoatedCapsule
VaginalRoute	Vaginal
ActClassClinicalTrial	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.
AcknowledgementDetailSyntaxErrorCode	Reflects errors in the syntax or structure of the communication.
EncounterAdmissionSource
Wiyot
ObligationPolicy	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.
NephClinPracticeSetting
RoleClassActiveIngredientMoietyBasis
ParticipationExposuretarget	**Description:** The entity playing the associated role is the target (contact) of exposure.
DeliveryAddressLine	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.
PackageEntityType	A material intended to hold other materials for purposes of storage or transportation
HemClinPracticeSetting
ActStatusAborted	The Act has been terminated prior to the originally intended completion.
RoleClassPreservative	A substance (player) added to a mixture (scoper) to prevent microorganisms (fungi, bacteria) to spoil the mixture.
Siouan
ActInvoiceAdjudicationPaymentGroupCode	Codes representing adjustments to a Payment Advice such as retroactive, clawback, garnishee, etc.
RoleClassICSRInvestigationSubject	**Description:** The class of the primary role by which the party is identified as the subject of an adverse event assessment.
ActRelationshipEndsAfterEndOf
RoleClassMember	A role played by an entity that is a member of a group. The group provides the scope for this role. Among other uses, groups as used in insurance (groups of covered individuals) and in scheduling where resources may be grouped for scheduling and logistical purposes.
SnodentAnteriorInterarchDeviationTypeInternational	The SNODENT identifiers for dental anterior inter-arch deviations utilized to calculate the Salzmann Malocclusion Severity Index. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
SecurityCategoryObservationType	Type of security metadata observation made about the category of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security category metadata is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "A nonhierarchical grouping of sensitive information used to control access to data more finely than with hierarchical security classification alone."
ActInpatientEncounterCode	An inpatient encounter is an encounter in which the patient is admitted to a hospital or equivalent facility.
EntityClass	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.
NorthernCaddoan
LocalRemoteControlState	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.
NursingServiceProviderHIPAA	Providers who are trained and educated to perform services in health promotion, disease prevention, acute and chronic care, and restoration of health, and health maintenance across the life span.
RoleClassConnection
SecurityTrustMechanismObservationValue	Values for security metadata observation made about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. \[Kantara Initiative\]
ActRelationshipIndependentOfTimeOf
ElectroOsmosisRoute	Electro-osmosis
EntityClassNonPersonLivingSubject
ActClassEncounter	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.
IntracavitaryRoute	Intracavitary
ObservationMeasureType	Observation values used to indicate what kind of health quality measure is used.
ActRelationshipAdjunctMitigation
EpiduralRoute	Epidural
CentralNumic
x_PayeeRelationshipRoleType	The specification of the relationship to the covered party of the payee in the case when an insurer is not directly paying the healthcare provider (as payee) but reimbursing the party that did pay them.
ActCoverageReason	**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.
NebulizationInhalation	Inhalation, nebulization
ActInvoiceInterGroupCode	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.
SubmucosalRoute	Submucosal
ActEncounterAccommodationCode	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.
AmbulatoryHealthCareFacilityHIPAA
ContextConductionStyle
LineAccessMedicalDevice	A hollow tube used to administer a substance into a vein, artery or body cavity
ActRelationshipSucceeds	**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.
HL7StandardVersionCode	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.
EthnicityHispanicSpaniard
ActAdministrativeRuleDetectedIssueCode
AccessMedicalDevice	A device used to allow access to a part of a body
RoleClassClinicalResearchInvestigator	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.
OtherServiceProviderHIPAA	Providers not otherwise classified, who perform or administer services in or related to the delivery or research of health care services, disease, and restoration of health. An individual provider who is not represented in one of the identified categories but whose data may be needed for clinical, operational or administrative processes.
ActRelationshipArrival	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.
RoleInformationSensitivityPolicy	RoleSensitivity codes are used to bind information to a Role.confidentialityCode per organizational policy. Role.confidentialityCode is defined in the RIM as "an indication of the appropriate disclosure of information about this Role with respect to the playing Entity."
ControlledSubstanceMonitoringProtocol	A monitoring program that focuses on narcotics and/or commonly abused substances that are subject to legal restriction.
SubconjunctivalRoute	Subconjunctival
DentalServiceProviderHIPAA	Broad category to identify practitioners licensed by the State who render services related the practice of dentistry. The Practice of Dentistry means the diagnosis, treatment, prescription, or operation for a disease, pain, deformity, deficiency, injury or physical condition of the human tooth, teeth, alveolar process, gums or jaws, or their dependent tissues, or an offer, undertaking, attempt to do, or holding oneself out to do any other these acts.
ObservationMeasureScoring
SubstanceAdministrationPermissionRefusalReasonCode	**Definition:**Indicates why the requested authorization to prescribe or dispense a medication has been refused.
x_EncounterParticipant	Clones using this x\_domain should have a name "encounterParticipant".
RaceAfricanAmericanAfrican
RaceAmericanIndianNorthwestTribes
StepParent	The player of the role is the spouse of the scoping person's parent and not the scoping person's natural parent.
NorthernIroquoian
SecurityTrustObservationValue	Values for security metadata observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain’s trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. \[Based on ISO IEC 10181-1 and NIST SP 800-63-2\]
DoseDurationHighDetectedIssueCode	Proposed length of therapy is longer than standard practice
CentralSalish
InterstitialRoute	Interstitial
EntityClassMaterial	Any thing that has extension in space and mass, may be of living or non-living origin.
StepChild	The player of the role is a child of the scoping person's spouse by a previous union.
CoverageRoleType	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
Aleut
ActStatusCompleted	An Act that has terminated normally after all of its constituents have been performed.
PowerOfAttorney	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.
EntityClassHolder	A type of container that can hold other containers or other holders.
RoleClassAliquot	A portion (player) of an original or source specimen (scoper) used for testing or transportation.
x_ActMoodOrdPrmsEvn	A grouping of Order, Promise and Event moods.
ActUncertainty	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.
ParticipationBaby	In an obstetric service, the baby.
RaceAmericanIndianSerrano
ActClassTrendelenburg	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
ArtificialDentition	Artificial dentition, artificial subsitutes for the natural dentition
SnodentOrthodonticTreatmentPreconditionInternational	The SNODENT identifiers for patient conditions that may preclude starting orthodontic treatment. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
ComplianceAlert
ActRelationshipHasCost	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.
DiagTherPracticeSetting	A practice setting where diagnostic procedures or therapeutic interventions are performed
AbstractChiropractersHIPAA
OralSolution
x_ActMoodIntentEvent	A constraint domain for RMIM design.
ObservationEnvironmentalIntoleranceType	Hypersensitivity resulting in an adverse reaction upon exposure to environmental conditions.
RoleClassStudent	A role played by an individual who is a student of a school, which is the scoping entity.
ActRelationshipProvidesEvidenceFor	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.
IntracerebralRoute	Intracerebral
OintmentDrugForm	A semisolid preparation intended for external application to the skin or mucous membranes.
ActRelationshipJoinExclusiveWait	Wait for any one of the branches in the set of exclusive wait branches to terminate, then discontinue all the other exclusive wait branches.
AcknowledgementCondition	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.
SerranoGabrielino
IntravascularRoute	Intravascular
MedicationObservationType
SecurityTrustAssuranceObservationType	Values for security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.
Transfer	Transfer of ownership for a product.
ActRelationshipSplitExclusiveTryOnce	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.
EntityStatusNullified	The state representing the termination of an Entity record instance that was created in error.
RoleClassEmergencyContact	An entity to be contacted in the event of an emergency.
SolidDrugForm
Utian
Liquid	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.)
GasLiquidMixture
Tepiman
PedsICUPracticeSetting
ParticipationPrimaryPerformer	The principal or primary performer of the act.
ActAdjudicationResultActionCode	Actions to be carried out by the recipient of the Adjudication Result information.
ParticipationPhysicalPerformer	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.
MilitaryHospital	A health care facility operated by the Department of Defense or other military operation.
EasternApachean
ParticipationProduct	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).
ParticipationExposureparticipation	**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.
ActStatusActiveSuspendedObsolete	\*\* none supplied \*\*
MedicationCap	Cap types for medication containers
ObservationLivingDependencyValue	Continued living in private residence requires functional and health care assistance from spouse or life partner.
ActClassVerification	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.
RaceAmericanIndianPawnee
ActRelationshipTreats
ParticipationTypeCDASectionOverride	Identifies the set of participation types context that can be blocked (overridden) at the CDA section or sub-section level of a document.
ActRelationshipTemporallyPertainsEnd
IssueFilterCode	**Description:**Indicates how result sets should be filtered based on whether they have associated issues.
x_ActMoodCompletionCriterion	**Description:**These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed, and any applicable criterion or condition over actual and potential services that must apply for an associated service to be considered.
ExtendedReleaseCapsule	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.
RegisteredDieticianHIPAA	A registered dietician (RD) is a food and nutrition expert who has successfully completed a minimum of a bachelor's degree at a US regionally accredited university or college and course work approved by The American Dietetic Association (ADA); an ADA-accredited or approved, supervised practice program, typically 6 to 12 months in length; a national examination administered by the Commission on Dietetic Registration; and continuing professional educational requirements to maintain registration.
ActAntigenInvalidReason	**Description:** Coded reasons why an antigen is considered invalid.
RoleClassFlavorAdditive	A substance (player) added to a mixture (scoper) to make it taste a certain way. In food the use is obvious, in pharmaceuticals flavors can hide disgusting taste of the active ingredient (important in pediatric treatments).
ActClassReview	The act of examining and evaluating the subject, usually another act. For example, "This prescription needs to be reviewed in 2 months."
ActSubstanceAdministrationCode	Describes the type of substance administration being performed.
ActInvoicePaymentCode
RoleStatusNullified	The state representing the termination of a Role instance that was created in error.
EquipmentAlertLevel
SnodentOralCavityAreaInternational	The SNODENT identifiers for regions in the mouth utilized to calculate the Salzmann Malocclusion Severity Index. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
IntratendinousRoute	Intratendinous
ActTaskCode	**Description:** A task or action that a user may perform in a clinical information system.
Eskimoan
ActMoodEventOccurrence	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.
RoleStatusSuspended	The state that represents a suspension of the Entity playing the Role. This state is arrived at from the "active" state.
ModelMediaType	Model media type.
ActClassExposure	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.
BuccalMucosaRoute	Buccal mucosa
ObservationInterpretationNormalityLow	Interpretation for a quantitative observation of degree of abnormality (including critical or "alert" level) below the lower limit of the reference range.
Nootkan
ActRelationshipObjective	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.
BarDrugForm
ActFinancialStatusObservationValue	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.
x_DocumentSubstanceMood	Used to enumerate the moods that a substance administration can take within the body of a clinical document.
IntralymphaticRoute	Intralymphatic
EntityClassMicroorganism	All single celled living organisms including protozoa, bacteria, yeast, viruses, etc.
SubstanceAdminSubstitutionReason
AthapaskanEyak
GeneticObservationValue	**Description:** The domain contains genetic analysis specific observation values, e.g. Homozygote, Heterozygote, etc.
OverriderParticipationFunction	This code is used to specify the exact function an actor is authorized to have in authoring a consent override.
LavageRoute	Lavage
InvoiceElementPaid	Total counts and total net amounts paid for all Invoice Groupings that were paid within a time period based on the payment date.
River
RaceAmericanIndianKlallam
IntravesicleRoute	Intravesicle
x_PersonNamePartType
ActRelationshipIsAppendage	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.
NeuropsychologistHIPAA	An individual with a doctorate degree, licensure in clinical psychology and specialized training or board certification in neuropsychology who practices or adheres to the principles of neuropsychology; a specialty within the field of psychology focusing primarily on neurobehavioral functioning.
RoleLocationIdentifiedEntity	**Description:**Describes types of identifiers other than the primary location registry identifier for a service delivery location. Identifiers may be assigned by a local service delivery organization, a formal body capable of accrediting the location for the capability to provide specific services or the identifier may be assigned at a jurisdictional level.
PharmacySupplyRequestFulfillerRevisionRefusalReasonCode	**Definition:**Indicates why the request to transfer a prescription from one dispensing facility to another has been refused.
BiotherapeuticNon-personLivingSubjectRoleType	**Description:**Animals, including fish and insects, and microorganisms which may participate as assigned entities in biotherapies.
ChronicCareFacility	(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
RoleLinkStatusPending
ActClassAccount	A financial account established to track the net result of financial acts.
OtherServiceProviderContractorHIPAA	A person who contracts to supply certain materials or do certain work for a stipulated sum; esp., one whose business is contracting work in any of the building trades. For purposes of the taxonomy, a person who contracts to complete home repairs or modifications to accommodate a health condition (e.g. wheelchair ramp, kitchen counter lowering).
HeightSurfaceAreaAlert	Proposed therapy may be inappropriate based on the patient's height or body surface area
MobilityImpaired
BuccalTablet
TimingDetectedIssueCode
ParticipationReferrer	A person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.
ManagedParticipationStatus	Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine.
ObservationInterpretationSusceptibility	Interpretations of anti-microbial susceptibility testing results (microbiology). At most one allowed.
ParticipationNon-reuseableDevice	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.
PastSubset	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.)
ControlActNullificationReasonCode	**Description:**Identifies reasons for nullifying (retracting) a particular control act. **Examples:**"Entered in error", "altered decision", etc.
RoleClassProductRelated	**Description:**A value set of product related role classCodes
AddressUse
IntracorpusCavernosumRoute	Intracorpus cavernosum
RoleClassAdditive	An ingredient (player) that is added to a base (scoper), that amounts to a minor part of the overall mixture.
IntracornealRoute	Intracorneal
ActRelationshipStartsBeforeOrConcurrentWithStartOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
PurposeOfUse	Supports communication of purpose of use at a general level.
MucousMembraneRoute	Mucous membrane
OralSuspension
ClinicalResearchObservationReason	**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.
UrinaryTractRoute	Urinary tract
ActRelationshipContainsStartOf
PharmacySupplyRequestRenewalRefusalReasonCode	**Definition:**A collection of concepts that identifies why a renewal prescription has been refused.
SecurityIntegrityProvenanceAssertedByObservationType	Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource.
CoverageParticipationFunction	**Definition:** Set of codes indicating the manner in which sponsors, underwriters, and payers participate in a policy or program.
immunizationForecastDate	Set of LOINC codes that identify the type of date that is specified within an immunization forecast step.
SignificantOtherRoleType	A person who is important to one's well being; especially a spouse or one in a similar relationship. (The player is the one who is important)
RespiratoryAndOrRehabilitativeAndOrRestorativeSpecialistOrTechnologistHIPAA	General classification identifying individuals who are trained on a specific piece of equipment or technical procedure.
Yokutsan
x_ClinicalStatementExposureMood
SnodentDentalAbnormalityInternational	The SNODENT identifiers for tooth-specific abnormalities that impact orthodontic treatment. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
RoleClassAdjacency
ActRelationshipHasContinuingObjective	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.
RoleClassInstance	An individual piece of material (player) instantiating a class of material (scoper).
ActRelationshipStartsBeforeOrConcurrentWithEndOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
WesternNumic
DeltaCalifornia
ParticipationPrimaryInformationRecipient	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.
ActAccountCode	An account represents a grouping of financial transactions that are tracked and reported together with a single balance. Examples of account codes (types) are Patient billing accounts (collection of charges), Cost centers; Cash.
LanguageAbilityProficiency	A value representing the level of proficiency in a language. *Example:*Excellent, good, fair, poor.
RaceAmericanIndianChemakuan
IntraarterialInjection	Injection, intraarterial
ActInvoiceElementCode	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.
IdentifierReliability	**Description:** The identifier was issued by the system responsible for constructing the instance.
DosageProblemDetectedIssueCode	Proposed dosage instructions for therapy differ from standard practice.
NativeEntityContiguous	NATIVE ENTITIES WITHIN THE CONTIGUOUS 48 STATES
ActRelationshipHasRisk	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.
TransportationServiceHIPAA	A provider who moves a patient, tissue specimen or equipment from one location to another.
Sahaptian
RoleClassPassive	An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity.
RouteBySite	Route of substance administration classified by site.
RoleClassActiveIngredient	A therapeutically active ingredient (player) in a mixture (scoper), where the mixture is typically a manufactured pharmaceutical.
FirstFillPharmacySupplyType	The initial fill against an order. (This includes initial fills against refill orders.)
x_DocumentEncounterMood	Used to enumerate the moods that an encounter can take within the body of a clinical document.
RaceAlaskanNativeAleutUnangan
ActRelationshipHasPart
ActInvoiceDetailGenericProviderCode	The billable item codes to identify provider supplied charges or changes to the total billing of a claim.
CodeSystem	Code systems used in HL7 standards.
IntravenousRoute	Intravenous
SecurityIntegrityConfidenceObservationType	Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
RaceAmericanIndian
RoleClassCommissioningParty	An Entity that is authorized to issue or instantiate permissions, privileges, credentials or other formal/legal authorizations.
Dentition
RigidContainerEntityType	A container having a fixed and inflexible dimensions and volume
ActRelationshipSubset	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.
Salishan
ActRelationshipHasMember
EntityNamePartTypeR2	**Description:**Indicates whether the name part is a given name, family name, prefix, suffix, etc.
WorkScheduleODH	Describes an individual's typical arrangement of working hours for an occupation.
CentralMuskogean
x_OrganizationNamePartType	A name for an organization, such as "Health Level Seven, Inc." An organization name consists only of untyped name parts, prefixes, suffixes, and delimiters.
HL7CalendarCycle
ActTaskPatientInformationReviewCode	A person (e.g., clinician, the patient herself) reviews patient information in the electronic medical record.
x_ActClassCareProvisionEncounter	**Definition:** When identifying the "request" that resulted in an encounter, there is a need to distinguish whether the "request" was a general referral (CareProvisionRequest) or a more specific ordered or scheduled encounter (PatientEncounter).
TopicalPowder
ActRelationshipTemporallyPertains
RoleLinkHasDirectAuthorityOver	The source Role has direct authority over the target role in a chain of authority.
ActTransportationModeCode	Characterizes how a transportation act was or will be carried out. *Examples:* Via private transport, via public transit, via courier.
x_SUCC_REPL_PREV
ActRelationshipLimitedBy	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.
SublingualRoute	Sublingual
RaceWhite
ActMoodIntent	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.
SecurityClassificationObservationType	Type of security metadata observation made about the classification of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security classification is defined by ISO/IEC 2382-8:1998(E/F)/ T-REC-X.812-1995 as: "The determination of which specific degree of protection against access the data or information requires, together with a designation of that degree of protection." Security classification metadata is based on an analysis of applicable policies and the risk of financial, reputational, or other harm that could result from unauthorized disclosure.
SchedulingActReason	Reasons for cancelling or rescheduling an Appointment
ExtraAmnioticRoute	Extra-amniotic
x_BillableProduct	**Description:**The billable codes selected for Clinical Product Invoices. Steward is Financial Management.
ActRelationshipEvaluatesGoal	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.
ActClassCorrelatedObservationSequences	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.
NaturalParent
IntracoronalRoute	Intracoronal (dental)
EthnicityHispanicCentralAmerican
IntramuscularInjection	Injection, intramuscular
Sibling	One person who shares a parent or parents with another.
TherapeuticProductDetectedIssueCode	Proposed therapy may interact with an existing or recent therapeutic product
UtoAztecan
RoleClassMutualRelationship	A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may be *de facto* behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children).
ActClassTransmissionExposure	**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.
TribalEntityUS	INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS
ActClassAccession	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).
SecurityDataIntegrityObservationType	Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made."
RaceAmericanIndianCalifornia
PersonalAndLegalRelationshipRoleType	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.
ActClassCluster	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
OutpatientFacilityPracticeSetting
RaceAmericanIndianChumash
PhysicianAndOrOsteopathHIPAA	A physician is a person qualified by a doctorate in medicine (M.D.) or osteopathy (D.O.), licensed by the state, and practicing within the scope of that license. A physician generally has primary responsibility for the health care of the patient. While M.D.s and D.O.s may use all accepted methods of treatment, including drugs and surgery, D.O.s place special emphasis on the body's musculoskeletal systems.
ActClassContract	An agreement of obligation between two or more parties that is subject to contractual law and enforcement.
OrganizationalHealthcareProviderHIPAA
x_ActRelationshipPertinentInfo
CompressionAlgorithm
ActTaskRiskAssessmentInstrumentCode	A person reviews a Risk Assessment Instrument report of a given patient.
StudentRoleType	Covered party to an insurance policy has coverage through full-time or part-time attendance at a recognized educational institution as defined by a particular insurance policy.
KnowledgeSubtopicObservationCode
UrethralRoute	Urethral
EntityClassGroup	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.
PolicyOrProgramCoverageRoleType	**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.
IntraepidermalRoute	Intraepidermal
EnteralRoute	Enteral
KnowledgeSubtopicObservationValue	Observation values used to indicate a knowledge subtopic of interest for which knowledge content is requested (e.g., treatment, etiology, prognosis).
ActRelationshipHasDebit	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.
PeriarticularRoute	Periarticular
CoverageLevelObservationValue	**Description:**Coded observation values for types of covered parties under a policy or program based on their personal relationships or employment status.
TopicalApplication	Topical application
ParticipationCatalyst
ManagedCarePolicy	**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.
GeneticObservationInterpretation	Codes that specify interpretation of genetic analysis, such as "positive", "negative", "carrier", "responsive", etc.
IntraabdominalRoute	Intra-abdominal
ActPatientAnnotationType	**Description:**Provides a categorization for annotations recorded directly against the patient
ActClassBattery	**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".
ClinicalResearchReason	**Definition:**Contains domains for act reasons used in clinical research.
RaceAmericanIndianPima
AmericanIndianAlaskaNativeLanguages
ResponsibleParty	The role played by a party who has legal responsibility for another party.
ActClassRecordOrganizer
RaceAmericanIndianWashoe
ECGObservationSeriesType
ActMedicationList	List of medications.
ActClassConditionNode	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
PublicHealthcareProgram	**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.
ObservationSocioEconomicStatusValue	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.
ParticipationRecordTarget	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.
IntraductalRoute	Intraductal
ModifyPrescriptionReasonType	Indicates why an existing prescription is changed.
RehabilitationCounselorHIPAA	An individual trained and educated in a systematic process of assisting persons with physical, mental, developmental, cognitive, and emotional disabilities to achieve their personal, career, and independent living goals assessment and appraisal, diagnosis and treatment planning, career (vocational) counseling, individual and group counseling interventions for adjustments to the medical and psychosocial impact of disability, case management, program evaluation and research, job analysis and placement counseling, and consultation on rehabilitation resources and technology. Certification generally requires a Master's degree with specialized courses in rehabilitation processes and technology.
AdministrationMedicalDevice	A device intended to administer a substance to a subject
x_ClinicalStatementSubstanceMood
ActIncidentCode	Set of codes indicating the type of incident or accident.
SecurityTrustAccreditationObservationValue	Values for security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework.
IntradiscalRoute	Intradiscal
ActPrivacyLaw	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.
SoftTissueRoute	Soft tissue
RoleStatusCancelled	The terminal state resulting from cancellation of the role prior to activation.
Penutian
x_ClinicalStatementEncounterMood
RoleClassTherapeuticAgent	A manufactured material (player) that is used for its therapeutic properties. The manufacturer is the scoper.
ActClassPositionCoordinate	**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.
FoamDrugForm
ActMoodDefinition	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.
InterameningealRoute	Interameningeal
LocalMarkupIgnore	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"
GIDiagTherPracticeSetting	A practice setting where GI procedures (such as endoscopies) are performed
Spouse	**Description:**A relationship between two people characterizing their "familial" relationship
SecurityTrustAgreementObservationType	Type of security metadata observation made about security requirements for a security domain. \[ISO IEC 10181-1\]
ActClassRoot	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.
RehabilitationHospital	(X12N 283X00000N)
SiouanCatawba
IntraduralRoute	Intradural
Palaihnihan
SnodentDentalUniversalNumberingSystemInternational	The SNODENT identifiers for all of the possible human teeth, both adult and adolescent. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
x_PhoneOrEmailURLScheme	Restricts scheme to e-mail or phone numbers at which a human can be reached
HealthQualityMeasureDocument
PharmacyServiceProviderHIPAA	A broad category grouping providers who render services relating to the preparation and dispensing of drugs.
ActRelationshipStartsConcurrentWithEnd	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).
ActInformationAccessContextCode	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
RoleLinkHasPart	The target Role is part of the Source Role.
BiliaryRoute	Biliary tract
ActNonObservationIndicationCode	**Description:**Concepts representing indications (reasons for clinical action) other than diagnosis and symptoms.
SouthernCaddoan
ActClaimAttachmentCategoryCode
TableCellHorizontalAlign	These values are defined within the XHTML 4.0 Table Model
ObservationInterpretation	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.
ActInvoiceDetailGenericAdjudicatorCode	The billable item codes to identify adjudicator specified components to the total billing of a claim.
IntramedullaryRoute	Intramedullary
DedicatedServiceDeliveryLocationRoleType	A role of a place that further classifies a setting that is intended to house the provision of services.
immunizationForecastStatusObservationValue	Represents the patient's status with respect to their immunization guideline as of an evaluation date.
SupplierHIPAA	A provider, other than a pharmacy, who supplies healthcare related products. The term supplier also includes pharmacies.
RoleClassSame	The "same" roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error. *Usage:* playing and scoping entities must have same classcode, but need not have identical attributes or values. *Example:* a provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.
GasSolidSpray
DentistHIPAA	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.
RaceSoutheastAlaskanIndianTsimshian
ActClassProcessStep
EntityClassCountry	The territory of a sovereign nation.
ActSupplyFulfillmentRefusalReason	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)
ActRelationshipStartsAfterStartOf	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).
NonDrugAgentEntity	Indicates types of allergy and intolerance agents which are non-drugs. (E.g. foods, latex, etc.)
AerosolDrugForm
RaceAmericanIndianMaidu
x_ClinicalStatementSupplyMood
FosterChild	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.
IntratrachealRoute	Intratracheal
DependentCoveredPartyRoleType	**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.
CoverageSponsorRoleType	**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)
PharmacistHIPAA	An individual who is licensed to prepare and sell or dispense drugs and compounds and to make up prescriptions.
ActInvoiceDetailGenericModifierCode	The billable item codes to identify modifications to a billable item charge. As for example after hours increase in the office visit fee.
KutchinHan
ActExposureLevelCode	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.
EntityClassContainer	A container of other entities.
PeriodontalRoute	Periodontal
ParticipationModeElectronicData	Participation by non-human-languaged based electronic signal
EntityDeterminerSpecificGroup	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".
CoverageEligibilityReason	**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.
GTSAbbreviationOther	**Description:**Other, more specific, abbreviations defined for the General timing Specification data type, that are specializations of one of the Base concepts.
ParticipationConsultant	An advisor participating in the service by performing evaluations and making recommendations.
ActRelationshipMitigates	The source act removes or lessens the occurrence or effect of the target act.
DietaryManagerHIPAA	A dietary manager is a trained food services professional who is charged with maintaining cost/profit objectives, purchasing foods and services for the department and supervising staff. Dietary managers are trained to understand the basic nutritional needs of clients and work in partnership with dietitians, who offer specialized nutritional expertise. The CDM certified dietary manager designation is an advanced professional credential awarded to dietary managers who have completed specific course work, have passed the national credentialing exams (including a sanitation and safety exam) and have applied for certification.
RoleClassContaminantIngredient
RaceAmericanIndianPonca
LiquidCleanser
EntityClassOrganization	A social or legal structure formed by human beings.
AdoptedChild	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.
IntravenousInjection	Injection, intravenous
Wintuan
ActRelationshipIsManifestationOf	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.
QualitySpecimenRoleType	A specimen specifically used to verify the sensitivity, specificity, accuracy or other perfomance parameter of a diagnostic test.
ActClassPublicHealthCase2	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.
RaceAmericanIndianOttawa
EyeAndVisionServiceProviderHIPAA	Broad category grouping individuals who render services related to the human eye and visual systems, but are not an allopathic or osteopathic physicians.
ActRelationshipProphylaxisOf
SpecimenRoleType
ParticipationConsumable	Target that is taken up, is diminished, and disappears in the service.
Keresan
RoleClassInactiveIngredient
IntradermalRoute	Intradermal
OromucosalRoute	Oromucosal
DispensableDrugForm
RaceAlaskanIndian
OtherActionTakenManagementCode	Order is performed as issued, but other action taken to mitigate potential adverse effects
IntralesionalRoute	Intralesional
ActListCode	Provides codes associated with ActClass value of LIST (working list)
ActRelationshipHasFinalObjective	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.
RaceAmericanIndianCahuilla
ActPaymentCode	Code identifying the method or the movement of payment instructions. Codes are drawn from X12 data element 591 (PaymentMethodCode)
RoleClassFomite	**Description:** A fomite is a non-living entity that is capable of conveying exposure agent from one entity to another. A doorknob contaminated with a Norovirus is an example of a fomite. Anyone touching the doorknob would be exposed to the virus. The scoper of the role must be the exposure agent (e.g., pathogen).
ActClassAction	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).
TopicalSolution
SecurityControlObservationValue	Security observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy, V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use, V:PrivacyMark, V:SecurityLabelMark, and V:ControlledUnclassifiedInformation used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats including, purpose of use, obligation policy, refrain policy, dissemination controls and privacy marks to which a custodian or receiver is required to comply.
Implantation	Implantation
ActFinancialTransactionCode
ActMedicalServiceCode	General category of medical service provided to the patient during their encounter.
ObservationInterpretationExpectation	Observation interpretation codes for expected results based on additional information (contraindicators) about the patient's situation.
ActPrivacyPolicy	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.
SnodentPosteriorInterarchDeviationTypeInternational	The SNODENT identifiers for dental posterior inter-arch deviations utilized to calculate the Salzmann Malocclusion Severity Index. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
EntityDeterminer	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.
ObservationHealthStatusValue	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.
ActRelationshipStartsConcurrentWith
ActClassPolypeptide	**Description:**A polypeptide resulting from the translation of a gene.
ActMoodRisk	**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.
ActClassDiagnosticImage	Class for holding attributes unique to diagnostic images.
MucosalAbsorptionRoute	Mucosal absorption
Muskogean
ActRelationshipCheckpointEnd	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).
ActClassCondition	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
ActClassSubjectBodyPosition	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
RectalRoute	Rectal
x_ActRelationshipRelatedAuthorizations
ActClassPolicy	**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
OccupationalTherapistHIPAA	An occupational therapist is a person qualified by completion of an approved program in occupational therapy, licensed by the state and practicing within the scope of that license, or where licensure does not exist, certified by the American Occupational Therapy Certification Board. An occupational therapist evaluates the self-care, work and leisure performance skills of well and disabled clients and plans and implements programs to restore, develop or maintain the task performance skills necessary for daily living and for the client's particular occupational role.
AddressRepresentationUse	**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.)
ActRelationshipStartsAfterOrConcurrentWithStartOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
ParticipationTargetSubject	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.
ActRelationshipHasQualifier
RoleClassCitizen	Citizen of apolitical entity
x_ActRelationshipExternalReference	Used to enumerate the relationships between a CDA entry and an externally referenced act.
RoleStatusNormal	The 'typical' state. Excludes "nullified" which represents the termination state of a Role instance that was created in error.
ActRelationshipHasControlVariable	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.
AbstractHealthcareProviderAgencyHIPAA	A non-facility provider that renders outpatient outreach services that are not provided at a specific location. The licensure or registration is assigned to the agency rather than to the individual practitioners as would be the case in a group practice.
AdministrativeContactRoleType	A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClassCommissioningParty.
ContextControlOverridingPropagating	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.
TriggerEventID
AuthorizationIssueManagementCode
StreetAddressLine
RoleClassContactCode
VaginalGel
ActRelationshipConcurrentWith
ExtendedReleaseSuspension
ProvenanceEventCurrentState-AS	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".
LOINCObservationActContextAgeType	**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.
ObservationDetectedIssueCode	Proposed therapy may be inappropriate or contraindicated due to conditions or characteristics of the patient
RoleStatus	Codes representing the defined possible states of an Role, as defined by the Role class state machine.
ActRelationshipTemporallyPertainsApproximates	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
SocialWorkerHIPAA	A clinical social worker is a person who is qualified by a master of Social Work (M.S.W.) degree, licensed, certified or registered by the state as a social worker and practicing within the scope of that license. A social worker provides assistance and counseling to patients and their families and dealing with social, emotional and environmental problems.
IntracardiacRoute	Intracardiac
ParticipationCustodian	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.).
USEncounterReferralSource
ActClassBoundedRoi	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).
ParticipationHolder	Participant who posses an instrument such as a financial contract (insurance policy) usually based on some agreement with the author.
OilDrugForm	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.
PlasticBottleEntityType	A bottle made of plastic
SecurityIntegrityProvenanceObservationValue
ActRelationshipRecovery	**Definition:** The source act is performed to recover from the effects of the target act.
CitizenRoleType	A role type used to qualify a person's legal status within a country or nation. **Examples:** * Full citizen * Asylum seeker * Permit card holder
x_ActMoodDocumentObservation	Used to enumerate the moods that an observation can take within the body of a clinical document.
ERPracticeSetting	The section of a health care facility for providing rapid treatment to victims of sudden illness or trauma.
RaceAmericanIndianGrosVentres
Yuman
ValidationIssue
ActClassLeftLateralDecubitus	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
Pomoan
RaceAmericanIndianAssiniboineSioux
ActIneligibilityReason	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.
RaceAmericanIndianCoushatta
IdentifierScope	**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.
RaceAsian
SuppositoryDrugForm	A solid body of various weights and shapes, adapted for introduction into the rectal, vaginal, or urethral orifice of the human body; they usually melt, soften, or dissolve at body temperature.
ActStatusObsolete	This Act instance has been replaced by a new instance.
SecurityTrustAccreditationObservationType	Type of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework.
ParticipationAncillary	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.
TransdermalPatch
ActRelationshipJoinWait	Wait for this branch to terminate.
RoleClassGuardian	Guardian of a ward
ActRelationshipHasCharge	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.
RoleClassQualifiedEntity	An entity (player) that has been recognized as having certain training/experience or other characteristics that would make said entity an appropriate performer for a certain activity. The scoper is an organization that educates or qualifies entities.
EntityStatus	Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.
IntrapleuralRoute	Intrapleural
Ethnicity	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.
ParticipationDischarger	The practitioner who is responsible for the discharge of a patient from a patient encounter.
NutritionistHIPAA	A specialist in adapting and applying food and nutrient knowledge to the solution of food and nutritional problems, the control of disease, and the promotion of health. Nutritionists perform research, instruct groups and individuals about nutritional requirements, and assist people in developing meal patterns that meet their nutritional needs; (2) A nutritionist is someone who has completed undergraduate and/or graduate training in the discipline of nutrition without necessarily meeting the academic and experience requirements to qualify for the Registered Dietitian designation.
GingivalRoute	Gingival
RoleLinkType	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.
DedicatedClinicalLocationRoleType	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.
InteractionDetectedIssueCode
ActTaskPatientDocumentationCode	A person enters documentation about a given patient.
PedsPracticeSetting
ConsenterParticipationFunction	This code is used to specify the exact function an actor is authorized to have in authoring a consent directive.
ResponseLevel	Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include
GeneticObservationMethod	A code that provides additional detail about the means or technique used to ascertain the genetic analysis. Example, PCR, Micro Array
RoleClassPatient	**Description:**A Role of a LivingSubject (player) as a recipient of health care services from a healthcare provider (scoper).
SecurityIntegrityObservationType	Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.
InvoiceElementAdjudicated	Total counts and total net amounts adjudicated for all Invoice Groupings that were adjudicated within a time period based on the adjudication date of the Invoice Grouping.
VaginalCream
ActMoodAppointment	A planned Act for a specific time and place.
BehavioralHealthAndOrSocialServiceCounselorHIPAA	A provider who is trained and educated in the performance of behavior health services through interpersonal communications and analysis. Training and education at the specialty level usually requires a master's degree and clinical experience and supervision for licensure or certification.
RoleClassStoredEntity	Relates an entity (player) (e.g. a device) to a location (scoper) at which it is normally found or stored when not used.
RoleClassHealthcareProvider	An Entity (player) that is authorized to provide health care services by some authorizing agency (scoper).
ActSuppliedItemDetectedIssueCode	Identifies types of detected issues regarding the administration or supply of an item to a patient.
ActClassFinancialContract	A contract whose value is measured in monetary terms.
ActClassObservationSeries	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.
IntrapulmonaryRoute	Intrapulmonary
ActMoodActRequest
InjectionMedicalDevice	A device intended to administer liquid into a subject via a
SecurityObservationType	Type of security metadata observation made about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used in security labels. According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator’s clearance to the target’s security label. All of the following must be true for authorization to be granted: * The security policy identifiers shall be identical, * The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and * For each security category in the target label, there shall be a security category of the same type in the initiator’s clearance and the initiator’s classification level shall dominate that of the target.
_0275a
SupplyAppropriateManagementCode	Confirmed supply action appropriate
SecurityCategoryObservationValue	Security observation values used to indicate security category metadata. V:SecurityCategoryObservationValue is the union of V:PrivacyPolicyType, V:ActPrivacyLaw, V:ActConsentDirective, V:InformationSensitivityPolicy, V:ActInformationSensitivityPolicy, V:RoleInformationSensitivityPolicy, V:EntityInformationSensitivityPolicy, and the V:ActConsentType value used to populate the SecurityCategoryObservationValue attribute in order to convey one or more nonhierarchical categories of sensitivity metadata, which are used to control access to data more finely than with hierarchical security classification alone. Could be bound R1 to a V:ActUSPrivacyPolicy in a future US Realm.
x_AccommodationRequestorRole
ParticipationUgentNotificationContact	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).
Algonquian
ContactRoleType	Types of contact for Role code "CON"
Coosan
ActBillableModifierCode	**Definition:**An identifying modifier code for healthcare interventions or procedures.
ActRelationshipAccounting	Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element.
CUI	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.
ActClassCoverage	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.
ActTaskMicrobiologyResultsReviewCode	A person reviews a list of microbiology results of a given patient.
ActObservationVerificationType	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)
x_ActReplaceOrRevise
PrescriptionDispenseFilterCode	A "helper" vocabulary used to construct complex query filters based on how and whether a prescription has been dispensed.
GeneralPurposeOfUse	Supports communication of purpose of use at a general level.
PatientProfileQueryReasonCode
ContextControlPropagating	The association propagates to any child Acts that are related via a conducting ActRelationship (refer to contextConductionInd).
OrderableDrugForm
ActTherapyDurationWorkingListCode	Codes used to identify different types of 'duration-based' working lists. Examples include "Continuous/Chronic", "Short-Term" and "As-Needed".
KnowledgeSubjectObservationValue	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).
ActMoodOption	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).
ActEmergencyEncounterCode	**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.)
RoleClassAssignedEntity	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.
x_ActClassDocumentEntryAct	The set of Act class codes allowed for the ACT class clone in the CDA Clinical Statement model. The scope of this value set are those Act class codes not otherwise covered by specific classes in the CDA Clinical Statement model and required to enable representation of Clinical Statement in CDA.
NaturalSibling	The player of the role has both biological parents in common with the scoping entity.
ActAdministrativeDetectedIssueCode	Identifies types of detectyed issues for Act class "ALRT" for the administrative and patient administrative acts domains.
RoleClassCoverageSponsor	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.
Allergy Status	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
ManagedParticipationStatusNullified	The state representing the termination of a Participation instance that was created in error.
ActRelationshipRefersTo	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.
PodiatricMedicineAndOrSurgeryServiceProviderHIPAA	Broad category grouping licensed providers who renders services related to the human foot.
QueryStatusCode	A code specifying the state of the Query.
ActBillingArrangementCode	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.
x_DocumentActMood	Used to enumerate the moods that an act can take within the body of a clinical document.
GasDrugForm	Any elastic aeriform fluid in which the molecules are separated from one another and have free paths.
ActRelationshipAdjunctCurativeIndication
Takelman
Swish	Swish
ActInformationSensitivityPolicy	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.
ActClassControlAct	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.
HL7AccommodationCode	**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.
RoleClassAdministerableMaterial	A material (player) that can be administered to an Entity (scoper).
ActClassFinancialAdjudication	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
ParticipationOrigin	The location of origin for services. May be a static building (or room therein) or a movable facility (e.g., ship).
ActMoodRecommendation	A non-mandated intent to perform an act where a level of professional responsibility is being accepted by making the proposal.
RoleClassProgramEligible	**Description:** A role played by a party that meets the eligibility criteria for coverage under a program. A program eligible may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations. **Discussion:** A program as typically government administered coverage for parties determined eligible under the terms of the program. **Note:** The party playing a program eligible is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However 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 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 party meeting eligibility criteria related to health or financial status, e.g., in the U.S., persons meeting health, demographic, or financial criteria established by state and federal law are eligible for Medicaid.
PerianalRoute	Perianal
ActRelationshipCheckpointThrough	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.
LivingSubjectProductionClass	Code indicating the primary use for which a living subject is bred or grown
IndustryClassificationSystem
DiagnosisICD9CM
ActRelationshipHasExplanation	This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition.
RelatedReactionDetectedIssueCode	Proposed therapy may be inappropriate or contraindicated because of a potential patient reaction to a cross-sensitivity related product.
ActPatientTransportationModeCode	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.
_0272	Testing to measure the minimum concentration of the antibacterial agent in a given culture medium below which bacterial growth is not inhibited.
RoleClassContinuity
RaceAlaskanNativeAleutAlutiiq
SecurityIntegrityProvenanceReportedByObservationType	Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource.
RoleClassGuarantor	A person or organization (player) that serves as a financial guarantor for another person or organization (scoper).
RaceAmericanIndianPugetSoundSalish
ParticipationVerifier	A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.
ActInvoiceRootGroupCode	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.
x_EncounterAdmissionUrgency	The urgency for starting a patient encounter. *Example:*Routine, urgent, emergency, and elective.
SnodentDentalPeriodontalProbingPositionInternational	The SNODENT identifiers for the relative positions around the tooth that are probed and measured in assessing a patient's periodontal health. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
RoleLinkReplaces	This relationship indicates that the source Role replaces (or subsumes) the target Role. Allows for new identifiers and/or new effective time for a registry entry or a certification, etc.
ActInvoiceGroupCode	Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a 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.
ParticipationDataEntryPerson	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.
SirenikskiYupik
ActRelationshipPertains	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.
Cree
ConfidentialityModifiers	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
ActClassSubjectPhysicalPosition	The spatial relationship of a subject whether human, other animal, or plant, to a frame of reference such as gravity or a collection device.
ActRelationshipCurativeIndication
Numic
EntityClassPlace	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.
ActInvoiceDetailDrugProductCode	An identifying data string for A substance used as a medication or in the preparation of medication.
EntityNamePartType
ActCredentialedCareCode	**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.
ActRelationshipSplit	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.
ActClassFinancialTransaction	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.
LotionDrugForm	The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin.
ActInvoiceDetailCode	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.
ParticipationFunction	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).
MultipartMediaType	Multipart Media Type
ActClassMonitoringProgram	An officially or unofficially instituted program to track acts of a particular type or categorization.
RoleClassHasGeneric	A special link between pharmaceuticals indicating that the target (scoper) is a generic for the source (player).
ParticipationParticipation	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.
Diegueno
RoleClassBirthplace	Relates a place (playing Entity) as the location where a living subject (scoping Entity) was born.
UNSPSC	**Description:**United Nations Standard Products and Services Classification, managed by Uniform Code Council (UCC): www.unspsc.org
MedicationOrderReleaseReasonCode	**Definition:**A collection of concepts that indicate why the prescription should be released from suspended state.
RoleLinkStatusNullified
ParticipationRemote	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."
PlaceEntityType	Types of places for EntityClass "PLC"
LoincDocumentOntologyInternational	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.
ActRelationshipEndsBeforeStartOf
ObservationActContextAgeType	**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.
ActClassOrganizationalPolicy	**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.
IntrapericardialRoute	Intrapericardial
Injection	Injection
x_ParticipationPrfEntVrf	A person that performed, contributed in recording or validating the act.
ActRelationshipConditional	Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred
SnodentDentitionStateInternational	The SNODENT identifiers for the stages of dentition an individual progresses through during a lifetime. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
OtherPhysicianOsteopathHIPAA	A physician is a person qualified by a doctorate in medicine (M.D.) or osteopathy (D.O.), licensed by the state, and practicing within the scope of that license. A physician generally has primary responsibility for the health care of the patient. While M.D.s and D.O.s may use all accepted methods of treatment, including drugs and surgery, D.O.s place special emphasis on the body's musculoskeletal systems.
PulmonaryRoute	Pulmonary
Nebulization	Nebulization
Kalapuyan
ObservationType	Identifies the kinds of observations that can be performed
RoleClassServiceDeliveryLocation	A role played by a place at which services may be provided.
ParticipationWitness	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.
x_ActStatusActiveSuspended
ActBoundedROICode	Type of bounded ROI.
EndocrinologyClinic
GTSAbbreviationHolidaysChristianRoman	Christian Holidays (Roman/Gregorian "Western" Tradition.)
EntityNamePartQualifier
IntraarticularRoute	Intraarticular
RoleClassAccess	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.
GastricRoute	Gastric
RaceAmericanIndianSeminole
TableRuleStyle	(abstract) Defines table cell rendering characteristics
ResourceGroupEntityType	Codes to characterize a Resource Group using categories that typify its membership and/or function . *Example:* PractitionerGroup
Pidgin
RoleClassActiveIngredientReferenceBasis
NameLegalUse
CalendarCycleOneLetter	One letter calendar cycle abbreviations (Temporary - remove when RoseTree is fixed)
RoleClassStabilizer	A stabilizer (player) added to a mixture (scoper) in order to prevent the molecular disintegration of the main substance.
RaceBlackOrAfricanAmerican
Tanana
Arapahoan
IntravitrealRoute	Intravitreal
OphthalmicRoute	Ophthalmic
ActRelationshipEndsAfterOrConcurrentWithStartOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
RoleClassUsedEntity	**Description:**An entity (player) that is used by another entity (scoper)
ActCoverageQuantityLimitCode	Maximum amount paid or maximum number of services/products covered; or maximum amount or number covered during a specified time period under the policy or program.
SecurityTrustCertificateObservationType	Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). \[Based on ISO IEC 10181-1\]
ActRelationshipSchedulesRequest	Associates a specific time (and associated resources) with a scheduling request or other intent.
SecurityTrustObservationType	Type of security metadata observation made about aspects of trust applicable to an IT resource (data, information object, service, or system capability). Trust applicable to IT resources is established and maintained in and among security domains, and may be comprised of observations about the domain’s trust authority, trust framework, trust policy, trust interaction rules, means for assessing and monitoring adherence to trust policies, mechanisms that enforce trust, and quality and reliability measures of assurance in those mechanisms. \[Based on ISO IEC 10181-1 and NIST SP 800-63-2\] *Usage Note:* SecurityTrustObservationType may be used as a trust attribute in a computable trust policy, trust credential, trust assertion, or trust label field in a security label and populated with trust observation values. The valued trust attributes may be used for used for authentication, authorization, and access control decisions. These may also be used to negotiate trust relationships, adjudicate or bridge trust policies, and to specify requirements for participation in a Trust Domain or for asserting compliance with a Trust Framework.
SnodentDentalFrenumRegionInternational	The SNODENT identifiers for the regions of the human frenum within the mouth. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
ActHomeHealthEncounterCode	**Definition:**Healthcare encounter that takes place in the residence of the patient or a designee
ActClassBioSequence	**Description:**A sequence of biomolecule like the DNA, RNA, protein and the like.
ActRelationshipActProvenance	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.
EntityClassManufacturedMaterial	Corresponds to the ManufacturedMaterial class
ParticipationSecondaryPerformer	A person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be.
PacificCoastAthapaskan
NationEntityType	Codes identifying nation states. Allows for finer grained specification of Entity with classcode <= NAT *Example:*ISO3166 country codes.
ParticipationInformationRecipient	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.
EmergencyMedicalServiceProviderHIPAA	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.
PharmacySupplyEventAbortReason	**Definition:**Identifies why the dispense event was not completed
URLScheme	A Universal Resource Locator (URL) is a type of telecommunications address specified as Internet standard RFC 1738 \[http://www.ietf.org/rfc/rfc1738.txt\]. The URL specifies the protocol and the contact point defined by that protocol for the resource.
ActConsentDirectiveType	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
SecurityLabelMark	Codes used for displayed Security Label tags. Supports selection of SecurityLabelMark value set with head code for e.g., rules engine policy set purposes.
ActClassTransportation	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.)
EntityInformationSensitivityPolicy	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."
ArapahoGrosVentre
BarSoapDrugForm
ActRelationshipDocuments	The source act documents the target act.
ActRelationshipICSRInvestigation	**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).
RaceAmericanIndianUmpqua
CodeIsNotValid
SurgClinPracticeSetting
ObservationMeasureCountableItems	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.
ActRelationshipDocumentHQMF	The reasons that may be used when relating a Quality Measure Document to other document types.
ObservationInterpretationProtocolInclusion	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.\]
ActClassExtract	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.
ParanasalSinusesRoute	Paranasal sinuses
ActSubstanceAdministrationImmunizationCode	The introduction of an immunogen with the intent of stimulating an immune response, aimed at preventing subsequent infections by more viable agents.
ActClassContainerRegistration	An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt
ObservationFoodIntoleranceType	Hypersensitivity resulting in an adverse reaction upon exposure to food.
ActMoodEventCriterion	A criterion or condition over service events that must apply for an associated service to be considered.
RaceAmericanIndianWampanoag
ParticipationReceiver	The person (or organization) who receives the product of an Act.
ActStatusAbortedCancelledCompleted	**Description:** The status of an assessment for indications of an abnormal condition.
ContextControlOverridingNon-propagating	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.
RoleClassInvoicePayor	The role of an organization that undertakes to accept claims invoices, assess the coverage or payments due for those invoices and pay to the designated payees for those invoices. This role may be either the underwriter or a third-party organization authorized by the underwriter. The scoping entity is the organization that underwrites the claimed coverage.
RoleClassClinicalResearchSponsor	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.
NursingServiceRelatedProviderHIPAA	Providers who are trained and educated to perform and administer services related to health promotion, disease prevention, acute and chronic care, spiritual guidance and comfort for healing and health, restoration of health and health maintenance across the life span.
RoleLinkIdentification	**Definition:** The source role provides identification for the target role. The source role must be IDENT. The player entity of the source role is constrained to be the same as the player of the target role if present. If the player is absent from the source role, then it is assumed to be the same as the player of the target role.
ActRelationshipItemsLocated	Items located
RoleStatusTerminated	The state representing the successful termination of the Role.
EntityClassPlant	A living subject from the order of plants.
CaseTransmissionMode	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.
ActInvoiceAdjudicationPaymentCode	Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee and other cost elements such as bonus, retroactive adjustment and transaction fees.
RoleClassOwnedEntity	An Entity (player) for which someone (scoper) is granted by law the right to call the material (player) his own. This entitles the scoper to make decisions about the disposition of that material.
IntracoronaryInjection	Injection, intracoronary
ActRelationshipEndsConcurrentWithStart	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).
ActRelationshipStartsBeforeEnd	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).
ActAdjudicationCode	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.
ActInformationTransferCode	**Description:** Conveyance of the type of information transfer protocol.
AlgorithmicDecisionObservationMethod	Reaching a decision through the application of an algorithm designed to weigh the different factors involved.
OrthoClinPracticeSetting
TableCellScope	These values are defined within the XHTML 4.0 Table Model
ActClassInvestigation	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.
RaceAmericanIndianMicmac
ObservationDiagnosisTypes	An observation about the presence (or absence) of a particular disease state in a subject.
ActInformationAccess	**Definition:** Consent to access healthcare information.
ActRelationshipOccurrence	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).
ActClassPublicHealthCase	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.
ActClassPosition	An observation denoting the physical location of a person or thing based on a reference coordinate system.
ActInvoiceDetailTaxCode	The billable item codes to identify modifications to a billable item charge by a tax factor applied to the amount. As for example 7% provincial sales tax.
ContextControlNonPropagating	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).
ActRelationshipSummarizedBy	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.
SwabDrugForm	A wad of absorbent material usually wound around one end of a small stick and used for applying medication or for removing material from an area.
RoleClassMaintainedEntity	An entity (player) that is maintained by another entity (scoper). This is typical role held by durable equipment. The scoper assumes responsibility for proper operation, quality, and safety.
ActRelationshipTransformation	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.)
DeviceAlertLevel	Domain values for the Device.Alert\_levelCode
RaceAmericanIndianLuiseno
EntityClassLivingSubject	Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.)
RaceAmericanIndianChoctaw
Dissolve	Dissolve
RaceAlaskanNativeAleutBristolBay
ActPharmacySupplyType	Identifies types of dispensing events
RaceAmericanIndianHoopa
x_ActFinancialProductAcquisitionCode	The method that a product is obtained for use by the subject of the supply act (e.g. patient), with financial compensation. Product examples are consumable or durable goods.
Transdermal	Transdermal
DropsDrugForm
EntityClassImagingModality	Class to contain unique attributes of diagnostic imaging equipment.
EntityNameUse
OropharyngealRoute	Oropharyngeal
RoleClassPolicyHolder	A role played by a person or organization that holds an insurance policy. The underwriter of that policy is the scoping entity. *Discussion:*The identifier of the policy is captured in 'Role.id' when the Role is a policy holder. A particular policy may cover several individuals 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.
GenderStatus	A value representing whether the primary reproductive organs of NonPersonLivingSubject are present.
IntraocularRoute	Intraocular
ActRelationshipType	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".
IntratesticularRoute	Intratesticular
CommunicationFunctionType	Describes the type of communication function that the associated entity plays in the associated transmission.
EntityClassCountyOrParish	The territory of a county, parish or other division of a state or province.
ActRelationshipJoinDetached	Detach this branch from the other branches so it will not be resynchronized with the other branches.
PlateauPenutian
ActRelationshipJoinKill	When all other concurrent branches are terminated, interrupt and discontinue this branch.
x_ActRelationshipPatientTransport	Relates a patient encounter act (source) to the transportation act (target) representing the patient"s arrival at or departure from the site of a patient encounter.
IntraluminalRoute	Intraluminal
CVDiagTherPracticeSetting	A practice setting where cardiovascular diagnostic procedures or therapeutic interventions are performed (e.g., cardiac catheterization lab, echocardiography suite)
DedicatedNonClinicalLocationRoleType	A role of a place that further classifies a setting that is intended to house the provision of non-clinical services.
x_ActStatusActiveComplete
Other	The actual value is not an element in the value domain of a variable. (e.g., concept not provided by required code system).
ActRelationshipOverlapsWith
RaceSoutheastAlaskanIndian
Algic
RaceAmericanIndianChickahominy
IntracardiacInjection	Injection, intracardiac
LabSpecimenCollectionProviders
UnorderedListStyle	Defines rendering characteristics for unordered lists
ServiceDeliveryLocationRoleType	A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered.
Rinse	Rinse
IncidentalServiceDeliveryLocationRoleType
ActStatusActiveAborted	\*\* none supplied \*\*
ActStatusSuspended	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
ObservationIssueTriggerCodedObservationType	Distinguishes the kinds of coded observations that could be the trigger for clinical issue detection. These are observations that are not measurable, but instead can be defined with codes. Coded observation types include: Allergy, Intolerance, Medical Condition, Pregnancy status, etc.
LabResultReportingProcessStepCode
ComplianceDetectedIssueCode	There may be an issue with the patient complying with the intentions of the proposed therapy
ActRelationshipEndsNearEnd	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
LabResultTriggerEvents	**Description:**Trigger Event ID as published in the standard.
RaceWhiteEuropean
ActMoodPotential
AuthorizedParticipationFunction	This code is used to specify the exact function an actor is authorized to have in a service in all necessary detail.
ActClassTopic	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.
EmployeeJobClass	A code qualifying the employment in various ways, such as, full-time vs. part time, etc.
ActRelationshipMatchesTrigger	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.
PodiatristHIPAA	A podiatrist is a person qualified by a Doctor of Podiatric Medicine (D.P.M.) degree, licensed by the state, and practicing within the scope of that license. Podiatrists diagnose and treat foot diseases and deformities. They perform medical, surgical and other operative procedures, prescribe corrective devices and prescribe and administer drugs and physical therapy.
RespiratoryTractRoute	Respiratory tract
RaceAlaskanNativeSiberianEskimo
IntrathecalRoute	Intrathecal
ActClassReverseTrendelenburg	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
ActConsentInformationAccessOverrideReason	**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.
ControlActReason	Identifies why a specific query, request, or other trigger event occurred.
ParticipationAuthenticator	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.
NursingServiceRelatedProviderTechnicianHIPAA	(1) A person with specialized training in a narrow field of expertise whose occupation requires training and is skilled in specific technical processes and procedures. (2) An individual having special skill or practical knowledge in an area, such as operation and maintenance of equipment or performance of laboratory procedures involving biochemical analyses. Special technical qualifications are normally required, though an increasing number or technicians also possess university degrees in science, and occasionally doctorate degrees. The distinction between technician and technologist in the health care field is not always clear.
RacePacificIslandPolynesian
ActRelationshipStartsWithEndsBeforeEndOf
RaceAlaskanNativeAleut
ActMedicationTherapyDurationWorkingListCode
EntityClassAnimal	A living subject from the animal kingdom.
ActStatus	Contains the names (codes) for each of the states in the state-machine of the RIM Act class.
ManagedParticipationStatusActive	The state representing the fact that the Participation is in progress.
FontStyle	(abstract) Defines font rendering characteristics
UpperChinook
ActRelationshipHasTrigger	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.
VideoMediaType	Video media type.
RacePacificIslandMicronesian
QueryRequestLimit	**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.
EntityClassPublicInstitution	An agency of the people of a state often assuming some authority over a certain matter. Includes government, governmental agencies, associations.
AutomobileInsurancePolicy	**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.
SubcutaneousRoute	Subcutaneous
IntratumorRoute	Intratumor
RaceAmericanIndianMiami
ActInvoiceElementModifier	Processing consideration and clarification codes.
ActObservationList
ActMoodResourceSlot	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.
ClaimantCoveredPartyRoleType	**Description**A role recognized through the eligibility of a party play a claimant for benefits covered or provided under an insurance policy.
RoleClassPart	An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity.
x_EncounterPerformerParticipation	Used to enumerate the ways in which a clinician can directly participate during an encounter which generates a clinical document.
IntravenousInfusion	Infusion, intravenous
AdjudicatedWithAdjustments	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).
HealthInformationTechnicianHIPAA	Preferred term for an Accredited Record Technician who is an individual with an associate's degree from an accredited college or independent study program who is skilled in analyzing health information and in examination of medical records for accuracy, reporting of patient data for reimbursement, and creation of disease registries for researchers.
MilitaryRoleType	**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
RoleLinkStatus
ActInformationCategoryCode	**Definition:**Indicates the set of information types which may be manipulated or referenced, such as for recommending access restrictions.
ActRelationshipHasStep
UnitsOfMeasureCaseSensitive	**Description:** All units of measure.
PasteDrugForm	A semisolid dosage form that contains one or more drug substances intended for topical application.
HL7UpdateMode	The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.
PhysicianHIPAA	A broad category grouping state licensed providers in allopathic or osteopathic medicine whose scope of practice is determined by education.
RaceAmericanIndianPomo
ActRelationshipPassiveImmunizationAgainst
HealthcareProviderTaxonomyHIPAA
ParticipationDonor	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.
HalfSibling	The player of the role is related to the scoping entity by sharing only one biological parent.
CervicalRoute	Cervix of the uterus
x_ActMoodDefEvn	A grouping of Definition, Event. These specific moods are used in control wrapper override acts. The domain is restricted to acts that are possible to occur or have already occurred.
ActRelationshipHasBoundedSupport	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.
_0280	Test methods designed to determine a microorganismaTMs susceptibility to being killed by an antibiotic.
LiquidSolidSuspension	A liquid preparation which consists of solid particles dispersed throughout a liquid phase in which the particles are not soluble.
Chinookan
Abenakian
Athapaskan
SnodentOrthodonticDiagnosticFeatureInternational	The SNODENT identifiers for gross patient findings that inform the course of orthodontic treatment to be performed. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
SecurityLabelMarkLabel	Codes used for displayed Security Label tags. Supports the selection of SecurityLabelMark leaf concepts for use, e.g., in security labels.
SubstanceAdminSubstitutionNotAllowedReason	Reasons why substitution of a substance administration request is not permitted.
ConditionDetectedIssueCode	Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis
ActDetectedIssueCode	Identifies types of detected issues for Act class "ALRT"
TelecommunicationCapabilities	**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.
EntityClassCityOrTown	The territory of a city, town or other municipality.
PathologyTechnicianHIPAA	An individual with knowledge of specific techniques and instruments who performs all of the routine tests in a medical laboratory and who has the ability to discriminate between similar factors that directly affect procedures and results.
PopulationInclusionObservationType	Observation types for specifying criteria used to assert that a subject is included in a particular population.
TopicalAbsorptionRoute	Topical absorption
ProcessingID	This attribute defines whether the message is part of a production, training, or debugging system.
RaceAmericanIndianCaddo
ActRelationshipStartsAfterOrConcurrentWithEndOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
RoleClassMechanicalIngredient
AcknowledgementDetailCode	A site specific problem code
NursingOrCustodialCarePracticeSetting
RoleClassIncidentalServiceDeliveryLocation	A role played by a place at which health care services may be provided without prior designation or authorization.
InhalantDrugForm
RaceAmericanIndianCheyenne
SetOperator
ReactionParticipant
RoleClassMolecularPart
ActRelationshipMaintenanceTreatment
IntraspinalRoute	Intraspinal
QueryResponse	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.
SecurityAlterationIntegrityObservationType	<pType of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource.</p>
IndividualPackageEntityType	Container intended to contain sufficient material for only one use.
RoleClassAffiliate	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.
ActRelationshipIsDerivedFrom	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.
BindingRealm	**Description:** All coded binding realms for terminology constraint context binding.
RoleClassTerritoryOfAuthority	Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction). For example, the Calgary Regional Health Authority (scoper) has authority over the territory "Region 4 of Alberta" (player) in matters of health.
Tiwa
SnodentJawTypeInternational	The SNODENT identifiers for the two jaws (mandible and maxilla). This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
ActSpecObsDilutionCode	An observation that reports the dilution of a sample.
ActClassPhenotype	**Description:**A genomic phenomenon that is expressed externally in the organism.
IDClinPracticeSetting
IntracartilaginousRoute	Intracartilaginous
RaceAlaskanNativeAleutChugach
ParticipationVia	For services, an intermediate location that specifies a path between origin an destination.
ActRelationshipStartsAfterStartofEndsAfterEndOf
ActRelationshipExcerptVerbatim	The source is a direct quote from the target.
ModifyIndicator	Indicates whether the subscription to a query is new or is being modified.
ObservationCoordinateAxisType
HumanLanguage	Codes for the representation of the names of human languages.
x_RoleClassCredentialedEntity	A role played by an entity that receives credentials from the scoping entity.
ExtracorporealCirculationRoute	Extracorporeal circulation
ActClassContainer	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.
TracheostomyRoute	Tracheostomy
ContentProcessingMode	**Description:**Identifies the order in which content should be processed.
PayorRoleType	**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.
ParenteralRoute	Parenteral
Catawba
ActStatusNullified	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.
MedicationOrderAbortReasonCode
IntraventricularRoute	Intraventricular
IntraduodenalRoute	Intraduodenal
NaturalChild	A child as determined by birth.
VerificationOutcomeValue	Values for observations of verification act results **Examples:** Verified, not verified, verified with warning.
ActRelationshipActiveImmunizationAgainst
RoleClassMolecularFeatures
ReligiousAffiliation	Assigment of spiritual faith affiliation
ActRelationshipHasContra-indication	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.
KiowaTanoan
Tsimshianic
ActProductAcquisitionCode	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.
HumanSubstanceAdministrationSite	The set of body locations to or through which a drug product may be administered.
ObservationIntoleranceType	Hypersensitivity resulting in an adverse reaction upon exposure to an agent.
EntityDeterminerDescribedGroup	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".
IntracavernosalRoute	Intracavernosal
RoleLinkStatusNormal
ActStatusNew	An Act that is in the preparatory stages and may not yet be acted upon
ActHealthInsuranceTypeCode	**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).
IntracisternalRoute	Intracisternal
EthnicityHispanic
ActRelationshipCheckpointEntry	Condition is tested once before the service is executed (IF condition THEN service).
GIClinicPracticeSetting
ActClassBioSequenceVariation	**Description:**A variation in a sequence as described by BioSequence.
MaterialEntityClassType	Types of Material for EntityClass "MAT"
CentralAlaskaYukon
IndividualHealthcareProviderHIPAA	Broad classification aggregating providers who are individual people rather than an organization.
Maiduan
ObservationNonAllergyIntoleranceType	Hypersensitivity to an agent caused by a mechanism other than an immunologic response to an initial exposure
ManagedCareOrganizationHIPAA
ActTaskMedicationListReviewCode	A person reviews a list of medication orders submitted to a given patient
ActRelationshipExacerbatredBy
ParticipationTargetDirect	Target that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.).
Pai
PrivateResidence	**Definition:** A living arrangement within a private residence for single family.
ActRelationshipStartsWithEndsAfterEndOf
ActRelationshipStartsAfterEndOf	**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.
OrganizationNameUse
ActInvoiceDetailPreferredAccommodationCode	An identifying data string for medical facility accommodations.
ActClassGenomicObservation	**Description:**An observation of genomic phenomena.
ObservationMethod	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.
ActClassJurisdictionalPolicy	**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.
x_ActRelationshipDocument	Used to enumerate the relationships between two clinical documents for document management.
TranstympanicRoute	Transtympanic
ActCoverageConfirmationCode	Response to an insurance coverage eligibility query or authorization request.
SecurityIntegrityProvenanceAssertedByObservationValue
PrivacyMark	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.
ActRelationshipEndsBeforeEnd	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).
SinusUnspecifiedRoute	Sinus, unspecified
AmnioticFluidSacRoute	Amniotic fluid sac
RetrobulbarRoute	Retrobulbar
Instillation	Instillation
Compartment	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."
MississippiValley
FamilyMember	A relationship between two people characterizing their "familial" relationship
RoleClassPayee	The role of an organization or individual designated to receive payment for a claim against a particular coverage. The scoping entity is the organization that is the submitter of the invoice in question.
RoleClassUnderwriter	A role played by a person or an organization. It is the party that 1. accepts fiscal responsibility for insurance plans and the policies created under those plans; 2. administers and accepts fiscal responsibility for a program that provides coverage for services to eligible individuals; and/or 3. has the responsibility to assess the merits of each risk and decide a suitable premium for accepting all or part of the risk. If played by an organization, this role may be further specified by an appropriate RoleCode. *Example:* 1. A health insurer; 2. Medicaid Program; 3. Lloyd's of London
Ritwan
Delawaran
RoleClassColorAdditive	A substance (player) influencing the optical aspect of material (scoper).
SecurityPolicy	Types of security policies that further specify the ActClassPolicy value set. **Examples:** * encrypt * prohibit redisclosure without consent directive
ActProcedureCodeCCI
ActClassDocument	Specialization of Act to add the characteristics unique to document management services.
ActSubstanceAdminSubstitutionCode
Loan	Temporary supply of a product without transfer of ownership for the product.
MissouriRiver
CompliancePackageEntityType	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.
TransferActReason	The explanation for why a patient is moved from one location to another within the organization
ResponseModality	Defines the timing and grouping of the response instances.
ActRelationshipStartsDuring
AcknowledgementDetailNotSupportedCode	Refelects rejections because elements of the communication are not supported in the current context.
RoleClassSubscriber	**Description:** A role played by a person covered under a policy based on association with a sponsor who is the policy holder, and whose association may provide for the eligibility of dependents for coverage. **Discussion:** The policy holder holds the contract with the policy or program underwriter. The subscriber holds a certificate of coverage under the contract. In legal proceedings concerning the policy or program, the terms of the contract takes precedence over the terms of the certificate of coverage if there are any inconsistencies. **Note:** The party playing the role of a subscriber is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a subscriber may make a claim under a policy, e.g., a subscriber under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party. In the case of a subscriber making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the subscriber has filed a claim for services covered under the health insurance policy. **Example:** An employee or a member of an association.
DiseaseProgram	**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.
ActMoodGoal	**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.
RaceAmericanIndianPassamaquoddy
ActMonitoringProtocolCode	Identifies types of monitoring programs
CoverageLimitObservationValue	**Description:**Coded observation values for coverage limitations, for e.g., types of claims or types of parties covered under a policy or program.
NieceNephew	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.
CreditCard
HealthcareServiceLocation	A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the 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. This valu set is aavailalbe from VSAC at https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.1.11.20275/expansion/Latest
PatchDrugForm	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.
ActMoodExpectation	**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.
IontophoresisRoute	Iontophoresis
ParticipationExposuresource	**Description:**The entity playing the associated role is the source of exposure.
SaukFoxKickapoo
RoleClassResearchSubject	**Definition:**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 experimental portion of the design.
ActClassObservation	**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
ActRelationshipUpdatesCondition	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.
RaceAmericanIndianApache
OralCapsule
RespiratoryAndOrRehabilitativeAndOrRestorativeProviderHIPAA	A provider who is trained and educated to perform services related to respiratory care, physical therapy, occupational therapy, rehabilitation and restorative services and may be licensed, certified or practice within the scope of training.
SouthernAlaska
ActClassCategory	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.
ActRelationshipOutcome	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
RadiologicTechnologistHIPAA	An individual who is trained and qualified in the \[art and science of\] use of both ionizing and non-ionizing radiation for the purposes of diagnostic medical imaging, interventional procedures and therapeutic treatment.
ActStatusNormal	Encompasses the expected states of an Act, but excludes "nullified" and "obsolete" which represent unusual terminal states for the life-cycle.
CUILabel	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.
DoseIntervalDetectedIssueCode	Proposed dosage interval/timing differs from standard practice
RoleClassNamedInsured	**Description:** A role played by a party to an insurance policy to which the insurer agrees to indemnify for losses, provides benefits for, or renders services. A named insured may be either a person, non-person living subject, or an organization, or a group of persons, non-person living subjects, or organizations. **Discussion:** The coded concept NAMED should not be used where a more specific child concept in this Specializable value set applies. In some cases, the named insured may not be the policy holder, e.g., where a policy holder purchases life insurance policy in which another party is the named insured and the policy holder is the beneficiary of the policy. **Note:** The party playing the role of a named insured is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a named insured may make a claim under a policy, e.g., e.g., a party that is the named insured and policy holder under a comprehensive automobile insurance policy may become the claimant for coverage under that policy e.g., if injured in an automobile accident and there is no liable third party. In the case of a named insured making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that a named insured has filed a claim for a loss. **Example:** The named insured under a comprehensive automobile, disability, or property and casualty policy that is the named insured and may or may not be the policy holder.
NailRoute	Nail
RaceAmericanIndianUte
Audiologist
x_ActStatusPrevious	**Description:**Cancelled, nullified and obsolete .
EasternAlgonquin
IntraesophagealRoute	Intraesophageal
StepSibling	The player of the role is a child of the scoping person's stepparent.
Ambulance
QualityMeasureSectionType	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.
ObservationAssetValue	Codes specifying asset indicators used to assess or establish eligibility for coverage under a policy or program.
ActClassDisciplinaryAction	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:*
ActInvoiceDetailClinicalProductCode	An identifying data string for healthcare products.
SubstanceAdminGenericSubstitution	Substitution occurred or is permitted with another product in the same generic ingredient.
RaceAmericanIndianShoshonePaiute
RaceAlaskanNativeEskimo
ActClassWorkingList	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.
JejunumRoute	Jejunum
ActRelationshipAuthorizedBy	A relationship in which the target act authorizes or certifies the source act.
Chimakuan
IntramuscularRoute	Intramuscular
RoleClassPhysician
IntrauterineRoute	Intrauterine
ContainerSeparator	A material in a blood collection container that facilites the separation of of blood cells from serum or plasma
x_PhysicalVerbalParticipationMode	Restricts participation to either physical or verbal
ActMoodRequest	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.
ObservationAlert
GelDrugForm	A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid.
RaceAmericanIndianCherokee
RoleClassDedicatedServiceDeliveryLocation	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."
TableCellVerticalAlign	These values are defined within the XHTML 4.0 Table Model
SecurityObservationValue	Observation values used to indicate security observation metadata.
UnderwriterParticipationFunction	**Definition:** Set of codes indicating the manner in which underwriters participate in a policy or program.
LivingArrangement	A code depicting the living arrangements of a person
IntrathoracicRoute	Intrathoracic
AskedButUnknown	Information was sought but not found (e.g., patient was asked but didn't know)
ActRelationshipInterferedBy
ObservationCategory	High level observation categories for the general type of observation being made. *Steward:* OO WG
USEncounterDischargeDisposition
ObservationLivingSituationValue	Code specifying observations related to living situation for a person in a private residence.
RoleClassSigningAuthorityOrOfficer	The role of a person (player) who is the officer or signature authority for of a scoping entity, usually an organization (scoper).
ActClassSpecimenCollection	A procedure for obtaining a specimen from a source entity.
SnodentCraniofacialAnomalyInternational	The SNODENT identifiers for the most common craniofacial anomalies that may influence the course of orthodontic treatment to be performed. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
AcknowledgementDetailType	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:*
ActMoodCriterion	A criterion or condition over actual and potential services that must apply for an associated service to be considered. Matches records any ActMoodCompletionTrack moods.
NasalRoute	Nasal
ActRelationshipStartsBeforeStartOfEndsWith
RoleClassNurse
GregorianCalendarCycle
UPC	**Description:**Universal Product Code is one of a wide variety of bar code languages widely used in the United States and Canada for items in stores.
Irrigation	Irrigation
OtherServiceProviderSpecialistHIPAA	An individual educated and trained in an applied knowledge discipline used in the performance of work at a level requiring knowledge and skills beyond or apart from that provided by a general education or liberal arts degree.
MedOncClinPracticeSetting
ActCodeProcessStep
RoleClassExposedEntity	A role played by an entity that has been exposed to a person or animal suffering a contagious disease, or with a location from which a toxin has been distributed. The player of the role is normally a person or animal, but it is possible that other entity types could become exposed. The role is scoped by the source of the exposure, and it is quite possible for a person playing the role of exposed party to also become the scoper a role played by another person. That is to say, once a person has become infected, it is possible, perhaps likely, for that person to infect others. Management of exposures and tracking exposed parties is a key function within public health, and within most public health contexts - exposed parties are known as "contacts."
IntrabronchialRoute	Intrabronchial
RoleClassEmployee	A relationship between a person or organization and a person or organization formed for the purpose of exchanging work for compensation. The purpose of the role is to identify the type of relationship the employee has to the employer, rather than the nature of the work actually performed. (Contrast with AssignedEntity.)
VeterinarianHIPAA	A doctor of veterinary medicine, trained and authorized to practice veterinarian medicine and surgery.
StatusRevisionRefusalReasonCode	Indicates why the act revision (status update) is being refused.
ExposureMode	Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.
SecurityIntegrityObservationValue
SkinRoute	Skin
ParticipationInformationGenerator	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).
EntityClassChemicalSubstance	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.
SpeechAndOrLanguageAndOrHearingServiceSpecialistOrTechnologistHIPAA	General classification identifying individuals who are trained on a specific piece of equipment or technical procedure.
x_DocumentProcedureMood	Used to enumerate the moods that a procedure can take within the body of a clinical document.
x_RoleClassCoverageInvoice	An abstract domain that encompasses the roles involved in submitting, responding to and managing invoices or claims for health care coverage.
Prosthodontics
Hokan
PowderDrugForm	An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use.
MaterialDangerInflammable	Material is highly inflammable and in certain mixtures (with air) may lead to explosions. Keep away from fire, sparks and excessive heat.
RaceAmericanIndianChinook
ActClassSpecimenTreatment	A procedure or treatment performed on a specimen to prepare it for analysis
ActRelationshipRelievedBy
Country2	Countries of the world. ISO 3166, part 1, alpha-2 set.
ActPriorityCallback	Filler should contact the placer (or target) to schedule the service. (Was "C" in HL7 version 2.3's TQ-priority component.)
EducationLevel
x_ParticipationEntVrf	A person that contributed to recording or validating the act.
BodySurfaceRoute	Body surface
ActRelationshipImmunizationAgainst
ActCredentialedCareProvisionPersonCode	**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.
SusceptibilityObservationMethodType	**Description:**Test methods designed to determine a microorganism’s susceptibility to an antibiotic.
EntityDeterminerDetermined	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.
IntragastricRoute	Intragastric
RaceAmericanIndianPeoria
x_ActInvoiceDetailPreferredAccommodationCode	The billable codes selected for use for Preferred Accommodation Invoices. Steward is Financial Management.
Infusion	Infusion
ActUSPrivacyLaw	***Deprecation Comment:*** Content moved to ActCode, and is now represented in value set ActPrivacyLaw.
VaginalOintment
Conditional	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.
HL7ITSVersionCode	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.
OrganizationIndustryClassNAICS
RaceSoutheastAlaskanIndianTlingit
Confidentiality	Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".
PostalAddressUse
RoleClassLicensedEntity	A relationship in which the scoper certifies the player ( e. g. a medical care giver, a medical device or a provider organization) to perform certain activities that fall under the jurisdiction of the scoper (e.g., a health authority licensing healthcare prlviders, a medical quality authority certifying healthcare professionals,)
RoleClassMolecularBond
ActClassCdaLevelOneClinicalDocument	A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)
ActRelationshipEndsBeforeOrConcurrentWithEndOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
ObservationLivingExpenseValue	Codes specifying living expense indicators used to assess or establish eligibility for coverage under a policy or program.
EntityStatusInactive	**Definition:** The state representing the fact that the entity is inactive.
RaceHawaiianOrPacificIsland
RaceAmericanIndianCupeno
GeneticObservationType	**Description:** Identifies the kinds of genetic observations that can be performed.
ActInvoiceAdjudicationPaymentSummaryCode	Codes representing a grouping of invoice elements (totals, sub-totals), reported through a Payment Advice or a Statement of Financial Activity (SOFA). The code can represent summaries by day, location, payee, etc.
EntityStatusActive	The state representing the fact that the Entity record is currently active.
RoleClassCaseSubject	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)
Cahitan
SnodentDentalToothFurcationSiteInternational	The SNODENT identifiers for the relative location of a human tooth root that is being observed for furcation. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
Inhalation	Inhalation
SecurityTrustMechanismObservationType	Type of security metadata observation made about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. \[Kantara Initiative\]
RoleClassHealthChart	The role of a material (player) that is the physical health chart belonging to an organization (scoper).
x_BasicConfidentialityKind	**Description:** Used to enumerate the typical confidentiality constraints placed upon a clinical document. *Usage Note:*x\_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.
RelationalOperator	Identifies common relational operators used in selection criteria.
ActInvoiceOverrideCode	Includes coded responses that will occur as a result of the adjudication of an electronic invoice at a summary level and provides guidance on interpretation of the referenced adjudication results.
DocumentStorageActive	A storage status in which a document is available on-line.
ExtendedReleaseTablet	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.
CardiologySpecialistOrTechnologistHIPAA	An allied health professional who performs diagnostic examinations at the request or direction of a physician in one or more of the following three areas: invasive cardiology, noninvasive cardiology, and noninvasive peripheral vascular study. Cardiovascular technologists are one type of allied health professional for which the Committee on Allied Health Education and Accreditation has accredited education programs.
InhalerMedicalDevice	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.
AudioMediaType	Audio media type.
ActRelationshipJoin	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.
UrinaryBladderRoute	Urinary bladder
GTSAbbreviationHolidays	Holidays
PsychologistHIPAA	An individual who specializes in psychological research, testing, and/or therapy. Psychology is the branch of science that deals with mental processes and behavior, composed of the following major fields: abnormal, clinical, comparative, counseling, developmental, educational, engineering, experimental, industrial, learning, motivation, perception, personality, physiological, psychometrics, school, and social psychology.
ActSpecObsVolumeCode	An observation that reports the volume of a sample.
Flush	Flush
Charset	Internet Assigned Numbers Authority (IANA) Charset Types
InteriorSalish
ActRelationshipCheckpointExit	Condition is a loop checkpoint, i.e. it is a step of an activity plan and, if negative causes the containing loop to exit.
LogicalObservationIdentifierNamesAndCodes	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
RaceAmericanIndianComanche
x_ClinicalStatementObservationMood
ParticipationBeneficiary	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.
x_ActRelationshipEntryRelationship	Used to enumerate the relationships between two CDA entries.
SublesionalRoute	Sublesional
InuitInupiaq
x_ActOrderableOrBillable
PartialCompletionScale
ActClassScopeOfPracticePolicy	**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.
ActRelationshipEndsNearStarts	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
ActClassOverlayRoi	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.
RheumClinPracticeSetting
DoseDurationLowDetectedIssueCode	Proposed length of therapy is shorter than that necessary for therapeutic effect
SecurityTrustCertificateObservationValue	Values for security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). \[Based on ISO IEC 10181-1\]
ActRelationshipAdjunctiveTreatment
ActConsentType	**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.
VerificationMethod
x_ActMoodDefEvnRqoPrmsPrp
ScalpRoute	Scalp
RoleClassIsSpeciesEntity	Relates a specialized material concept (player) to its generalization (scoper).
NasalInhalation	Inhalation, nasal
IntratubularRoute	Intratubular
EthnicityHispanicSouthAmerican
RoleLinkRelated	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:*
AudiologistHIPAA	(1) A specialist in evaluation, habilitation and rehabilitation of those whose communication disorders center in whole or in part in hearing function. Audiologists are autonomous professionals who identify, assess, and manage disorders of the auditory, balance and other neural systems. Audiologists provide audiological (aural) rehabilitation to children and adults across the entire age span. Audiologists select, fit and dispense amplification systems such as hearing aids and related devices. (2) An audiologist is a person qualified by a master's degree in audiology, licensed by the state, where applicable, and practicing within the scope of that license. Audiologists evaluate and treat patients with impaired hearing. They plan, direct and conduct rehabilitative programs with audiotry substitutional devises (hearing aids) and other therapy.
ActRelationshipReferencesOrder	Relates either an appointment request or an appointment to the order for the service being scheduled.
AuthorizedReceiverParticipationFunction	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.
ActRelationshipHasBaseline
IntrasternalRoute	Intrasternal
CodeSystemType	How a code system is maintained by HL7
CompositeMeasureScoring	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
RaceAmericanIndianLongIsland
PhysicalTherapistHIPAA	(1) Physical therapists are health care professionals who evaluate and treat people with health problems resulting from injury or disease. PT's assess joint motion, muscle strength and endurance, function of heart and lungs, and performance of activities required in daily living, among other responsibilities. Treatment includes therapeutic exercises, cardiovascular endurance training, and training in activities of daily living. (2) A physical therapist is a person qualified by an accredited program in physical therapy, licensed by the state, and practicing within the scope of that license. Physical therapists treat disease, injury, or loss of a bodily part by physical means, such as the application of light, heat, cold, water, electricity, massage and exercise. They develop treatment plans based upon each patient's strengths, weaknesses, range of motion and ability to function. (3) A health professional who specializes in physical therapy- the health care field concerned primarily with the treatment of disorders with physical agents and methods, such as massage, manipulation, therapeutic exercises, cold, heat (including short-wave, microwave, and ultrasonic diathermy), hydrotherapy, electric stimulation and light to assist in rehabilitating patients and in restoring normal function after an illness or injury.
ChiropractersHIPAA	A provider qualified by a Doctor of Chiropractic (D.C.), licensed by the State and who practices chiropractic medicine -that discipline within the healing arts which deals with the nervous system and its relationship to the spinal column and its interrelationship with other body systems.
ImmunizationObservationType	**Description:** Indicates the valid antigen count.
IntraperitonealRoute	Intraperitoneal
DocumentStorage	Identifies the storage status of a document.
ActRelationshipDocumentProvenance	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.
x_MedicationOrImmunization
ManagedParticipationStatusNormal	The 'typical' state. Excludes "nullified" which represents the termination state of a participation instance that was created in error.
RoleClassBase	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.
ApplicationMediaType	Application specific media type.
HealthInformationSpecialistOrTechnologistHIPAA	An individual with a high school diploma, on-the-job experience and coding education from seminars or college classes who passes a national certification examination in either inpatient and outpatient facility services coding, or physician services coding.
x_ActMoodRequestEvent
ActProgramTypeCode	**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.
RaceAmericanIndianSacFox
ActCredentialedCareProvisionProgramCode	**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.
ActRelationshipStartsNearEnd	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
ActTaskOrderEntryCode
ActInsuranceTypeCode	**Definition:** Set of codes indicating the type of insurance policy. Insurance, in law and economics, is a form of risk management primarily used to hedge against the risk of potential financial loss. Insurance is defined as the equitable transfer of the risk of a potential loss, from one entity to another, in exchange for a premium and duty of care. A policy holder is an 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.
RoleClassSubstancePresence	The presence of an bio-chemical entity (substance) at a location or environment, such as an ingredient in a mixture, molecular part of a complex, a located entity at a cellular structure, or content of a container, such as a vesicle.
ParticipationTargetDevice	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.
TextMediaType	For any text
ObservationSequenceType
CardiologyTechnicianHIPAA	An individual who has knowledge of specific techniques, instruments, and equipment required in performing specific cardiovascular/peripheral vascular diagnostic procedures.
PathologySpecialistOrTechnologistHIPAA	(1) An individual educated and trained in clinical chemistry, microbiology or other biological sciences; and in gathering data on the blood, tissues, and fluids in the human body. Tests and procedures performed or supervised center on major areas of hematology, microbiology, immunohematology, immunology, clinical chemistry and urinalysis. Education and certification requires the equivalent of an associate degree and alternative combinations of accredited training and experience. (2) A specially trained individual who works under the direction of a pathologist, other physician, or scientist, and performs specialized chemical, microscopic, and bacteriological tests of human blood, tissue, and fluids. Also known as medical technologists, they perform and supervise tests and procedures in clinical chemistry, immunology, serology, bacteriology, hematology, parasitology, mycology, urinalysis, and blood banking.
Country	Countries of the world. ISO 3166, part 1, alpha-3 set.
ParticipationSpecimen	The subject of non-clinical (e.g. laboratory) observation services is a specimen.
ActRelationshipEndsAfterStartOf
ActCoverageAuthorizationConfirmationCode	Indication of authorization for healthcare service(s) and/or product(s). If authorization is approved, funds are set aside.
ActStatusHeld	An Act that is still in the preparatory stages has been put aside. No action can occur until the Act is released.
ReactionDetectedIssueCode	Proposed therapy may be inappropriate or contraindicated based on the potential for a patient reaction to the proposed product
IndividualInsuredCoveredPartyRoleType	**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.
IrrigationSolution	A sterile solution intended to bathe or flush open wounds or body cavities; they're used topically, never parenterally.
CardClinPracticeSetting
ActRelationshipFulfills	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.
Nadene
ReactivityObservationInterpretation	Interpretations of the presence and level of reactivity of the specified component / analyte with the reagent in the performed laboratory test.
SecurityIntegrityStatusObservation	Security observation values used to indicate security integrity status metadata.
RouteOfAdministration	The path the administered medication takes to get into the body or into contact with the body.
RaceAlaskanIndianAthabascan
ObservationInterpretationOustsideThreshold	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.\]
RoleClassContent	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.
RaceAlaskanNativeAleutKoniag
SponsorParticipationFunction	**Definition:** Set of codes indicating the manner in which sponsors participate in a policy or program. NOTE: use only when the Sponsor is not further specified with a SponsorRoleType as being either a fully insured sponsor or a self insured sponsor.
DurableMedicalEquipmentAndOrMedicalSupplySupplierHIPAA	A supplier of medical equipment such as respirators, wheelchairs, home dialysis systems, or monitoring systems, that are prescribed by a physician for a patient's use in the home and that are usable for an extended period of time.
PersonalRelationshipRoleType	Types of personal relationships between two living subjects. *Example:*Parent, sibling, unrelated friend, neighbor
OralTablet
ActRelationshipHasGoal	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.
WesternMiwok
ActClassSupine	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
ActRelationshipEndsConcurrentWith
RoleClassNotaryPublic
AdministrableDrugForm	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:*
RoleClassSpecimen	A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen.
ActRelationshipUses
RoleClassLocatedEntity	Relates an entity (player) to a location (scoper) at which it is present in some way. This presence may be limited in time.
MemberRoleType	A role type that is used to further qualify an entity playing a role where the role class attribute is set to RoleClassMember.
ActClassInformation	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.
ParticipationLegalAuthenticator	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.
ListStyle	Defines list rendering characteristics
SpeechAndOrLanguageAndOrHearingServiceProviderHIPAA	A provider who renders services to improve communicative skills of people with language, speech and hearing impairments.
ActClassStandardOfPracticePolicy	**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.
x_ClinicalStatementProcedureMood
BottleEntityType	A container, typically rounded, either glass or plastic with a narrow neck and capable of storing liquid.
x_ActBillableCode
QueryPriority	Identifies the time frame in which the response is expected.
ActClassInform	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.
SecurityTrustFrameworkObservationValue	Values for security metadata observation made about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. \[Kantara Initiative\]
ActClassSupply	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.
CodingRationale	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.
AssignedNonPersonLivingSubjectRoleType	**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
ObservationInterpretationExceptions	Technical exceptions resulting in the inability to provide an interpretation. At most one allowed. Does not imply normality or severity.
HumanActSite	An anatomical location on a human which can be the focus of an act. *OpenIssue:* This value set was approved for **deletion** in November 2008, and was deleted at release \#762. Subsequently, however, it was found that this deletion caused the legacy software embedded in the RMIM Designer in Visio to fail to show appropriate options for concepts in the subject area of this value set. For that reason, the value set was **re-added in releasse 813 and DEPRECATED from general use** at the same time. This value set should be deleted as soon as it is no longer required to support of the legacy software.
ActRelationshipBlocks	**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.
PeriduralRoute	Peridural
AgeGroupObservationValue	Observation values used to indicate the age group of a person in terms of age group concept codes.
CalendarCycle
SiblingInLaw	The player of the role is: (1) a sibling of the scoping person's spouse, or (2) the spouse of the scoping person's sibling, or (3) the spouse of a sibling of the scoping person's spouse.
ActRelationshipDiagnosis
RoleClassChild	The player of the role is a child of the scoping entity, in a generic sense.
GreatGrandparent	The player of the role is a parent of the scoping person's grandparent.
RegisteredNurseHIPAA	(1) A registered nurse is a person qualified by graduation from an accredited nursing school (depending upon schooling, a registered nurse may receive either a diploma from a hospital program, an associate degree in nursing (A.D.N.) or a Bachelor of Science degree in nursing (B.S.N.), who is licensed or certified by the state, and is practicing within the scope of that license or certification. R.N.'s assist patient in recovering and maintaining their physical or mental health. They assist physicians during treatments and examinations and administer medications. (2) A provider who is trained and educated in a formal nursing education program at an accredited school of nursing, passes a national certification examination, and is licensed by the state to practice nursing. The individual provides nursing services to patients or clients in areas such as health promotion, disease prevention, acute and chronic care and restoration and maintenance of health across the life span.
ObservationCoordinateSystemType
ActRelationshipPosting	Expresses values for describing the relationship between a FinancialTransaction and an Account.
ContextControlAdditivePropagating	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.
DietaryAndOrNutritionalServiceProviderHIPAA	Broad category defining practitioners who help prevent and treat illness by promoting healthy eating habits, scientifically evaluating diets and suggesting modifications. They may also assess the nutritional needs of patients, develop and implement nutritional care plans.
Caddoan
ActClassSitting	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
x_ActRelationshipEntry	Used to enumerate the relationships between a CDA section and its contained entries.
SCDHEC-GISSpatialAccuracyTiers	**Description:** The South Carolina Department of Health and Environmental Control GIS Spatial Data Accuracy Tiers have been derived from the National Standard for Spatial Data Accuracy as a means to categorize the accuracy of spatial data assignment utilizing a variety of tools for capturing coordinates including digitizers, geocoding software and global positioning system devices.
ActMoodAppointmentRequest	A request for the booking of an appointment.
EntityNamePartQualifierR2	**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.
ActFieldEncounterCode	**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.
RaceAmericanIndianChippewa
PharmacySupplyEventStockReasonCode
ActClassExpressionLevel	**Description:**An expression level of genes/proteins or other expressed genomic entities.
ContextControlAdditive	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.
HospitalPracticeSetting	An acute care institution that provides medical, surgical, or psychiatric care and treatment for the sick or the injured.
CecostomyRoute	Cecostomy
x_ClinicalStatementActMood
ActMoodPermissionRequest	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:*
ActRelationshipHasValue
LacrimalPunctaRoute	Lacrimal puncta
RoleLinkStatusCompleted
ImageMediaType	Image media type.
ActRelationshipCoveredBy	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.
ActClassProne	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
EyeAndVisionServiceProviderTechnicianAndOrTechnologistHIPAA	A broad category grouping different kinds of technologists and technicians. See individual definitions.
RaceAmericanIndianYurok
MultiUseContainerEntityType	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.)
EntityClassFood	Naturally occurring, processed or manufactured entities that are primarily used as food for humans and animals.
PhysicianAssistantHIPAA	A physician assistant is a person who has successfully completed an accredited education program for physician assistant, is licensed by the state and is practicing within the scope of that license. Physician assistants are formally trained to perform many of the routine, time-consuming tasks a physician can do. In some states, they may prescribe medications. They take medical histories, perform physical exams, order lab tests and x-rays, and give inoculations. Most states require that they work under the supervision of a physician.
RoleClassPartitive	An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity.
ActRelationshipEndsBeforeOrConcurrentWithStartOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
ActRelationshipHasReferenceValues	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.
ActRelationshipSequel	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.
RaceAmericanIndianEasternTribes
RoleClassContact	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.
EntityClassDevice	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.
ActRelationshipTemporallyPertainsStart
RaceAmericanIndianTohonoOOdham
ActRelationshipHasGeneralization	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).
UrinaryBladderIrrigation	Irrigation, urinary bladder
TherapyAppropriateManagementCode	Confirmed drug therapy appropriate
Douche	Douche
RoleClassPersonalRelationship	Links two people in a personal relationship. The character of the relationship must be defined by a PersonalRelationshipRoleType code. The player and scoper are determined by PersonalRelationshipRoleType code as well.
BlisterPackEntityType	A bubblepack. Medications sealed individually, separated into doses.
EncounterSpecialCourtesy	A code identifying special courtesies extended to the patient. For example, no courtesies, extended courtesies, professional courtesy, VIP courtesies.
x_ActMoodRqoPrpAptArq
DoseHighDetectedIssueCode	Proposed dosage exceeds standard practice
x_AdverseEventCausalityAssessmentMethods	Value set provides methods used to assess the causality of adverse events. New codes should not be added to the domain without first checking with its steward - the Regulated Clinical Research Information Management (RCRIM) technical committee.
RoleLinkStatusActive
RoleClassCredentialedEntity	A role played by an entity that receives credentials from the scoping entity.
TabletDrugForm	A solid dosage form containing medicinal substances with or without suitable diluents.
ParticipationDestination	The destination for services. May be a static building (or room therein) or a movable facility (e.g., ship).
ActRelationshipReason	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.
VaccineManufacturer	The manufacturer of a vaccine.
HealthCareCommonProcedureCodingSystem
ProvenanceEventCurrentState-DC	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".
EmploymentStatusUB92
ActInsurancePolicyCode	Set of codes indicating the type of insurance policy or other source of funds to cover healthcare costs.
Iroquoian
OtherTechnologistOrTechnicianHIPAA	General classification identifying individuals trained on specific equipment and technical procedures in one of a collection of miscellaneous healthcare disciplines.
Unknown	A proper value is applicable, but not known.
ActRelationshipDuring
RoleClassOntological	A relationship in which the scoping Entity defines or specifies what the playing Entity is. Thus, the player's "being" (Greek: ontos) is specified.
x_ActClassDocumentEntryOrganizer
ManagedParticipationStatusCompleted	The terminal state representing the successful completion of the Participation.
RoleClassRetailedMaterial	Material (player) sold by a retailer (scoper), who also give advice to prospective buyers.
RectalInstillation	Instillation, rectal
HairRoute	Hair
ActRelationshipRe-challenge	**Description:**A relationship in which the target act is carried out to determine whether an effect attributed to the source act can be recreated.
IntracaudalRoute	Intracaudal
RaceAmericanIndianPueblo
ActClassTransfer	**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.
ActClassDocumentBody	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.
x_EntityClassDocumentReceiving
ActAmbulatoryEncounterCode	**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.
IntraosseousRoute	Intraosseous
EthnicityHispanicMexican
WorkClassificationODH	Provide the concepts for the value element of the C-CDA Work Classification Observation entry template.
RoleClassAssociative	A general association between two entities that is neither partitive nor ontological.
SubstitutionCondition	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.
SecurityIntegrityProvenanceObservationType	Type of security metadata observation made about the provenance integrity of an IT resource (data, information object, service, or system capability), which indicates the lifecycle completeness or workflow status of an IT resource, such as its creation, modification, suspension, and deletion; locations in which the resource has been collected or archived, from which it may be retrieved, and the history of its distribution and disclosure. Integrity provenance metadata about an IT resource may be used to assess its veracity, reliability, and trustworthiness.
Shasta
ActAccommodationReason	Identifies the reason the patient is assigned to this accommodation type
CreamDrugForm	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.
RaceWhiteArab
ActMoodPermission	A kind of service which is authorized to be performed.
SpecimenAdditiveEntity	Set of codes related to specimen additives
ActClassSubstanceExtraction
HealthcareProviderAgencyHIPAA	A non-facility provider that renders outpatient outreach services that are not provided at a specific location. The licensure or registration is assigned to the agency rather than to the individual practitioners as would be the case in a group practice.
ActRelationshipEndsDuring
LaboratoryHIPAA	A room or building equipped for scientific experimentation, research, testing, or clinical studies of materials, fluids, or tissues obtained from patients.
ActHealthInformationManagementReason	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.
PatientImportance	Patient VIP code
WeightAlert	Proposed therapy may be inappropriate based on the patient's weight
RoleLinkHasIndirectAuthorityOver	The source Role has indirect authority over the target role in a chain of authority.
ParticipationTracker	A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
RoleClassMilitaryPerson	A role played by a member of a military service. Scoper is the military service (e.g. Army, Navy, Air Force, etc.) or, more specifically, the unit (e.g. Company C, 3rd Battalion, 4th Division, etc.)
x_ActMoodPermPermrq	Enumerates the moods that an Act can take when describing privileges.
ActAdministrativeDetectedIssueManagementCode	Codes dealing with the management of Detected Issue observations for the administrative and patient administrative acts domains.
ActRelationshipContainsEndOf
OrganizationNamePartQualifier
SpecimenEntityType
IntraepithelialRoute	Intraepithelial
RaceCanadianLatinIndian
ActRelationshipAssignsName	Used to assign a "name" to a condition thread. Source is a condition node, target can be any service.
SnodentSalzmannInterarchDeviationMaxillaryToothInternational	The SNODENT identifiers for the teeth in the maxilla assessed for tooth-specific inter-arch deviations as part of calculating the Salzmann Malocclusion Severity Index. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
MapRelationship	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
RelationshipConjunction	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.
ActRelationshipReverses	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.
ActClassDocumentSection	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.
Dakotan
AdditionalLocator	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).
ObservationAllergyType	Hypersensitivity to an agent caused by an immunologic response to an initial exposure.
employmentStatusODH	Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment.
PillDrugForm	A small, round solid dosage form containing a medicinal agent intended for oral administration.
ObservationQualityMeasureAttribute	Codes used to define various metadata aspects of a health quality measure.
ActConsentDirective	ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms.
UreteralRoute	Ureteral
RoleClassRoot	Corresponds to the Role class
ChildInLaw	The player of the role is the spouse of scoping person's child.
PermanentDentition	Permanent dentition, the natural teeth of adulthood that replace or are added to the deciduous teeth
ActRelationshipStartsNearStart	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
TranstrachealRoute	Transtracheal
DuplicateTherapyAlert
RaceAmericanIndianPequot
ParticipationGuarantorParty	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.
VitreousHumourRoute	Vitreous humour
TargetAwareness	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.
EntityHandling	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.
TableFrame	These values are defined within the XHTML 4.0 Table Model
ResearchSubjectRoleBasis	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.
ActClassConcern
ObservationInterpretationDetected	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.
ActSpecObsCode	Identifies the type of observation that is made about a specimen that may affect its processing, analysis or further result interpretation
PharmacyServiceProviderTechnicianHIPAA	(1) A person with specialized training in a narrow field of expertise whose occupation requires training and is skilled in specific technical processes and procedures. (2) An individual having special skill or practical knowledge in an area, such as operation and maintenance of equipment or performance of laboratory procedures involving biochemical analyses. Special technical qualifications are normally required, though an increasing number or technicians also possess university degrees in science, and occasionally doctorate degrees. The distinction between technician and technologist in the health care field is not always clear.
ActClassAcquisitionExposure	**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.
AmbulatoryClinicOrCenterHIPAA	A facility or distinct part of one used for the diagnosis and treatment of outpatients. "Clinic/center" is irregularly defined, either including or excluding physician's offices and allied health professionals, sometimes being limited to organizations serving specialized treatment requirements or distinct patient/client groups (e.g., radiology, poor, public health).
ObservationInterpretationNormalityAbnormal	Interpretation of degree of abnormality (including critical or "alert" level). Concepts in this category are mutually exclusive, i.e., at most one is allowed.
ParticipationInformationTranscriber	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.
ParticipationReusableDevice	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.
x_ParticipationAuthorPerformer	One who initiates the control act event, either as its author or its physical performer.
SecurityIntegrityConfidenceObservationValue
RaceAmericanIndianDelaware
ActClassRegistration	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:*
x_RoleClassAccommodationRequestor	The requestor for the accommodation. Steward is Financial Management Technical Committee
ObservationPopulationInclusion	Observation values used to assert various populations that a subject falls into.
ObservationActContextAgeGroupType	Identifies a type of observation that captures the age of a person in terms of age group concept codes.
ActRelationshipUpdate	**Description:** **Deprecation Comment:** Was mis-named, and a proper representation has been provided. Replaced by value set ActRelationshipCompliesWith.
RoleClass	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.
Institution	Institution
AcknowledgementType	Acknowledgement code as described in HL7 message processing rules.
MobileUnit	Location (mobile) where healthcare service was delivered.
EndocervicalRoute	Endocervical
ActRelationshipSplitExclusiveWait	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.
EntityDeterminerDescribedQuantified	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.
ActClassOutbreak	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.
AdministrativeGender	The gender of a person used for adminstrative purposes (as opposed to clinical gender)
Parent	one that begets or brings forth offspring or a person who brings up and cares for another (Webster's Collegiate Dictionary)
ActRelationshipIsEtiologyFor	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.
RaceAmericanIndianKiowa
EmergencyPharmacySupplyType	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)
ParticipationReferredTo	The person who receives the patient
SecurityTrustFrameworkObservationType	Type of security metadata observation made about a complete set of contracts, regulations, or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. \[Kantara Initiative\]
ContextControlAdditiveNon-propagating	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.
Child	The player of the role is a child of the scoping entity.
SupplyDetectedIssueCode	Supplying the product at this time may be inappropriate or indicate compliance issues with the associated therapy
ActRelationshipCompliesWith
ActRelationshipEpisodelink	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.
IntrasynovialRoute	Intrasynovial
MediaType	Internet Assigned Numbers Authority (IANA) Mime Media Types
AllergyTestValue	Indicates the result of a particular allergy test. E.g. Negative, Mild, Moderate, Severe
LanguageAbilityMode	A value representing the method of expression of the language. *Example:*Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed.
ActRelationshipEndsAfterOrConcurrentWithEndOf	Pro-forma value set for each head code in the ActRelationshipType code system; all codes present and future below the head code.
NUCCProviderCodes	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.
SupernumeraryTooth	Supernumerary tooth, any tooth in addition to the normal permanent and primary dentition
IntraovarianRoute	Intraovarian
x_DocumentSubject
CombinedPharmacyOrderSuspendReasonCode	**Description:**Indicates why the prescription should be suspended.
TransmucosalRoute	Transmucosal
RoleClassNextOfKin	An individual designated for notification as the next of kin for a given entity.
Homeless	**Definition:** Living arrangements lacking a permanent residence.
Takic
ActRelationshipStartsBeforeStartOf
ConceptPropertyId	Property identifiers for a concept code
RoleClassEventLocation
ManagedParticipationStatusPending	The state representing that fact that the Participation has not yet become active.
SecurityIntegrityProvenanceReportedByObservationValue
ActInjuryCodeCSA
IntraarterialRoute	Intra-arterial
ParticipationMode	Identifies the primary means by which an Entity participates in an Act.
SubarachnoidRoute	Subarachnoid
TransmissionRelationshipTypeCode	**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.
Insertion	Insertion
ParticipationInformant	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.
IndividualCaseSafetyReportType	All codes from code system ActCode.\_IndividualCaseSafetyReportType
SuspensionDrugForm
RaceAmericanIndianDiegueno
OrderedListStyle	Defines rendering characteristics for ordered lists
ActClassFolder
x_DocumentStatus	Status of a clinical document.
TimingEvent
TananaTutchone
Sequencing	Specifies sequence of sort order.
RaceAmericanIndianKickapoo
HtmlLinkType	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
ParticipationIndirectTarget	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.
DosageProblem
ObservationDrugIntoleranceType	Hypersensitivity resulting in an adverse reaction upon exposure to a drug.
CriticalityObservationValue	Recommended values for criticality observations > *Steward:* Security WG
GrandChild	The player of the role is a child of the scoping person's son or daughter.
KnowledgeSubjectObservationCode
ActMoodDesire
ParticipationSubset	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.
ActCoverageTypeCode	**Definition:** Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.
PersonNameUse	A code indicating the type of name (e.g. nickname, alias, maiden name, legal, adopted)
StyleType	(abstract) Used within an instance to give the author some control over various aspects of rendering
GTSAbbreviationHolidaysUSNational	United States National Holidays (public holidays for federal employees established by U.S. Federal law 5 U.S.C. 6103.)
MessageWaitingPriority	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.
InvoiceElementSubmitted	Total counts and total net amounts billed for all Invoice Groupings that were submitted within a time period. Adjudicated invoice elements are included.
SupplyOrderAbortReasonCode	**Definition:**A collection of concepts that indicates why the prescription should no longer be allowed to be dispensed (but can still administer what is already being dispensed).
AgeDetectedIssueCode	Proposed therapy may be inappropriate or contraindicated due to patient age
ActRelationshipHasCredit	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.
Currency	The currency unit as defined in ISO 4217
Enema	Enema
ContainerCap	The type of cap associated with a container
CaliforniaAthapaskan
Diffusion	Diffusion
ResponseMode	Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.
ActClassInvoiceElement	Represents concepts related to invoice processing in health care
CreeMontagnais
Miwokan
IntraprostaticRoute	Intraprostatic
ActRelationshipStartsBeforeStartOfEndsBeforeEndOf
RaceAmericanIndianPaiute
ActRelationshipReplaces	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.
ActCoverageMaximaCodes	**Definition:** Codes representing the maximum coverate or financial participation requirements.
ActClassOutbreak2	An Outbreak is a concern resulting from a series of public health cases.
SecurityDataIntegrityObservationValue
x_InformationRecipientRole	Used to represent the role(s) of those who should receive a copy of a document.
AddressPartType	Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"
x_Medicine	A type of Administered Substance that is manufactured from raw organic or inorganic ingredients and used in the course of a patient's therapy.
RoleLinkHasContact
ActDietCode	Code set to define specialized/allowed diets
EntityClassState	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.
MedicationGeneralizationRoleType	Identifies the specific hierarchical relationship between the playing and scoping medications. *Examples:* Generic, Generic Formulation, Therapeutic Class, etc.
RaceNativeAmerican
x_ParticipationVrfRespSprfWit	One who oversees a control act event. Includes either a type of accountability, as in responsible party, verifier (and its children) and witness; or being an assistant to the control act event, as in secondary performer.
EntityClassRoot	Corresponds to the Entity class
ActRelationshipHasSupport	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.)
GTIN	**Description:**Global Trade Item Number is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council).
ControlActNullificationRefusalReasonType
IntracervicalRoute	Intracervical
ActAdjudicationGroupCode	Catagorization of grouping criteria for the associated transactions and/or summary (totals, subtotals).
ParticipationModeWritten	Participation by human language recorded on a physical material
ActRelationshipHasMetadata
RoleClassSubsumedBy	Relates a prevailing record of an Entity (scoper) with another record (player) that it subsumes. *Examples:* Show a correct new Person object (scoper) that subsumes one or more duplicate Person objects that had accidentally been created for the same physical person. *Constraints:* Both the player and scoper must have the same classCode.
Dhegiha
EntityNameUseR2	**Description:**A set of codes advising a system or user which name in a set of names to select for a given purpose.
ActClassClinicalDocument	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."
Wakashan
RoleClassActiveMoiety	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.
ActRelationshipHasComponent	A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.
RoleClassManagedEntity	**Description:**A value set of role classCodes related to entity management.
ActRelationshipContainsTimeOf
ParticipationAuthorOriginator	**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.
ActStatusActive	The Act can be performed or is being performed
ParticipationAdmitter	The practitioner who is responsible for admitting a patient to a patient encounter.
Grandparent	parent of a parent of the subject
GeneralAddressUse
PersonDisabilityType	A code identifying a person's disability.
ActInformationAccessCode	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.
ContextControlOverriding	The association adds to the existing context associated with the Act, but replaces associations propagated from ancestor Acts whose typeCodes are the same.
ProgramEligibleCoveredPartyRoleType	**Description:**A role recognized through the eligibility of a party to play a program eligible for benefits covered or provided under a program.
RaceAmericanIndianPotawatomi
RoleClassNursePractitioner
ParticipationType	A code specifying the meaning and purpose of every Participation instance. Each of its values implies specific constraints on the Roles undertaking the participation.
ActRelationshipSplitInclusiveWait	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).
ActRelationshipCheckpointBeginning	Condition is tested every time before execution of the service (WHILE condition DO service).
EntityDeterminerSpecific	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.
ActMoodPredicate	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.
OralRoute	Oral
ParticipationAnalyte
VaccineEntityType	A Type of medicine that creates an immune protection without the recipient experiencing the disease.
ActStatusCancelled	The Act has been abandoned before activation.
ActMood	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.)
MaritalStatus	The domestic partnership status of a person. *Example:*Married, separated, divorced, widowed, common-law marriage.
x_ServiceEventPerformer	Clones using this x\_domain should have a name "performer".
ParticipationSignature	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.)
Ojibwayan
ActClassROI	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.
RoleClassActiveIngredientBasis
ActRelationshipModifies	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"
OtherTechnologistAndOrTechnicianHIPAA	A broad category grouping providers who apply scientific knowledge in solving practical or theoretical problems or applies technical procedures in accordance with their training and experience.
SolutionDrugForm	A liquid preparation that contains one or more chemical substances dissolved, i.e., molecularly dispersed, in a suitable solvent or mixture of mutually miscible solvents.
RoleClassDependent	**Description:** A role played by a person covered under a policy or program based on an association with a subscriber, which is recognized by the policy holder. **Note:** The party playing the role of a dependent is not a claimant in the sense conveyed by the RoleClassCoveredParty CLAIM (claimant). However, a dependent may make a claim under a policy, e.g., a dependent under a health insurance policy may become the claimant for coverage under that policy for wellness examines or if injured and there is no liable third party. In the case of a dependent making a claim, a role type code INSCLM (insured claimant) subtypes the class to indicate that the dependent has filed a claim for services covered under the health insurance policy. **Example:** The dependent has an association with the subscriber such as a financial dependency or personal relationship such as that of a spouse, or a natural or adopted child. The policy holder may be required by law to recognize certain associations or may have discretion about the associations. For example, a policy holder may dictate the criteria for the dependent status of adult children who are students, such as requiring full time enrollment, or may recognize domestic partners as dependents. Under certain circumstances, the dependent may be under the indirect authority of a responsible party acting as a surrogate for the subscriber, for example, if the subscriber is differently abled or deceased, a guardian ad Lidem or estate executor may be appointed to assume the subscriberaTMs legal standing in the relationship with the dependent.
ActRelationshipContainsStartOfEndsBeforeEndOf
AmbulanceHIPAA	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).
CalendarType
VaccineType	The kind of vaccine.
ProbabilityDistributionType
ActRelationshipInstantiatesMaster	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.
x_ActRelationshipDocumentSPL
IntrasinalRoute	Intrasinal
GTSAbbreviationBase	**Description:**Basic abbreviations defined for the General timing Specification data type.
ActClassStanding	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
EntityClassNation	A politically organized body of people bonded by territory and known as a nation.
MaterialDangerInfectious	Material known to be infectious with human pathogenic microorganisms. Those who handle this material must take precautions for their protection.
DoseLowDetectedIssueCode	Proposed dosage is below suggested therapeutic levels
ParticipationEntryLocation	A location where data about an Act was entered.
Taracahitan
AdministrationDetectedIssueCode	Administration of the proposed therapy may be inappropriate or contraindicated as proposed
ParticipationCausativeAgent	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.
ActRelationshipStartsAfterStartOfEndsWith
ActClassRightLateralDecubitus	**Deprecation Comment:** This value set has been deprecated because its root code was deprecated in an earlier vocabulary release.
HomeAddress
x_ActInvoiceDetailPharmacyCode	The billable codes selected for use for Pharmacy Invoices. Steward is Financial Management.
ActInvoiceElementSummaryCode	Identifies the different types of summary information that can be reported by queries dealing with Statement of Financial Activity (SOFA). The summary information is generally used to help resolve balance discrepancies between providers and payors.
ObservationInterpretationNormality	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.
AppropriatenessDetectedIssueCode
NativeEntityAlaska	NATIVE ENTITIES WITHIN THE STATE OF ALASKA RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS
TelecommunicationAddressUse
x_ActMoodOrdPrms	A grouping of Order, Promise. These specific moods are used in orders.
IntegrityCheckAlgorithm
ActNoImmunizationReason	A coded description of the reason for why a patient did not receive a scheduled immunization. (important for public health strategy
x_EntityClassPersonOrOrgReceiving
ActVirtualEncounterCode	**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.
RepetitionsOutOfRange
BuildingNumber	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.
SubsidizedHealthProgram	**Definition:** A government health program that provides coverage for health services to persons meeting eligibility criteria such as income, location of residence, access to other coverages, health condition, and age, the cost of which is to some extent subsidized by public funds.
SnodentDentalToothMobilityMillerClassificationInternational	The SNODENT identifiers for the recognized grades of tooth mobility according to the Miller Classification system. This value set contains content from SNODENT® Copyright American Dental Association (ADA). All rights reserved. SNODENT is a registered trademark of the ADA. http://www.ada.org/en/member-center/member-benefits/practice-resources/dental-informatics/snodent/licensing-snodent *Steward:* Attachments WG
ParticipationTargetLocation	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.)
RaceAlaskanNative
ActTaskClinicalNoteEntryCode	A clinician enters a clinical note about a given patient
IntrailealRoute	Intraileal
KoyukonIngalik
ActClassConsent	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.
EntityCode	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.
ClassNullFlavor	**Description:** Subset of null flavors, used for associations as needed for the ITS, and used in InfrastructureRoot.
ActShortStayEncounterCode	**Definition:**An encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less than 24 hours.
ActRelationshipDeparture	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.
ProcessingMode	This attribute defines whether the message is being sent in current processing, archive mode, initial load mode, restore from archive mode, etc.
ConsultedPrescriberManagementCode	Consulted prescriber, therapy confirmed
EntityClassStateOrProvince	The territory of a state, province, department or other division of a sovereign country.
NoInformation	**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.
CochimiYuman
ActMoodCompletionTrack	These are moods describing activities as they progress in the business cycle, from defined, through planned and ordered to completed.
ObservationEligibilityIndicatorValue	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.
RoleClassPhysicianAssistant
ActClassPositionAccuracy	**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.
Tsamosan
SecurityTrustAgreementObservationValue	Type of security metadata observation made about security requirements for a security domain. \[ISO IEC 10181-1\] Definition Is Immutable: true
SeverityObservationCode
Cupan
PerinealRoute	Perineal
RoleClassExposureAgentCarrier	An exposure agent carrier is an entity that is capable of conveying an exposure agent from one entity to another. The scoper of the role must be the exposure agent (e.g., pathogen).
RoleClassIsolate	A microorganism that has been isolated from other microorganisms or a source matrix.
ObservationSeriesType
WesternApachean
ActClassStorage	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.
PhysicianAssistantsAndOrAdvancedPracticeNursingProviderHIPAA	A broad grouping of providers who are: 1) trained, educated, and certified to perform basic medical and minor surgical services (or to assist the physician in performance of more complex services) under general physician supervision; and 2) trained, educated at a post-graduate level, and certified to perform autonomous and specialized roles as nurse practitioners, midwives, nurse anesthetists, or clinical nurse specialists.
SouthernNumic
ActClassSubstanceAdministration	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
ChiwereWinnebago
CalendarCycleTwoLetter	Two letter calendar cycle abbreviations (Temporary - remove when RoseTree is fixed)
RaceAmericanIndianShoshone
Decision Observation Method	Provides codes for decision methods, initially for assessing the causality of events.
RoleClassExposureVector	**Description:** A vector is a living subject that carries an exposure agent. The vector does not cause the disease itself, but exposes targets to the exposure agent. A mosquito carrying malaria is an example of a vector. The scoper of the role must be the exposure agent (e.g., pathogen).
NursePractitionerHIPAA	(1)A registered nurse provider with a graduate degree in nursing prepared for advanced practice involving independent and interdependent decision making and direct accountability for clinical judgment across the health care continuum or in a certified specialty. (2) A registered nurse who has completed additional training beyond basic nursing education and who provides primary health care services in accordance with state nurse practice laws or statutes. Tasks performed by nurse practitioners vary with practice requirements mandated by geographic, political, economic, and social factors. Nurse practitioner specialists include, but are not limited to, family nurse practitioners, gerontological nurse practitioners, pediatric nurse practitioners, obstetric-gynecologic nurse practitioners, and school nurse practitioners.
RoleClassPlaceOfDeath	Definition: Relates a place (playing Entity) as the location where a living subject (scoping Entity) died.
LengthOutOfRange
EntityStatusNormal	The 'typical' state. Excludes "nullified" which represents the termination state of an Entity record instance that was created in error.
Calendar
ActSpecObsInterferenceCode	An observation that relates to factors that may potentially cause interference with the observation
OrganizationEntityType	Further classifies entities of classCode ORG.
ParticipationExposureagent	**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.
RoleClassWarrantedProduct	A role a product plays when a guarantee is given to the purchaser by the seller (scoping entity) stating that the product is reliable and free from known defects and that the seller will repair or replace defective parts within a given time limit and under certain conditions.
x_LabProcessClassCodes
ActClass	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.)
ActRelationshipPalliates
DocumentCompletion	Identifies the current completion state of a clinical document.
RoleClassEquivalentEntity
ParticipationModeVerbal	Participation by voice communication
SecurityIntegrityStatusObservationType	Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Indicates the completeness or workflow status of an IT resource, which may impact users that are authorized to access and use the resource.
ActRelationshipStartAfterStartOfContainsEndOf
ParticipationEscort	Only with Transportation services. A person who escorts the patient.

Terminology: Code Systems

These define new code systems used by systems conforming with this implementation guide

PH_RaceAndEthnicity_CDC	Code system of concepts specifying the patient's race. Used in HL7 Version 2.x messages in the PID segment.
NUBC UB04 Claims Form Edit Codes	Codes used for the pick lists for identified UB04 claims form fields. See https://www.nubc.org/ub-04-products
nubc-PresentOnAdmission-cs	National Uniform Billing Committee (NUBC) UB-04 Data Specifications Manual, UB form locator 67, Present on Admission (POA) Indicator. Code identifying a diagnosis that was present at the time the order for inpatient admission occurs. POA indicator is assigned to all diagnoses as defined in Appendix I of the "ICD-9-CM Official Guidelines for Coding and Reporting" or "ICD-10-CM Official Guidelines for Coding and Reporting (appropriate to the ICD revision used). The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the DG1 segment. Note that this content was previously published in HL7 artifacts in violaton of IP restrictions; the content has been removed in version 2.2.0 pending finalization of a republication permission request to AHA/NUBC.
nubc-ServiceLineRevenue-cs	Code system of concepts specifying a revenue code as specified in the National Uniform Billing Committee (NUBC) UB-04 manual, UB form locator 42, the service line revenue code. These are claim codes indicating the identifying number for the product or service provided. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the Revenue Code (GP1) value. Updated by NUBC annually; see the coding instructions for more detail. Note that this content was previously published in HL7 artifacts in violaton of IP restrictions; the content has been removed in version 2.2.0 pending finalization of a republication permission request to AHA/NUBC.
PH_VaccinesAdministeredCVX_CDC_NIP	Table of codes specifying the administered vaccines. The values are maintained by the US Centers of Disease Control. The code system is maintained by the CDC, and may be found at URL; https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.113883.12.292 The value set is maintained by the CDC and may be found at URL: https://phinvads.cdc.gov/vads/ViewValueSet.action?id=ABDEE003-77C3-48E7-B941-EBF92B6B81FC
PH_ManufacturersOfVaccinesMVX_CDC_NIP	Table of codes specifying the organization that manufactures a vaccine. The values are maintained by the US Centers of Disease Control. Note that the source of truth for these code values are maintained by the CDC, and the code system may be accessed at URL: https://phinvads.cdc.gov/vads/SearchCodeSystems_search.action?searchOptions.searchText=PH_ManufacturersOfVaccinesMVX_CDC_NIP. The value set is also maintained by the CDC, and may be accessed at URL: https://phinvads.cdc.gov/vads/SearchValueSets_search.action?searchOptions.searchText=PHVS_ManufacturersOfVaccinesMVX_CDC_NIP
nubc-OccurrenceCode-cs	National Uniform Billing Committee (NUBC) UB-04 Data Specifications Manual, UB form locator 31 - 34, Occurrence Codes and Amounts - code and associated date defining asignificant event relating to the bill that may affect payer processing the claim. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the OCD segment. Updated by NUBC annually; see the coding instructions for more detail. Note that this content was previously published in HL7 artifacts in violaton of IP restrictions; the content has been removed in version 2.2.0 pending finalization of a republication permission request to AHA/NUBC.
nubc-OccurrenceSpan-cs	HL7-defined code system of concepts specifying a National Uniform Billing Committee (NUBC) code that identifies an event that relates to the payment of a claim. The UB-04 Data Specifications Manual with the codes is available by subscription from NUBC at http://www.nubc.org/become.html. Used in HL7 Version 2.x messaging in the Occurrence Span Code and Date (OSP) value. Updated by NUBC annually; see the coding instructions for more detail. Note that this content was previously published in HL7 artifacts in violaton of IP restrictions; the content has been removed in version 2.2.0 pending finalization of a republication permission request to AHA/NUBC.
NAACCR	NAACCR Cancer Registry
Active Ingredient Code	**Description:** A code assigned to any component that has medicinal properties, and supplies pharmacological activity or other direct effect in the diagnosis, cure, mitigation, treatment or prevention of disease, or to affect the structure or any function of the body of man or other animals. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
The Read Codes Version 2	The Read Codes Version 2 contains over 70,000 coded concepts arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs
Human Genome Variation Society nomenclature	HGVS nomenclatures are the guidelines for mutation nomenclature made by the Human Genome Variation Society. HGVS nomenclature can be used with the HL7 coded data type (code data type that accepts expression data, or a coded expression data type). This coded data type should be able to distinguish expressions in HGVS nomenclature from coded concepts. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, HGVS nomenclature can be used to as the observation values for DNA sequence variations. For example, OBX|1|CWE|48004-6^DNA Sequence Variation^LN||c.1129C>T^^HGVS| Versioning information: The HGVS nomenclature for the description of sequence variants was last modified Feb 20, 2008. The HGVS nomenclature for the description of protein sequence variants was last modified May 12, 2007. The HGVS nomenclature for the description of DNA sequence variants was last modified June 15, 2007 The HGVS nomenclature for the description of RNA sequence variants was last modified May 12, 2007 HGVS nomenclatures can be used freely by the public.
International Classification of Sleep Disorders	International Classification of Sleep Disorders
Medispan Diagnostic Codes	Medispan Diagnostic Codes
pan-Canadian LOINC Observation Code Database	The pan Canadian LOINC Observation Code Database (pCLOCD) is the Canadian version of the LOINC(tm) database. It was created using the LOINC(tm) records and attributes that were constrained for Canadian use and supplemented to specifically meet Canadian requirements. It contains the core LOINC(tm) attributes as required by Regenstrief copyright rules. The LOINC(tm) Component has been customized to meet Canadian requirements and is displayed as the pan Canadian Component Name. This component name is the basis for the pan Canadian Display Name. Core attributes are include both English and Canadian French. This code system contains supplemental "X" codes defined in the pCLOCD that do not yet exist in the LOINC code system.
Omaha System	The Omaha System provides standardized terms, definitions, and codes for observations and procedures, specifically for client problems, multidisciplinary interventions including those focusing on assessment and care, and problem-specific client outcomes.
SNOMED-DICOM Microglossary	SNOMED-DICOM Microglossary
Clinical Care Classification System	Clinical Care Classification System (formerly Home Health Care Classification system) codes. The Clinical Care Classification (CCC) consists of two taxonomies: CCC of Nursing Diagnoses and CCC of Nursing Interventions both of which are classified by 21 Care Components. Each of these are classified by Care Components which provide a standardized framework for documenting patient care in hospitals, home health agencies, ambulatory care clinics, and other health care settings.
DEEDS405	ED Source of Referral
DICOM Query Label	DICOM Query Label
International Classification of Primary Care, second edition, English	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
Canadian DiagnosisCodes ICD-10-CA	Canadian Coding Standards ICD-10 CA. These standards are a compilation of international rules of coding as established by the World Health Organization (International Classification of Diseases, 10th Revision, Volume 2) and the Diagnosis Typing Standard developed to denote case complexity for application in Canadian facilities. For example: * L40 Psoriasis * L40.0 Psoriasis vulgaris * Nummular psoriasis * Plaque psoriasis * L40.1 Generalized pustular psoriasis * Impetigo herpetiformis * Von ZumbuschaTMs disease * L40.2 Acrodermatitis continua * L40.3 Pustulosis palmaris et plantaris * L40.4 Guttate psoriasis * L40.5\* Arthropathic psoriasis (M07.0-M07.3\*)(M09.0\*) * L40.8 Other psoriasis * Erythroderma psoraticum * Erythrodermic psoriasis * Flexural psoriasis * L40.9 Psoriasis unspecified They are maintained by CIHI (Canadian Institute for Health Information). CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca
HUGO Gene Nomenclature	HUGO Gene Nomenclature Committee (HGNC) is committee jointly funded by the US National Human Genome Research Institute and the Wellcome Trust (UK). It operates under the auspices of HUGO, with key policy advice from an International Advisory Committee, and is responsible for approving gene names and symbols. All approved symbols are stored in the HGNC database. Each symbol is unique and each gene is only given one approved gene symbol. More than 28,000 human gene symbols and names have been approved so far. The vast majority of these is for protein-coding genes, but also includes symbols for peudogenes, non-coding RNAs, phenotypes and genomic features. HGNC gene symbols can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model Implementation Guide, HGNC gene symbols can be used to as the observation values for gene identifiers. For example, OBX|1|CWE|48018-6^Gene identifier^||BRCA1^HGNC| Versioning Information: The version of the HGNC database is reported using the last updated date and timestamp. The last updated date and timestamp is posted on the main HGNC Search screen in the format like "Monday March 30 23:00:56 2009". HGNC is updated daily. HGNC is a free database for the public.
ICPC2-ICD10ENG Thesaurus, Dutch Translation	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
Locus Reference Genomic Sequences (LRG)	In collaboration with NCBI, the European Bioinformatics Institute (EBI) is developing the Locus Reference Genomic Sequences (LRG) database, which is a database of reference sequences. LRG is a system for providing a genomic DNA sequence representation of a single gene that is idealized, has a permanent ID (with no versioning), and core content that never changes. LRG is not a nomenclature system. More than one LRG could be created for a region of interest, should that need arise. Additional annotations will be present that may change with time (each item carrying its own date stamp), so that the latest ancillary knowledge about a gene is directly available. In other words, an LRG sequence and its core annotation are not meant to represent current biology knowledge, but to provide a standard for reporting variation in a stable coordinate system. The combination of the LRG plus the updatable-annotation layer will be used to support the biological interpretation of variants. LRG identifiers can be used with the HL7 coded data type (code data type that accepts expression data, or a coded expression data type). This coded data type will be gene symbols can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, LRG identifiers can be used to as the observation values for Genomic Reference Sequence Identifier (LOINC code: 48013-7). LRG is a database that can be used freely by the public.
Tags for the Identification of Languages	Older value from OID registry. Superceded; see recommendations in BCP-47.
Genetic Sequence polymorphism database	In collaboration with the National Human Genome Research Institute, The National Center for Biotechnology Information has established the dbSNP database to serve as a central repository for both single base nucleotide substitutions and short deletion and insertion polymorphisms. The entries in the dbSNP database can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, dbSNP entries can be used to as the observation values for DNA sequence variation identifiers. For example, OBX|1|CWE|48004-6^DNA Sequence Variation Identifier^LN||rs55538123^^dbSNP Versioning is identified by the build id. A new build is released approximately every six months or every year. The latest build id is 130, and the dbSNP web query for built 130 was available on Apr 30, 2009. dbSNP is a database that can be used freely by the public. More information may be fouond at: http://www.ncbi.nlm.nih.gov/projects/SNP/
CDC Vaccine Manufacturer Codes	CDC Vaccine Manufacturer Codes
DEEDS407	Code for Initial Healthcare Encounter for Chief Complaint
DEEDS412	ED Responsiveness Assessment
MedDRA Dutch	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Dutch Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the Dutch language version as encapsulated in the UMLS..
ICD9	ICD9
Health Outcomes	Health Outcomes
Active Ingredient Group Code	**Description:** Codes for particular grouping of active ingredients. This is the first 5 characters of active ingredient group number. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
X12.3 Data Elementary Dictionary	X12.3 Data Elementary Dictionary This is the root OID for vocabulary defined internally by X12N. OIDS for each vocabulary will be assigned underneath this oid by appending the X12N data element id to the root OID. Data Element 1336 is Insurance Type Code, so the OID for the X12N Insurance Type Code vocabulary will be 2.16.840.1.113883.6.255.1336
GCRT	GCRT Route of Administration Code (1-character) a one-character alphanumeric column that provides the normal site or method by which a drug is administered, such as oral, injection, or topical. A GCRT is associated to each GCN\_SEQNO to identify that component of the generic drug formulation.
WHO Adverse Reaction Terms German	WHO Adverse Drug Reaction Terminology (WHOART). German Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
US EPA Substance Registry System	The United States Environmental Protection Agency's (US EPA) Substance Registry System (SRS) provides information on substances and how they are represented in US environmental statutes, in US EPA information systems, and in information systems owned by other organizations. The SRS provides standardized identification for each substance to improve data quality in US EPA systems and elsewhere.
WHO Adverse Reaction Terms foreign language translations	WHO Adverse Drug Reaction Terminology (WHOART). Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. This branch node OID contains identifiers for the different foreign language versions of this terminology. For more information, see http://www.umc-products.com/graphics/3149.pdf
MEDCIN	MEDCIN contains more than 175,000 clinical data elements arranged in a hierarchy, with each item having weighted links to relevant diagnoses. The clinical data elements are organized into six basic termtypes designed to accommodate information relevant to a clinical encounter. The basic termtypes in MEDCIN's terminological hierarchy are as follows: Symptoms History Physical Examination Tests Diagnoses Therapy Within this basic structure, MEDCIN terms are further organized in a ten level terminological hierarchy, supplemented by an optional, multi-hierarchical diagnostic index. For example, the symptom of "difficulty breathing" is placed in the terminological hierarchy as a subsidiary (or "child") finding of "pulmonary symptoms," although the presence (or absence) of difficulty breathing can related to conditions as diverse as myocardial infarction, bronchitis, pharyngeal foreign bodies, asthma, pulmonary embolism, etc. MEDCIN's diagnostic index provides more than 800 such links for difficulty breathing.
European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System	**Description:** The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.
ICD-10 Procedure Codes	ICD Procedure Coding System (ICD 10 PCS)
European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis	**Description:**The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.
ISO 3166 Part 1 Country Codes, 2nd Edition	This OID identifies the coding system published in the ISO 3166-1 Standard for Country codes. It contains 3 sets of synonyms for the country codes: 2-character alphabetic, 3-character alphabetic, and numeric. Note that this is the 2nd edition of the standard.
DEEDS416	Glasgow motor component assessment
DEEDS402	Mode of transport to ED
HL7 Registered External Coding Systems	External coding systems registered in HL7 with an HL7 OID
ABCcodes	Five character alphabetic codes fit into current claims processing software or onto standard paper claim forms. ABC Codes give business parity to licensed CAM and nurse providers who file claims to insurance companies. .
ICPC2E Am Engl (Metathesaurus)	Henk Lamberts and Inge Hofmans-Okkes. International Classification of Primary Care 2nd Edition, Electronic, 2E, American English Equivalents. Amsterdam: International Classification of Primary Care / prepared by the Classification Committee of the World Health Organization. Entry derived from the UMLS Metathesaurus.
DEEDS vocabularies	root for the DEEDS code sets
Enzyme Codes	Enzyme Codes
International Classification of Primary Care 1993 Danish	The International Classification of Primary Care (ICPC). Danish Translation. Denmark: World Organisation of Family Doctors, 1993.
ISO 3166 Part 1 Country Codes, 2nd Edition, Alpha-2	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, 2-character alphabetic codes.
CDC - National Healthcare Safety Network (NHSN) code system	CDC - National Healthcare Safety Network (NHSN) code system - A set of patient safety and healthcare personnel safety vocabulary concepts and associated identifiers maintained as a code system by the CDC's National Healthcare Safety Network. CDC NHSN is planning to use these code system concepts in the HAI implementation guide. These concepts would be submitted for the HL7 Ballot (Dec 2008). CDC NHSN can provide complete list of concepts, identifiers and extended attributes for this code system.
FIPS_SOC	FIPSPUB92 - GUIDELINE FOR STANDARD OCCUPATIONAL CLASSIFICATION (SOC) CODES, version 1983 February 24. This entry is now obsolete, as FIPS92 was withdrawn from use in February 2005 by the US Government. It has been replaced by 2.16.840.1.113883.6.243; please use that OID instead.
ICPC2P 1998 Plus Austral Mod	International Classification of Primary Care, Version 2-Plus, Australian Modification. January, 2000
NUCC Health Care Provider Taxonomy	The Provider Taxonomy Code List is published (released) twice a year on July 1st and January 1st. The July publication is effective for use on October 1st and the January publication is effective for use on April 1st. The time between the publication release and the effective date is considered an implementation period to allow providers, payers and vendors an opportunity to incorporate any changes into their systems. This listing includes Active codes approved for use effective April 1st, 2003, version 3.0; and codes that are New and approved for use effective October 1st, 2003, version 3.1. It was identified that there is an IP licensure issue with the republishing of the content for this code system by HL7, so the content was removed as of the July 2016 Harmonization cycle release. This external code system content may be accessed from the web page located at http://www.nucc.org/index.php/code-sets-mainmenu-41/provider-taxonomy-mainmenu-40. Multiple formats and means of accessing the content are available from this page.
First DataBank Drug Codes	First DataBank Drug Codes
American College of Radiology finding codes	American College of Radiology finding codes
DEEDS415	Glasgow verbal component assessment
DEEDS414	Glasgow eye opening assessment
ISO 3166 Part 2 Country Subdivision Codes	Identifies the coding system published in the ISO 3166-2 Standard for Country Subdivision codes. This standard is released periodically, and a new OID will be assigned by ISO for new editions.
International Classification of Primary Care 1993 German	The International Classification of Primary Care (ICPC). German Translation. Denmark: World Organisation of Family Doctors, 1993.
Healthcare Service Location	A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the National Healthcare Safety Network (NHSN) location code system that has been developed over a number of years through CDC's 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. The HSLOC content, including relationships can be acced at the following location: http://www.cdc.gov/phin/activities/standards/vocabulary/index.html
ICPC2E 1998 Plus Am Engl	International Classification of Primary Care, Version 2-Plus, Australian Modification. Americanized English Equivalents, January, 2000. Produced by NLM. Bethesda (MD): National Library of Medicine, UMLS project
ISO 3166 Part 1 Country Codes, 2nd Edition, Alpha-3	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, 3-character alphabetic codes.
ICD-10	International Classification of Diseases revision 10 (ICD 10)
National Center for Health Statistics	The International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II (diagnoses) and III (procedures) describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases and procedures. The ICD-9-CM codes can be used as the value of the Act.cd attribute.
ICD10, Dutch Translation	Hirs, W., H.W. Becker, C. van Boven, S.K. Oskam, I.M. Okkes, H. Lamberts. ICD-10, Dutch Translation, 200403. Amsterdam: Department of General Practice, Academic Medical Center/University of Amsterdam, Dutch College of General Practitioners (NHG), March 20
Healthcare Provider Taxonomy HIPAA	NUCC Healthcare Provider Taxonomy codes, as cited in US HIPAA regulations. This HL7 copy of the content is made available by request of various HL7 Affiliates,so do have have direect access to the NUCC contnet as they are outside the US. In additions, some concept have been added to this set that are pending being added to the NUCC master.
International Classification of Diseases for Oncology	International Classification of Diseases for Oncology)
ISO 639-3 Language Codes Alpha 3	**Description:** ISO 639-3 is a code that aims to define three-letter identifiers for all known human languages. At the core of ISO 639-3 are the individual languages already accounted for in ISO 639-2. The large number of living languages in the initial inventory of ISO 639-3 beyond those already included in ISO 639-2 was derived primarily from Ethnologue (15th edition). Additional extinct, ancient, historic, and constructed languages have been obtained from Linguist List. SIL International has been designated as the ISO 639-3/RA for the purpose of processing requests for alpha-3 language codes comprising the International Standard, Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages. The ISO 639-3/RA receives and reviews applications for requesting new language codes and for the change of existing ones according to criteria indicated in the standard. It maintains an accurate list of information associated with registered language codes which can be viewed on or downloaded from this website, and processes updates of registered language codes. Notification of pending and adopted updates are also distributed on a regular basis to subscribers and other parties.
CDC Methods/Instruments Codes	CDC Methods/Instruments Codes
NHSN LCBI Pathways	NHSN Laboratory Confirmed Bloodstream Infection Pathways
Systemized Nomenclature of Medicine (SNOMED)	Systemized Nomenclature in Medicine (SNOMED)
International Classification of Primary Care 1993 (English)	The International Classification of Primary Care (ICPC). Swedish Translation. Denmark: World Organisation of Family Doctors, 1993.
CDT-2 Codes	American Dental Association's Current Dental Terminology 2 (CDT-2) codes.
CDC Surveillance	CDC Surveillance
MedDRA French	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, French Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the French language version as encapsulated in the UMLS..
Food and Drug Administration Food Facility Registration Numbers	Entered in error originally - do not use. Correct OID for this item is 2.16.840.1.113883.4.344.
IUPAC/IFCC Property Codes	IUPAC/IFCC Property Codes
ISO 639-2: Codes for the representation of names of languages -- Part 2: Alpha-3 code	**Description:** Codes for the representation of names of languages, 3 character alphabetic codes. This has been superceded by ISO 639-3 for many purposes. ISO 639-2 was released in 1998. The code set is available from http://www.iso.org/iso/iso\_catalogue/catalogue\_tc/catalogue\_detail.htm?csnumber=4767
UCDS	UCDS
MDNS	MDNS
MedDRA Am Engl expanded	Medical Dictionary for Regulatory Activities Terminology (MedDRA), American English Equivalents with expanded abbreviations, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004.
EPSG Geodetic Parameter Dataset	**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. **Deprecation Comment:** This has been superceded by the two code systems EPSG-CRS and EPSG-CA
NHSN Spinal Fusion Level	NHSN Spinal Fusion Level
IETF RFC 1766	Codes representing languages for which a person has some level of proficiency for written or spoken communication. *Examples:* Spanish, Italian, German, English, American Sign, etc.
AS4 Neurophysiology Codes	AS4 Neurophysiology Codes
Medical Economics Diagnostic Codes	Medical Economics Diagnostic Codes
Health Canada Natural Product Number	A unique identifier assigned to natural health products that have been issued a product licence by Health Canada. http://www.hc-sc.gc.ca/dhp-mps/prodnatur/applications/licen-prod/lnhpd-bdpsnh-eng.php
MedDRA Spanish	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Spanish Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004. This is the Spanish language version as encapsulated in the UMLS..
ISO 639-2 Alpha-3 Language Codes	Codes for the Representation of Names of Languages Part 2: Alpha-3 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. *DeprecationComment:* This code system is being deprecated, as the OID identifying it has been replaced with the correct ISO OID of 1.0.639.2
MTH MedDRA Spanish	Metathesaurus Forms of Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Spanish Edition. Bethesda, MD: National Library of Medicine, March 2004.
International Classification of Diseases for Oncology, version 3.	International Classification of Diseases for Oncology, version 3. For more information see http://www.who.int/classifications/icd/adaptations/oncology/en/.
Medispan GPI	Medispan GPI
ICD-10 German	Internationale Klassifikation der Krankheiten 10 \[German translation of ICD10\]. Germany: Deutsches Institut fuer Medizinische Dokumentation und Information, 1998.
DEEDS519	Clinical Finding Data Source
ISO 639-1: Codes for the representation of names of languages -- Part 1: Alpha-2 code	**Description:** Codes for the Representation of Names of Languages Part 1: Alpha-2 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. This part of ISO 639 provides a code consisting of language code elements comprising two-letter language identifiers for the representation of names of languages. The language identifiers according to this part of ISO 639 were devised originally for use in terminology, lexicography and linguistics, but may be adopted for any application requiring the expression of language in two- letter coded form, especially in computerized systems. The alpha-2 code was devised for practical use for most of the major languages of the world that are not only most frequently represented in the total body of the world's literature, but which also comprise a considerable volume of specialized languages and terminologies. Additional language identifiers are created when it becomes apparent that a significant body of documentation written in specialized languages and terminologies exists. Languages designed exclusively for machine use, such as computer-programming languages, are not included in this code. The code set is available from http://www.iso.org/iso/iso\_catalogue/catalogue\_ics/catalogue\_detail\_ics.htm? csnumber=22109&ICS1=1&ICS2=140&ICS3=20
DEEDS2.10	Code for ED Practitioner Role
ISO 3166 Part 1 Country Codes, 2nd Edition, Numeric	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, numeric codes.
MedDRA Portuguese	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Portuguese Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004. This is the Portuguese language version as encapsulated in the UMLS..
SCDHEC GIS Spatial Accuracy Tiers	**Description:** The South Carolina Department of Health and Environmental Control GIS Spatial Data Accuracy Tiers have been derived from the National Standard for Spatial Data Accuracy as a means to categorize the accuracy of spatial data assignment utilizing a variety of tools for capturing coordinates including digitizers, geocoding software and global positioning system devices.
WHO rec# drug codes	WHO rec\# drug codes
ICD-9CM	International Classification of Diseases revision 9, with Clinical Modifications (ICD 9 CM)
Japanese Chemistry	Japanese Chemistry
DICOM modality codes	DICOM modality codes
DEEDS508	Safety Equipment Use
National Drug Data File	National Drug Data File Plus Source Vocabulary 2004. San Bruno, CA: First DataBank, March 11, 2004. This entry was generated to support the Sources in the UMLS. Additional metadata is still missing.
ICD-9 Dual Coding	ICD-9 Dual Coding Expression Syntax", description: ICD-9 allows dual coding. Refer to Section ?? of the ICD-9 Instruction Manual (ref?). This OID identifies the code system that describes how to encode Dual Coding in a CD compatible expression (for Datatypes R2 CD only). An ICD-9 dual code expression SHALL consist of two ICD-9 codes separated by space. This code system SHALL NOT be used for single ICD-9 codes; the normal ICD-9 code system oid which is 2.16.840.1.113883.6.3 should be used in this case. DisplayName SHALL not be used. Dual code expressions SHALL only be used per the rules described in the ICD-9 instruction manual. **An example CD:**<br></br><example code="989.5 E905.9" codeSystem="2.16.840.1.113883.6.261"><br></br><originalText value="ANAPHYLAXIS DUE TO BITE OR STING"/><br></br></example><br></br>Where 989.5 is: "Toxic effect of venom" and E905.9 is: "Bite or sting"
National Center for Health Statistics	The International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II (diagnoses) and III (procedures) describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases and procedures. The ICD-9-CM codes can be used as the value of the Act.cd attribute.
Read Classification	Clinical Terms Version 3 contains over 200,000 coded concepts arranged in a sub-type hierarchical structure. Top level hierarchy sections: Disorders Findings Morphology Surgical procedures Regimes & therapies Investigations Stages & scales Occupations Organisms Units Drugs Appliances & equipment
IUPAC/IFCC Component Codes	IUPAC/IFCC Component Codes
NHSN SSI Location Type	NHSN SSI LocationType
International Classification of Primary Care 1993 Italian	The International Classification of Primary Care (ICPC). Italian Translation. Denmark: World Organisation of Family Doctors, 1993.
NCI Thesaurus	NCI Thesaurus NCI Thesaurus is a biomedical thesaurus created specifically to meet the needs of the cancer research community, especially those engaged in translational research NCI Thesaurus is produced by the NCI Enterprise Vocabulary Services project. The NCI Thesaurus is provided under an open content license.
FDB HIC Code	The FDB Hierarchical Ingredient Code is a six character identifier that represents an active ingredient and its specific therapeutic classification.
Gene Reference Sequence Collection	The Reference Sequence (RefSeq) is one of the NCBI projects, the RefSeq collection aims to provide a comprehensive, integrated, non-redundant, well-annotated set of sequences, including genomic DNA, transcripts, and proteins. ReqSeq is accessible via BLAST, Entrez, and the NCBI FTP site. Information is also available in Entrez Genomes and Entrez Gene, and for some genomes additional information is available in the Map Viewer. RefSeq entries can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, RefSeq entries can be used to as the observation values for genomic reference sequence identifiers (LOINC \#: 48013-7). More information may be found at: http://www.ncbi.nlm.nih.gov/RefSeq Versioning informaiton: The latest release of RefSeq was released on May 13, 2009 with the release number of 35. RefSeq generates new releases roughly every two months. The dates of the three previous releases were: Release 34, March 12, 2009 Release 33, January 20, 2009 Release 32, November 17, 2008 RefSeq is a free database for the public.
NHSN BSI Risk Factors	NHSN Blood Stream Infection Risk Factors
Industry CDC Census 2010	2010 Industry coding system used by CDC (NIOSH and NCHS) for coding industry text. Industry describes an economic/business sector comprised of businesses/ enterprises concerned with the output of a specified category of products or services.
WHO ATC	WHO ATC
pan-Canadian Provider Qualification Types	This code system contains the list of provider qualifications used in the pan-Canadian specifications.
DEEDS506	Injury Activity
International Classification of Primary Care 1993 Portuguese	The International Classification of Primary Care (ICPC). Portuguese Translation. Denmark: World Organisation of Family Doctors, 1993.
WHO Adverse Reaction Terms	WHO Adverse Reaction Terms
ISO 11073-10101 Health informatics - Point-of-care	The nomenclature relates primarily to vital signs monitoring, but also includes semantics of other medical devices that are commonly used in acute care settings. There are multiple coding partitions each of which has a systematic name consisting of a set of base concepts and differentiating criteria.
NHSN SSI Anatomic Site	NHSN Surgical Site Infection Anatomic Site
US Department of Veterans Affairs	VHA Enterprise Reference Terminology is based on CHI standard terminologies (e.g., SNOMED-CT, LOINC, HL7, NDF-RT, etc.) when available and on VHA own code sets when necessary (e.g., allergens). All concepts used within the VHA clinical environment receive a VHA Unique IDentifier or VUID. VHA Enterprise Reference Terminology complies with the semantics of the HL7 message structure
International Classification of Primary Care, second edition (1998)	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
WHO rec# code with ASTM extension	WHO rec\# code with ASTM extension
The Read Codes Four Byte Set:	The Read Codes Four Byte Set consists of 4 alphanumeric characters. This version contains approximately 40,000 codes arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs
CDA_RUS	Coding system intended for use in the Russian clinical documents
International Classification for Nursing Practice	ICNP(r) is a combinatorial terminology, using a multi-axial structure. ICNP(r) provides standardized terms and codes for terms in two classifications that can be used to compose or create pre-coordinated concepts to represent observations and procedures, specifically, patient problems/nursing diagnoses, nursing interventions including those focused on assessment and actual or expected (goal) outcomes. The ICNP(r) Classification for Nursing Phenomena is used to compose concepts or statements to represent observations (nursing diagnoses, patient problems, patient status, patient outcomes). The ICNP(r) Nursing Actions Classification is used to compose concepts or statements to represent procedures (nursing interventions)
North American Industry Classification System	North American Industry Classification System(NAICS) for the United States, a new economic classification system that replaces the 1987 Standard Industrial Classification (SIC) for statistical purposes. NAICS is a system for classifying establishments by type of economic activity. Its purposes are: (1) to facilitate the collection, tabulation, presentation, and analysis of data relating to establishments, and (2) to promote uniformity and comparability in the presentation of statistical data describing the economy. NAICS will be used by Federal statistical agencies that collect or publish data by industry.
CEN ECG diagnostic codes	CEN ECG diagnostic codes
Health Canada Drug Id Number	**Description:** A Drug Identification Number (DIN) is a number assigned by Health Canada to a drug product prior to being marketed in Canada. It consists of eight digits (numbers) generated by a computer system in the Submission and Information Policy Division. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
CAMNCVS	CAM & Nursing Coding Vocabulary Set
National Uniform Billing Council, UB 92	National Uniform Billing Council, UB 92
Standard Occupation Code	The Standard Occupational Classification (SOC) system is used by Federal statistical agencies to classify workers into occupational categories for the purpose of collecting, calculating, or disseminating data. All workers are classified into one of over 820 occupations according to their occupational definition. To facilitate classification, occupations are combined to form 23 major groups, 96 minor groups, and 449 broad occupations. Each broad occupation includes detailed occupation(s) requiring similar job duties, skills, education, or experience. This code system replaced the older FIPSPUB92, which was withdrawn in February 2005.
Home Health Care	HHCC - Home Health Codes
DICOM Controlled Terminology	Coded concepts defined in PS 3.16 Digital Imaging and Communications in Medicine (DICOM): Part 16: Content Mapping Resource, Annex D: DICOM Controlled Terminology Definition
CAN/CSA-Z795-96	Nature of injury (NOI) codes, which are part of the Work Injury or Disease Information coding system (CAN/CSA-Z795-96 - R2003). The CSA code set includes 3 parts: Nature of injury (NOI), body part (BP), side of body (SB). For example: * NOI - Cut or laceration Injury = 03400 * BP - Upper Arm body part = 31100 * SOB - Left Side of Body = L The Body Part codes are qualified by the Side of Body codes code system, to be more precise in specifying the location of the injury being coded. Code set is maintained by the Canadian Standards Association (CSA). set is maintained by the Canadian Standards Association (CSA). The Canadian Standards Association 5060 Spectrum Way Mississauga, Ontario Canada L4W 5N6 Phone: (416) 747-4000 1-800-463-6727 Fax: (416) 747-2473
DICOM Class Label	DICOM Class Label
MeSH	Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004
WHO Adverse Reaction Terms Portuguese	WHO Adverse Drug Reaction Terminology (WHOART). Portuguese Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
Unified Medical Language	Unified Medical Language
International Classification of Primary Care 1993 Hebrew	The International Classification of Primary Care (ICPC). Hebrew Translation, Denmark: World Organisation of Family Doctors, 1993
International Classification of Primary Care 1993 Finnish	The International Classification of Primary Care (ICPC). Finnish Translation. Denmark: World Organisation of Family Doctors, 1993.
ICD-10 Dual Coding	ICD-10 allows dual coding. Refer to Section 3.1.3 of the ICD-10 Instruction Manual (2nd Edition, http://www.who.int/entity/classifications/icd/ICD-10\_2nd\_ed\_volume2.pdf). This OID identifies the code system that describes how to encode Dual Coding in a CD compatible expression (for Datatypes R2 CD only). An ICD-10 dual code expression SHALL consist of two ICD-10 codes separated by space. This code system SHALL NOT be used for single ICD-10 codes; the normal ICD-10 code system oid which is 2.16.840.1.113883.6.3 should be used in this case. Dual code expressions SHALL only be used per the rules described in the ICD-10 instruction manual. **An example CD:**<br></br> <example code="J21.8 B95.6" codeSystem="2.16.840.1.113883.6.260"><br></br> <originalText value="Staph aureus bronchiolitis"/><br></br> </example><br></br><br></br> Where:<br></br> J21.8 is: Acute bronchiolitis due to other specified organisms<br></br> B95.6 is: Staphylococcus aureus as the cause of diseases classified to other chapters
COSTART	COSTART
Medical Economics Drug Codes	Medical Economics Drug Codes
WHO Adverse Reaction Terms Spanish	WHO Adverse Drug Reaction Terminology (WHOART). Spanish Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
MedDRA	MedDRA is a five-level hierarchy of terms. MedDRA was developed as an ICH initiative and is maintained and distributed by the MedDRA Maintenance and Support Services Organization (MSSO). Versions - Versions are released twice per year and are identified by 2 numbers separated by a decimal point (e.g., 7.0, 7.1, 8.0, and 8.1). .0 releases may contain changes to the hierarchy. .1 releases will only contain additions, moves, and modifications of medical concept terms (Preferred Terms) and coding level terms (Lowest Level Terms). Concepts - Concepts are represented by a MedDRA code and a MedDRA term name. The MedDRA code is an eight digit numeric code. MedDRA codes are unique and are never reused. The MedDRA term name is a 100 character alphanumeric field used to describe the concept or term. Hierarchies - MedDRA is structured as a five level hierarchy. System Organ Classes (SOCs) are the broadest terms (e.g., Cardiac disorders, Investigations). The lowest level of the terminology is the Lowest Level Term (LLT) level. There are 26 SOCs and over 60,000 LLTs
Standard Billing Unit	NCPDP standard product billing codes of NCPDP field Unit of Measure (600-28). This billing code is assigned per product, placed in the Structured Product Label, and used in the pharmacy billing processing for consistent billing unit.
US Census Occupation Code	Coding system of United States Census Occupation Codes, published by the US Governmetn Bureau of the Census. Doucmentation and Crosswalk mapping between the COC and the SOC and NAICS code systems available at http://www.census.gov/hhes/www/ioindex/view.html
PH_RaceAndEthnicity_CDC	Codes for Race, authored and maintained by the CDC
ICPC2E 1998 Plus	International Classification of Primary Care, Version 2-Plus. Produced by NLM. Bethesda (MD): National Library of Medicine, UMLS project. This node has the various modifications and translations produced under it.
SNOMED topology codes (anatomic sites)	SNOMED topology codes (anatomic sites)
NHSN Hip Replacement	NHSN Hip Replacement
ICPC2-ICD10 Thesaurus (English)	Becker, H.W., C. van Boven, S.K. Oskam, I.M. Okkes, W. Hirs, H. Lamberts. ICPC2 - ICD10 Thesaurus, Version March, 2004. Amsterdam: Project "Adaptation ICPC, integration and implementation of ICPC2 and ICD10(-CM)." Department of General Practice, Academic
pan-Canadian Temporary Codes	These pan-Canadian codes are maintained in circumstances where the desired code is not yet available in another code system (HL7 code systems, LOINC, SNOMED, etc.) In general, the codes will be deprecated once an equivalent code is available in the preferred code system.
NHSN Procedure Category	NHSN Procedure Category
HIBCC	HIBCC
International Classification of Primary Care 1993 French	The International Classification of Primary Care (ICPC). French Translation. Denmark: World Organisation of Family Doctors, 1993.
CPT-5	CPT-5
ICPC2-ICD10 Thesaurus	A diagnostic Terminology for semi-automatic Double Coding in Electronic Patient Records The thesaurus is a part of the CD Rom: "ICPC in the Amsterdam Transition Project. Extended Version. IM Okkes, SK Oskam, H. Lamberts. Amsterdam: Academic Medical Center/University of Amsterdam. Department of Family Medicine", see also the web site http://www.transitieproject.nl for this application of the thesaurus. This bilingual (English/Dutch) ICPC2-ICD10 thesaurus is derived from an extended version of the CD-Rom ICPC in the Amsterdam Transition Project, that was published as a companion to ICPC-2-R by Oxford University Press (2005). As was the case with the former thesaurus (published in Dutch in 2003), the content of this new thesaurus may be copied for academic purposes, and be used for teaching and research under the usual referencing conditions. Any other and/or commercial use requires prior permission from the authors, represented by Dr. Inge Okkes (see below). It is strongly recommended that you first go through the ICPC Tutorial, the Manual and the Glossary, and consider printing them. Becker, H.W., C. van Boven, S.K. Oskam, I.M. Okkes, W. Hirs, H. Lamberts. ICPC2 - ICD10 Thesaurus, Version March, 2004. Amsterdam: Project "Adaptation ICPC, integration and implementation of ICPC2 and ICD10(-CM)." Department of General Practice, Academic
CDC Analyte Codes	CDC Analyte Codes
NOC	NOC - Nursing Outcome Codes
ICPC2E, Dutch Translation	Hirs, W., H.W. Becker, C. van Boven, S.K. Oskam, I.M. Okkes, H. Lamberts. International Classification of Primary Care 2E: 2nd ed. electronic. Dutch Translation. Amsterdam: Department of General Practice, Academic Medical Center/University of Amsterdam, D
ASTM E1238/ E1467 Universal	ASTM E1238/ E1467 Universal
ICPC2-ICD10 Thesaurus, 7-bit	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
DEEDS(old)	retired root for DEEDs from earlier work. Superceded.
WHO Adverse Reaction Terms French	WHO Adverse Drug Reaction Terminology (WHOART). French Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
ICPC2-ICD10 Thesaurus, Am Engl	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
METABOLIC SYNDROME	A collection of metabolic risk factors in one individual. The root causes of metabolic syndrome are overweight / obesity, physical inactivity, and genetic factors. Various risk factors have been included in metabolic syndrome. Factors generally accepted as being characteristic of this syndrome include abdominal obesity, atherogenic dyslipidemia, raised blood pressure, insulin resistence with or without glucose intolerance, prothrombotic state, and proinflammatory state.
CPT-4	American Medical Association's Current Procedure Terminology 4 (CPT-4) codes.
NHSN Spinal Fusion Approach	NHSN Spinal Fusion Approach
International Classification of Primary Care 1993 Spanish	The International Classification of Primary Care (ICPC). Spanish Translation. Denmark: World Organisation of Family Doctors, 1993.
MedDRA expanded	Medical Dictionary for Regulatory Activities Terminology (MedDRA), with expanded abbreviations, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004.
NANDA	The terminology consists of standardized terms and codes for patient problems or life processes expressed as nursing diagnoses. These data elements would be classified by HL7 as "observations". The taxonomy is multi-axial. It consists of 12 domains and 36 classes. All domains and classes are defined. There are 7 axes with definitions for each. Each nursing diagnosis consists of: a concept label or term expressed as a noun or a noun phrase; a definition of the term; a set of defining characteristics (signs and symptoms) of the diagnostic term; an approved list of modifiers of the term; a set of risk factors with definitions; and a set of related factors (or etiologies) for the term. The system preserves semantics by having robust review procedures and policies to ensure against semantic drift in the meanings of the encoded terms over time. NANDA as an organization is committed to updating the terminology on a regular biannual basis. NANDA has been in existence since 1973 and is thus the oldest developer of standardized language in nursing. Most other nursing language systems use many of the older NANDA terms in their vocabularies. The express purpose of the organization is to develop a comprehensive standardized nursing language that captures the conclusions that nurses make based on observations - in effect, the nursing diagnoses. The work is a continuing effort and diagnoses are revised, retired or added bi-annually. The codes are simple integers and are not linked to each other. If a diagnostic term is retired, the code is also retired. If a new diagnosis is added a new code is given to that term. If a diagnostic term is revised, the code is kept intact but the date of the revision is published alongside the term. Domains and classes are not coded.
Global Medical Device Nomenclature	http://www.gmdnagency.com/
Systematized Nomenclature of Dentistry (SNODENT)	Systematized Nomenclature of Dentistry (SNODENT) is owned, maintained and distributed by the American Dental Association (ADA). SNODENT is a vocabulary designed for use in the electronic environment - for electronic health and dental records. The intended purpose is to: * Provide standardized terms for describing dental disease * Capture clinical detail and patient characteristics * Permit analysis of patient care services and outcomes * To be interoperable with Electronic Health Records (EHR) and Electronic Dental Records (EDR) SNODENT licensing information can be found at: http://www.ada.org/8466.aspx URL for Official Source: http://www.ada.org/snodent.aspx
Occupation CDC Census 2010	2010 Occupation coding system used by CDC (NIOSH and NCHS) for coding occupation text. Occupation describes a set of activities or tasks that individuals are paid to perform or, if unpaid, define a person's contribution to a household/family business/community.
Nursing Management Minimum Data Set	The NMMDS is the minimum set of items of information with uniform definitions and categories concerning the specific dimension of the context of patient care delivery. It represents the minimum data used to support the management and administration of patient/nursing care delivery across all types of settings. The NMMDS is composed of seventeen (17) data elements organized into three categories: environment, nurse resources, and financial resources. See Tables 1-3 for the elements and related definitions organized by each categories. The NMMDS most appropriately focuses at the first level of accountability for patient/client/family/community nursing care: this may be the delivery unit, service, or center of excellence level. The NMMDS supports numerous constructed variables as well as aggregation of data at the unit, institution, network, and system, etc levels. This minimum data set provides the structure for the collection of uniform information that influences quality of patient care, directly and indirectly.
Food and Drug Administration Food Canning Establishments	Entered erroneously - do not use. The correct OID for this identifier system is 2.16.840.1.113883.4.345.
FDA K10	FDA K10
First DataBank Diagnostic Codes	First DataBank Diagnostic Codes
US Census Bureau	The Standard Industrial Classification Codes that appear in a company's disseminated EDGAR filings indicate the company's type of business. These codes are also used in the Division of Corporation Finance as a basis for assigning review responsibility for the company's filings. For example, a company whose business was Metal Mining (SIC 1000) would have its filings reviewed by staffers in A/D Office 4. Note that this code system is published both by the US Bureau of Labor Statistics (BLS) at http://www.sec.gov/info/edgar/siccodes.htm, and by the US Occupational & Safety Health Administration (OSHA) at http://www.osha.gov/pls/imis/sic\_manual.html.
DEEDS418	Systolic blood pressure special situation
DEEDS424	Respiratory rate special circumstances codes
MIME	IETF MIME media types
National drug codes	National drug codes
Unified Medical Language System	UMLS codes as CUIs making up the values in a coding system. More information may be found at http://www.nlm.nih.gov/research/umls/
NHSN Summary Data	NHSN Summary Data
URL	Universal Resource Locator (URL) schemes Currently there is no single authority for URL schemes. The authority for URL scheme assignments clearly lies within IANA or W3C and it is likely that a formal URL/URI assigning authority will be formed soon.
CLIP	CLIP
American Type Culture Collection	American Type Culture Collection
Brazilian Procedure Codes SUS	Brazilian Procedure Codes used in the National Health System
Online Product Identification Number Index of Nova Scotia	Codes to identify products and services that do not have DIN's and which need to be billed. http://www.atlanticpharmaceutical.ca/default.asp?mn=5.23
DEEDS427	Patient temperature route
ISO 4217 Currency Codes	ISO 4217 currency codes.
HCFA Procedure Codes (HCPCS)	The Healthcare Common Procedure Coding System (HCPCS) contains alpha-numeric codes used to identify those coding categories not included in the American Medical Association's CPT-4 codes (such as supplies) For example: E1093 - Wheelchair wide w/ foot rest Common Name - HCPCS Related Names, Versions, and Synonyms - Health Care Financing Administration Common Procedure Coding System Authoring/Maintenance Authority - US Health Care Financing Administration Coverage - Medical and Surgical Procedures, Supplies and Services License Fee(s) - Please review detailed description. Intended Use - Billing and claims processing for medical and surgical services and supplies Other Uses - Update Frequency - Generally, once a year.
Canadian Classification of Health Interventions	CCI - Canadian Classification of Health Interventions, developed to accompany ICD-10-CA, maintained by CIHI (Canadian Institute for Health Information). For example: sections 3.AA-3.BZ Diagnostic Imaging Interventions on the Nervous System 3.AN.^ ^.^ ^ Diagnostic Imaging Interventions on the Brain 3.AN.40. ^ ^ Magnetic Resonance Imaging, Brain Incudes: That for meninges, ventricles, cerebellum, brain stem, cisterna \[of brain\], posterior fossa MRI, brain 3.AN.40.VA without contrast 3.AN.40.VC following intravenous injection of contrast 3.AN.40.VZ following percutaneous injection of contrast CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca
International Classification of Primary Care 1993 Basque	The International Classification of Primary Care (ICPC). Basque Translation. Denmark: World Organisation of Family Doctors, 1993.
EUCLIDES	EUCLIDES
MDDID	Medispan Drug Descriptor ID Entry autogenerated to support Sources from the UMLS. Full metadata set still incomplete.
pan-Canadian Provider Types	This code system contains the list of provider types used in the pan-Canadian specifications.
International Classification of Primary Care, 1993 edition	The International Classification of Primary Care (ICPC). Denmark: World Organisation of Family Doctors, 1993. Various language translations are identified beneath this OID.
MedDRA German	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, German Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the German language version as encapsulated in the UMLS..
Occupational Data for Health (ODH)	The concepts representing the values supporting Occupational Data for Health, including Job Supervisory Level or Pay Grade (ODH) code system consists of data elements that describe a person's work information, structured to facilitate individual, population, and public health use; not intended to support billing.).
Active Ingredient Group Number	Codes for particular collections of active ingredients combined at specific strengths. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
Nursing Minimum Data Set	The NMDS is the minimum set of items of information with uniform definitions and categories concerning the specific dimension of the context of patient care delivery. It represents the minimum data used to support the management and administration of patient/nursing care delivery across all types of settings.
Multum Lexicon	Broadly, the fields and values in the Multum Lexicon and the VantageRx Database are intended to be available for use in any HL7 message that includes a reference to non-veterinary drug products or active ingredients that are either approved for sale by the FDA or readily available in the United States. The following inter-related definitions recently circulated by us to the HL7 Vocabulary Technical Committee explain the scope of what we mean by "drug product" and "active ingredient". (A definition for "drug ingredient" is also provided here because the definition of "active ingredient" is reliant on this term.) Drug Product A drug product is a manufactured or extemporaneously-compounded physiologically-active material intended by the preparer to achieve therapeutic, diagnostic, or preventative effects via biochemical mechanisms when applied to an epithelial surface or placed in an internal body space of a targeted organism. Drug Ingredient A drug ingredient is a chemical compound or biologic agent that occurs in a drug product. Active Ingredient An active ingredient is a drug ingredient that mediates one or more of the intended therapeutic, diagnostic, or preventative effects of a drug product and is present in sufficient quantities to achieve such effects according to the allopathic tradition of healthcare practice.
Euclides quantity codes	Euclides quantity codes
ISO/IEC 21000-6:2004(E) Rights Data Dictionary	ISO/IEC 21000-6:2004 describes a Rights Data Dictionary which comprises a set of clear, consistent, structured, integrated and uniquely identified terms to support the MPEG-21 Rights Expression Language (REL), ISO/IEC 21000-5. Annex A specifies the methodology for and structure of the RDD Dictionary, and specifies how further Terms may be defined under the governance of a Registration Authority, requirements for which are described in Annex C. Taken together, these specifications and the RDD Dictionary and Database make up the RDD System. Use of the RDD System will facilitate the accurate exchange and processing of information between interested parties involved in the administration of rights in, and use of, Digital Items, and in particular it is intended to support ISO/IEC 21000-5 (REL). Clause 6 describes how ISO/IEC 21000-6:2004 relates to ISO/IEC 21000-5. As well as providing definitions of terms for use in ISO/IEC 21000-5, the RDD System is designed to support the mapping of terms from different namespaces. Such mapping will enable the transformation of metadata from the terminology of one namespace (or Authority) into that of another namespace. Mapping, to ensure minimum ambiguity or loss of semantic integrity, will be the responsibility of the Registration Authority. Provision of automated trm look-up is also a requirement. The RDD Dictionary is a prescriptive dctionary, in the sense that it defines a single meaning for a trm represented by a particular RddAuthorized TermName, but it is also inclusive in that it can recognize the prescription of other Headwords and definitions by other Authorities and incorporates them through mappings. The RDD Dictionary also supports the circumstance that the same name may have different meanings under different Authorities. ISO/IEC 21000-6:2004describes audit provisions so that additions, amendments and deletions to Terms and their attributes can be tracked. ISO/IEC 21000-6:2004 recognizes legal definitions as and only as Terms from other Authorities that can be mapped into the RDD Dictionary. Therefore Terms that are directly authorized by the RDD Registration Authority neither define nor prescribe intellectual property rights or other legal entities.
NHSN Infection Type	NHSN Infection Type
Nursing Intervention Classification	NIC provides names and values for procedures/orders/service intent related to the treatment activities of nurses and other providers who may perform the same treatment activities. Names, definitions, and associated codes are attached for 486 interventions. Defining activities (anywhere from ten to several dozen) are listed for each of the interventions in the NIC classification book but are not attached to this document.
DEEDS422	Heart rate method
Chemical abstract codes	Chemical abstract codes
AHFS Pharmacologic-Therapeutic Classification	**Description:** The AHFS Pharmacologic-Therapeutic Classification has been in use in hospitals in the United States since its inception in 1959. An integral part of the American Hospital Formulary Service, the AHFS classification allows the grouping of drugs with similar pharmacologic, therapeutic, and/or chemical characteristics. Today, the AHFS classification is used by many people outside of hospitals.
NHSN KneeR eplacement	NHSN Knee Replacement
International Classification of Primary Care 1993 Norwegian	The International Classification of Primary Care (ICPC). Norwegian Translation. Denmark: World Organisation of Family Doctors, 1993.
International Classification of Primary Care 1993 Swedish	The International Classification of Primary Care (ICPC). Swedish Translation. Denmark: World Organisation of Family Doctors, 1993.
United States Postal Service	Coding system of defined postal zip codes for the United States of America.
GCDF	GCDF Dosage Form Code (2-character) a two-character alphanumeric column that represents a dosage form. The dosage form of a generic drug formulation describes the physical presentation of a drug, such as tablet, capsule, or liquid. It may also incorporate the delivery and release mechanism of the drug. A GCDF is associated to each GCN\_SEQNO to identify that component of the generic drug formulation.
SNOMED International	SNOMED International
GTIN Global Trade Item Number	The GS1 GTIN is a globally unique identifier of trade items. A trade item is any item (product or service) upon which there is a need to retrieve pre-defined information and that may be priced, or ordered, or invoiced at any point in any supply chain.
Euclides Lab method codes	Euclides Lab method codes
POS Codes	POS Codes
NHSN HAI Vocabulary	NHSN HAI Vocabulary used for Single Value bindingsto Observation Identifier
MedDRA Am Engl	Medical Dictionary for Regulatory Activities Terminology (MedDRA), American English Equivalents, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004 This is the English language version as encapsulated in the UMLS..
CDC Vaccine Codes	CDC Vaccine Codes
ISO 639-1 Alpha-2 Language Codes	Codes for the Representation of Names of Languages Part 1: Alpha-2 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. *DeprecationComment:* This code system is being deprecated, as the OID identifying it has been replaced with the correct ISO OID of 1.0.639.1
DEEDS408	Code for Acuity Assessment
NHSN Occasion Of Detection	NHSN Occasion Of Detection
International Classification of Primary Care 1993 Dutch	The International Classification of Primary Care (ICPC). Dutch Translation. Denmark: World Organisation of Family Doctors, 1993.
NCI Version of NDF-RT	The National Drug File RT (NDF-RT) is published by the US Veterans' Administration (VA). NDF-RT covers clinical drugs used at the VA. The NCI version of NDF-RT is used by NCI to provide automated terminology access to the Food and Drug Administration (FDA) Structured Product Label (SPL) initiative. NCI makes its version of NDF-RT available publicly thru the Web, download via FTP and via open APIs for Java, SOAP and HTTP.
Perioperative Nursing Data Set	The PNDS provides standardized terms and codes for patient problems/nursing diagnoses, nursing interventions including actual or expected (goal) outcomes. The PNDS provides standardized terms and codes for nursing diagnoses (a subset of NANDA), nursing interventions and outcomes. The outcomes and interventions are in a relational database. The PNDS intervention and outcome statements are attached in an Access Database. The NANDA diagnoses in the PNDS have already been registered by HL7.
Universal Product Code	Universal Product Code
ICCS	ICCS
ICHPPC-2	ICHPPC-2
Euclides Lab equipment codes	Euclides Lab equipment codes
Gold Standard's Clinical Pharmacology Monograph Number	Gold Standard's Clinical Pharmacology Monograph Number
International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)	The International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM), describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases. The ICD-10-CM codes can be used as the value of the Act.cd attribute.
ICD-10 American English	International Statistical Classification of Diseases and Related Health Problems (ICD-10): Americanized Version. 10th rev. Geneva (Switzerland): World Health Organization, 1998.
International Classification of Primary Care 1993 Hungarian	The International Classification of Primary Care (ICPC). Hungarian Translation. Denmark: World Organisation of Family Doctors, 1993.
ISBT	ISBT 128 is a coding system for blood components, hematopoietic progenitor cells and other tissues. It is comprised of an overall Application Specification, and labeling and coding documents for the separate sections: blood components, hematopoietic progenitor cells (draft), source plasma (draft) and tissues (draft). The documentation is supported by databases: Country/Collection Facility, Product Code (blood components), Product Code (hematopoietic progenitor sells), Product Code (source plasma), Product Code (tissues) and Special Testing. ISBT 128 is designed as a series of data structures that are designed to be technology-independent and can be used for bar coding, radio frequency tag encoding and electronic data interchange. The HL7 Blood Bank SIG is currently designing example messages that incorporate ISBT 128 coding. No changes of any kind will be needed to use ISBT 128 in HL7 messages.
MeasureImprovementNotation	Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.
MedicationRequest Course of Therapy Codes	MedicationRequest Course of Therapy Codes
GoalAcceptanceStatus	Codes indicating whether the goal has been accepted by a stakeholder.
Audit Event Source Type	The type of process where the audit event originated from.
Organization type	This example value set defines a set of codes that can be used to indicate a type of organization.
Risk Probability	Codes representing the likelihood of a particular outcome in a risk assessment.
Operation Outcome Codes	Operation Outcome codes used by FHIR test servers (see Implementation file translations.xml)
EvidenceDirectness	The quality of how direct the match is.
Missing Tooth Reason Codes	This value set includes sample Missing Tooth Reason codes.
ReferralMethod	The methods of referral can be used when referring to a specific HealthCareService resource.
CodeSystem/extra-security-role-type	This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere
MedicationKnowledge Status Codes	MedicationKnowledge Status Codes
Consent Scope Codes	This value set includes the four Consent scope codes.
HandlingConditionSet	Set of handling instructions prior testing of the specimen.
ResearchStudyPhase	Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.
Claim Type Codes	This value set includes Claim Type codes.
StandardsStatus	HL7 Ballot/Standards status of artifact.
Funds Reservation Codes	This value set includes sample funds reservation type codes.
QualityOfEvidenceRating	A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.
MedicationAdministration Performer Function Codes	MedicationAdministration Performer Function Codes
ExpansionProcessingRule	Defines how concepts are processed into the expansion when it's for UI presentation.
CodeSystem/dicom-audit-lifecycle	Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message,
Unit Type Codes	This value set includes a smattering of Unit type codes.
StatisticStatisticType	The type of a specific statistic.
Enteral Formula Additive Type Code	EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example.
Example Revenue Center Codes	This value set includes sample Revenue Center codes.
Admit source	This value set defines a set of codes that can be used to indicate from where the patient came in.
Exception Codes	This value set includes sample Exception codes.
SubscriptionTag	Tags to put on a resource after subscriptions have been sent.
ConformanceExpectation	Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.
Modifier type Codes	This value set includes sample Modifier type codes.
AllergyIntoleranceCertainty	Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.
Validation-type	What the target is validated against
Supply Type	This value sets refers to a Category of supply.
Goal priority	Indicates the level of importance associated with reaching or sustaining a goal.
Payment Adjustment Reason Codes	This value set includes smattering of Payment Adjustment Reason codes.
ResearchSubjectMilestone	Indicates the progression of a study subject through the study milestones.
ConditionVerificationStatus	The verification status to support or decline the clinical status of the condition or diagnosis.
Service category	This value set defines an example set of codes that can be used to classify groupings of service-types/specialties.
Immunization Evaluation Dose Status codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example.
Benefit Term Codes	This value set includes a smattering of Benefit Term codes.
SmartCapabilities	Codes that define what the server is capable of.
Payment Type Codes	This value set includes sample Payment Type codes.
Example Coverage Financial Exception Codes	This value set includes Example Coverage Financial Exception Codes.
Oral Site Codes	This value set includes a smattering of FDI oral site codes.
ResearchSubjectState	Indicates the progression of a study subject through a study.
Encounter type	This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided.
StatisticCertaintySubcomponentType	The subcomponent classification of quality of evidence rating systems.
ActionType	The type of action to be performed.
AuditEventOutcome	Indicates whether the event succeeded or failed.
SubscriberPolicyholder Relationship Codes	This value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).
Goal category	Example codes for grouping goals to use for filtering or presentation.
Encounter subject status	This example value set defines a set of codes that can be used to indicate the status of the subject within the encounter
StatisticStudyType	The type of study a statistic was derived from.
List Order Codes	Base values for the order of the items in a list resource.
Reason Medication Given Codes	This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.
Example Service Place Codes	This value set includes a smattering of Service Place codes.
Practitioner role	This example value set defines a set of codes that can be used to indicate the role of a Practitioner.
Benefit Type Codes	This value set includes a smattering of Benefit type codes.
Coverage SelfPay Codes	This value set includes Coverage SelfPay codes.
Location type	This example value set defines a set of codes that can be used to indicate the physical form of the Location.
Immunization Recommendation Status Codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example.
Flag Category	Example list of general categories for flagged issues. (Not complete or necessarily appropriate.)
chromosome-human	Chromosome number for human.
Financial Task Input Type Codes	This value set includes Financial Task Input Type codes.
MedicationUsage Administration Location Codes	MedicationUsage Administration Location Codes
MeasureDataUsage	The intended usage for supplemental data elements in the measure.
USCLS Codes	This value set includes a smattering of USCLS codes.
Discharge disposition	This value set defines a set of codes that can be used to where the patient left the hospital.
Need	The frequency with which the target must be validated
Contract Subtype Codes	This value set includes sample Contract Subtype codes.
ChargeItemCode	Example set of codes that can be used for billing purposes.
Validation-status	Status of the validation of the target against the primary source
PlanDefinitionType	The type of PlanDefinition.
MedicationDispense Performer Function Codes	MedicationDispense Performer Function Codes
Example Related Claim Relationship Codes	This value set includes sample Related Claim Relationship codes.
CoverageEligibilityResponse Auth Support Codes	This value set includes CoverageEligibilityResponse Auth Support codes.
RejectionCriterion	Criterion for rejection of the specimen by laboratory.
Adjudication Reason Codes	This value set includes smattering of Adjudication Reason codes.
AdverseEventCausalityMethod	TODO.
Observation Reference Range Meaning Codes	This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population.
CommunicationTopic	Codes describing the purpose or content of the communication.
Form Codes	This value set includes a sample set of Forms codes.
CatalogType	The type of catalog.
AllergyIntolerance Clinical Status Codes	Preferred value set for AllergyIntolerance Clinical Status.
FamilyHistoryAbsentReason	Codes describing the reason why a family member's history is not available.
Nutrition intake category codes	NutritionIntake Category Codes
Contract Content Derivation Codes	This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.
Benefit Category Codes	This value set includes examples of Benefit Category codes.
MaxOccurs	Flags an element as having unlimited repetitions.
AllergyIntolerance Verification Status	The verification status to support or decline the clinical status of the allergy or intolerance.
ClaimPayeeResourceType	The type of Claim payee Resource.
StatisticSynthesisType	Types of combining results from a body of evidence (eg. summary data meta-analysis).
Supply Item Type	This value sets refers to a specific supply item.
HumanNameAssemblyOrder	A code that represents the preferred display order of the components of a human name.
Basic Resource Types	This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts.
QuestionnaireItemUsageMode	Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item.
Special arrangements	This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.
AllergyIntoleranceSubstanceExposureRisk	The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products).
AdverseEventSeriousness	Overall seriousness of this event for the patient.
Example Diagnosis Related Group Codes	This value set includes example Diagnosis Related Group codes.
ResearchSubjectStateType	Identifies the kind of state being refered to.
MatchGrade	A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not.
Provenance participant type	The type of participation a provenance participant.
CommunicationNotDoneReason	Codes for the reason why a communication did not happen.
MedicationRequest Category Codes	MedicationRequest Category Codes
CodeSystem/iso-21089-lifecycle	Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication). This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.
Example Program Reason Codes	This value set includes sample Program Reason Span codes.
ExpansionParameterSource	Declares what the source of a parameter is.
StatisticCertaintySubcomponentRating	The quality rating of the subcomponent of a quality of evidence rating.
MeasurePopulationType	The type of population.
Observation Category Codes	Observation Category codes.
Coverage Copay Type Codes	This value set includes sample Coverage Copayment Type codes.
AlternativeCodeKind	Indicates the type of use for which the code is defined.
Benefit cost applicability	Whether the cost applies to in-network or out-of-network providers.
DeviceDefinitionParameterGroup	Codes identifying groupings of parameters; e.g. Cardiovascular.
ContractDataMeaning	How a resource reference is interpreted when evaluating contract offers.
MedicationRequest Status Reason Codes	MedicationRequest Status Reason Codes
UsageContextType	A code that specifies a type of context being specified by a usage context.
CharacteristicMethod	The method used to determine the characteristic(s) of the variable.
ChoiceListOrientation	Direction in which lists of possible answers should be displayed.
StrengthOfRecommendationRating	A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.
PayeeResourceType	The type of payee Resource.
Test script profile destination type	This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript.
ActivityDefinitionCategory	High-level categorization of the type of activity.
VerificationResult Communication Method	Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated.
SpecialValues	A set of generally useful codes defined so they can be included in value sets.
CodeSystem/payeetype	This value set includes sample Payee Type codes.
Validation-process	The primary process by which the target is validated
Consent Action Codes	This value set includes sample Consent Action codes.
MedicationAdministration Location Codes	MedicationAdministration Location Codes
Endpoint Connection Type	This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.
DefinitionStatus	Codes identifying the lifecycle stage of a definition.
AdverseEventCategory	Overall categorization of the event, e.g. product-related or situational.
Claim Care Team Role Codes	This value set includes sample Claim Care Team Role codes.
Consent Vefication Codes	This value set includes base Consent Verification codes.
AuditEventEntityRole	Code representing the role the entity played in the audit event.
CodeSystem/diagnosis-role	This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.
AdverseEventSeverity	The severity of the adverse event itself, in direct relation to the subject.
Immunization Subpotent Reason	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example.
Example Claim SubType Codes	This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation.
MedicationKnowledge Package Type Codes	MedicationKnowledge Package Type Codes
Digital Media Category	Codes for high level media types - whether the media is an image, video, or audio.
CompositeMeasureScoring	The composite scoring method of the measure.
GoalRelationshipType	Types of relationships between two goals.
DefinitionTopic	High-level categorization of the definition, used for searching, sorting, and filtering.
MedicationKnowledge Characteristic Codes	MedicationKnowledge Characteristic Codes
Condition Category Codes	Preferred value set for Condition Categories.
Implant Status	A set codes that define the functional status of an implanted device.
Immunization Evaluation Dose Status Reason codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example.
Contract Action Codes	This value set includes sample Contract Action codes.
Goal achievement status	Describes the progression, or lack thereof, towards the goal against the target.
Program	This value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties.
Payment Status Codes	This value set includes a sample set of Payment Status codes.
SubscriptionStatusAtEvent	A status code for the state of the Subscription.
AdverseEventCausalityAssessment	Codes for the assessment of whether the entity caused the event.
Adjudication Value Codes	This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc.
SubscriptionChannel Type Codes	Codes to represent subscription error details
Network Type Codes	This value set includes a smattering of Network type codes.
CopyNumberEvent	Copy Number Event.
ResearchStudyPrimaryPurposeType	Codes for the main intent of the study.
ResearchStudyObjectiveType	Codes for the kind of study objective.
Audit event entity type	Code for the entity type involved in the audit event.
Contract Signer Type Codes	This value set includes sample Contract Signer Type codes.
StatisticCertaintyRating	The relative quality of the statistic.
Example Procedure Type Codes	This value set includes example Procedure Type codes.
DoseAndRateType	The kind of dose or rate specified.
Medication request administration location codes	MedicationRequest Administration Location Codes
Example Diagnosis on Admission Codes	This value set includes example Diagnosis on Admission codes.
Endpoint Payload Type	This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.
Insurance plan type	This example value set defines a set of codes that can be used to indicate a type of insurance plan.
StatisticAttribute Estimate Type	Method of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation.
Contact entity type	This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.
ResourceSecurityCategory	Provides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource.
Example Message Reason Codes	Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.
StatisticsCode	The statistical operation parameter -"statistic" codes.
Immunization Funding Source	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example.
Consent PolicyRule Codes	This value set includes sample Regulatory consent policy types from the US and other regions.
Appointment cancellation reason	This example value set defines a set of reasons for the cancellation of an appointment.
Contract Type Codes	This value set includes sample Contract Type codes.
List Empty Reasons	General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).
MeasureScoring	The scoring type of the measure.
Diet	This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.
ServiceProvisionConditions	The code(s) that detail the conditions under which the healthcare service is available/offered.
Structure Definition Use Codes / Keywords	Structure Definition Use Codes / Keywords
Push-type-available	Type of alerts/updates the primary source can send
Can-push-updates	Ability of the primary source to push updates/alerts
Adjudication Error Codes	This value set includes a smattering of adjudication codes.
Condition Clinical Status Codes	Preferred value set for Condition Clinical Status.
AlternativeCodeKind	Indicates the type of use for which the code is defined.
CommunicationCategory	Codes for general categories of communications such as alerts, instructions, etc.
Test script operation code	This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.
Example Use Codes for List	Example use codes for the List resource - typical kinds of use.
Claim Information Category Codes	This value set includes sample Information Category codes.
Audit Event ID	Event Types for Audit Events - defined by DICOM with some FHIR specific additions.
Immunization Origin Codes	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine. This value set is provided as a suggestive example.
Financial Task Codes	This value set includes Financial Task codes.
Subscription Error Codes	Codes to represent subscription error details
Immunization Program Eligibility	The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example.
Consent Category Codes	This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes; HL7 VALUE SET: ActConsentType(2.16.840.1.113883.1.11.19897); examples of US realm consent directive legal descriptions and references to online and/or downloadable forms such as the SSA-827 Authorization to Disclose Information to the Social Security Administration; and other anticipated consent directives related to participation in a clinical trial, medical procedures, reproductive procedures; health care directive (Living Will); advance directive, do not resuscitate (DNR); Physician Orders for Life-Sustaining Treatment (POLST)
Coverage Class Codes	This value set includes Coverage Class codes.
Example Diagnosis Type Codes	This value set includes example Diagnosis Type codes.
Example Payment Type Codes	This value set includes example Payment Type codes.
EvidenceVariableRole	The role that the assertion variable plays.
Common Tags	Common Tag Codes defined by FHIR project
SupplyRequestReason	The reason why the supply item was requested.
FHIRDeviceStatusReason	The availability status reason of the device.
LibraryType	The type of knowledge asset this library contains.
Substance Category Codes	Substance category codes
ConditionState	Enumeration indicating whether the condition is currently active, inactive, or has been resolved.
MeasureType	The type of measure (includes codes from 2.16.840.1.113883.1.11.20368).
Episode of care type	This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.
sequenceStatus	Codes providing the status of the variant test result.
Designation Usage	Preferred value set for Condition Categories.
Contract Actor Role Codes	This value set includes sample Contract Actor Role codes.
ContainerCap	Color of the container cap.
GuideParameterCode	Code of parameter that is input to the guide.
Process Priority Codes	This value set includes the financial processing priority codes.
Test script profile origin type	This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript.
Contract Term Type Codes	This value set includes sample Contract Term Type codes.
Primary-source-type	Type of the validation primary source
ResearchStudyReasonStopped	Codes for why the study ended prematurely.
Participant type	This value set defines a set of codes that can be used to indicate how an individual participates in an encounter.
StateChangeReason	Indicates why the state of the subject changed.
Surface Codes	This value set includes a smattering of FDI tooth surface codes.
Contract Term Subtype Codes	This value set includes sample Contract Term SubType codes.
Example Vision Prescription Product Codes	This value set includes a smattering of Prescription Product codes.
Failure-action	The result if validation fails
Example Provider Qualification Codes	This value set includes sample Provider Qualification codes.
Service type	This value set defines an example set of codes of service-types.
MaterialForm	A value representing the state (solid, liquid, gas) and nature of the material. *Open Issue:* There exist no codes in the repository for this coding system; should it be removed?
Encounter Acuity	The level of resource intensiveness of patient care. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. No content.
ISO 3166 2 Character Country Codes	Two character country codes Note that this OID was erroneously entered into HL7 some years ago, and has recently been replaced by 1.0.3166.1 at the request of ISO.
ISO 3166 Numeric country Codes	Numeric country codes Note that this was erroneously entered into the HL7 system some years ago and has been replaced by 1.0.3166.1.2.1 at the request of ISO.
EncounterAccident	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. No content.
VocabularyDomainQualifier	Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain. Code system retired.
DataType	Code system retired.
Country	The territory of a sovereign nation. Note that this has been deprecated in favor of using the ISO 3166 Country codes - 1.0.3166.1 iso3166-1
ISO 4217 Currency code, HL7 use	ISO 4217 currency code Created prior to ISO ruling on OIDs for ISO code tables defined in ISO standards. Recommend using 1.0.4217 iso4217 code system instead.
MaterialType	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. This is outside the hierarchy and there's already an equivalent domain MaterialEntityClass in the right hierarchy. The corresponding code system is empty.
Currency	The currency unit as defined in ISO 4217. Created prior to ISO ruling on OIDs for ISO code tables defined in ISO standards. Retired. Replaced by 1.0.4217 iso4217.
ISO 3166 3 Character Country Codes	Three character country codes Note that this was erroneously entered into the HL7 system some years ago and has been replaced by 1.0.3166.1.2.3 at the request of ISO.
HL7Workgroup	An HL7 administrative unit that owns artifacts in the FHIR specification.
Concept Domains	Concept Domains - includes both v2 abd v3 concept domains
HL7 Terminology Maintenance Infrastructure Vocabulary	Codes that may have been strings or other types of data in pre-existing tooling for V3 and V2 terminology maintenance, and moved to codes in this code system for proper handling in the FHIR based UTG maintenance facilities.
UTG Specific Concept Properties	A set of concept properties used by UTG to maintain legacy terminology distribution systems
V2 Table List	Master List of V2 Tables
routeOfAdministration	Code system of concepts which specify the route of administration. Used in HL7 Version 2.x messaging in the RXR segment.
ethnicGroup	Code system of concepts further defining a patient's ancestry. In the US, a current use is to use these codes to report ethnicity in line with US federal standards for Hispanic origin. Used for HL7 Version 2 messaging in the PID segment.
organizationUnitType	HL7-defined code system of concepts which identify an environment in which a provider acts in a specified role. The provider environment is not the specialty for the provider. This is intended to allow communication of this information when the provider information may not have been communicated previously in a master file, and is used to support international requirements. Used in HL7 Version 2 messaging in the PRT and ROL segments.
degreeLicenseCertificate	Code system of concepts specifying an educational degree (e.g., MD). Used in the CNN datatype (names and identifiers of clinicians) in Version 2 messaging. Used in HL7 Version 2.x messaging in the CNN segment; note that in releases of HL7 prior to 2.3.1, was also used in person names (XPN), but this use was deprecated, then withdrawn in 2.7.
systemInducedContaminants	Code system of concepts that identify the specimen contaminant identifier associated with the specimen in the container. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
taxStatus	Code system of concepts used to specify the tax status of the provider. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging.
specialProgram	Code system of concepts used to record a health insurance program required for healthcare visit reimbursement. Used in HL7 Version 2.x messaging in the PV2 segment.
nameType2	HL7-defined code system of concepts for types of names for persons. Used in HL7 Version 2.x messaging in the XPN, PPN, XCN, PID and MRG segments.
bloodUnitType	HL7-defined code system of concepts used to specify the type of blood unit. Used in the Blood Unit Information (BUI) segment in HL7 Version 2.x messaging.
diagnosisClassification	Code system of concepts used to classify whether a patient visit can be related to a diagnosis. Used in HL7 Version 2.x messaging in the DG1 segment.
maritalStatus	Code system of concepts specifying a person's marital (civil/legal) status. Used in HL7 Version 2.x messages in the PID segment.
equipmentStateIndicator	HL7-defined code sytem of cocepts that specify the type of measurement of the state of an automated laboratory instrument. Used in HL7 Version 2.x messaging in the INV segment.
drgstatusAdmission	Code system of concepts specifying the admission status for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
eventType	HL7-defined code system of concepts specifying the trigger event for Version 2.x interface messages. Used in HL7 Version 2.x messaging in the MSH segment.
transactionType	Code system of concepts specifying a type of financial transaction. Used in HL7 Version 2.x messaging in the FT1 segment.
telecommunicationUse	HL7-defined code system of concepts for specifying a specific use of a telecommunication number. Best practice is to use this concept whenever a telecommunication number or access string is specified. Used in HL7 Version 2.x messaging in the XTN segment.
publicity	Code system of concepts specifying a level of publicity of information about a patient for a specific visit. Used in HL7 Version 2.x messaging in the PV2 and PD1 segments.
artificialBlood	Code system of concepts that identify the artificial blood identifier associated with the specimen. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
confidentialityCodes	Code system of concepts specifying the degree to which special confidentiality protection should be applied to the observation. Used in HL7 Version 2.x messaging in the OM1 and ORC segments.
bodySite	HL7-defined code system of concepts that specify a body site from which a specimen is obtained. Used in HL7 Version 2.x messaging in the OBX and CH7 segments.
masterFileIdentifierCodes	HL7-defined code system of concepts which are represented by codes identifying HL7 Versions 2.x Master Files. Used in HL7 Version 2.x messaging in the MFI segment.
allowSubstitution	HL7-defined code system of concepts which specify whether substitutions are allowed and, if so, the type of substitutions allowed. Used in HL7 Version 2.x messaging in the RXO segment.
dayType	Code system of concepts which specify whether the days are denied, pending or approved. Used in HL7 Version 2.x messaging in the DTN segment.
mimeTypes	Code system of concepts specifying the general type of data. Used in HL7 Version 2.x messaging in the RP and ED datatypes.
environmentalFactors	Code system of concepts that identify the other environmental factors associated with the specimen in a specific container, e.g., atmospheric exposure. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
processingType	HL7-defined code system of concepts identifying the processing type that applies to the test code. If this attribute is omitted, then regular production is the default. Used in HL7 Version 2.x messaging in the Test Code Configuration (TCC) segment.
providerAdjustmentReason	Code system of concepts used to specify the reason for this adjustment. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging.
identifierType	HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON.
visitPriority	Code system of concepts used to define a relative level of urgency applied to a patient visit. Used in HL7 Version 2.x messaging in the PV2 segment.
invoiceProcessingResultsStatus	Code system of concepts used to specify the processing status for an Invoice Processing Result. Used in the Invoice Processing Result (IPR) segment in HL7 Version 2.x messaging.
product-serviceStatus	Code system of concepts used to specify the processing status for the Product/Service Code. Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging.
administrativeSex	Code system of concepts specifying a patient's sex for administrative purposes. Used in HL7 Version 2.x messages in the PID segment.
limitationTypeCode	HL7-defined code system of concepts specifying the type of limitation. Used in HL7 Version 2.x messaging in the DPS segment.
payeeRelationshipToInvoice	Code system of concepts used to specify the relationship to the invoice for Person Payee Types. Used in the Payee Information (PYE) segment in HL7 Version 2.x messaging.
patientStatus	Code system of concepts used to define the state of a care episode for a patient. Used in HL7 Version 2.x messaging in the PV2 segment.
paymentMethod	Code system of concepts used to specify the method for the movement of payment. Used in the Payment Information (PMT) segment in HL7 Version 2.x messaging.
adjustmentCategory	Code system of concepts used to specify the category of adjustment and is used to assist in determining which table is used for Adjustment Reason. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging.
telecommunicationEquipmentType	HL7-defined code system of concepts for specifying a type of telecommunication equipment. Best practice is to use this concept whenever a telecommunication number or access string for particular equipment is specified. Used in HL7 Version 2.x messaging in the XTN segment.
analyteRepeatStatus	HL7-defined code system of concepts identifying the repeat status for the analyte/result (e.g. original, rerun, repeat, reflex). The following are assumptions regarding the table values: Repeated without dilution — performed usually to confirm correctness of results (e.g., in case of results flagged as "Panic" or mechanical failures). Repeated with dilution — performed usually in the case the original result exceeded the measurement range (technical limits). Reflex test — this test is performed as the consequence of rules triggered based on other test result(s). Used in HL7 Version 2.x messaging in the Test Code Detail (TCD) segment.
allergyClinicalStatus	Code system of concepts specifying the verification status for the allergy. Used in HL7 Version 2.x messaging in the IAM segment.
languageProficiency	HL7-defined code system of concepts which specify a level of knowledge that a Staff Member possesses with respect to their language ability. Used in HL7 Version 2 messaging in the LAN segment.
specialHandling	Code system of concepts describing how a specimen and/or container needs to be handled from the time of collection through the initiation of testing. Used in HL7 Version 2.x messaging in the SPM, SAC, PAC and OM4 segments.
moneyOrPercentageIndicator	HL7-defined code system of concepts which specify whether the amount is currency or a percentage. Used in HL7 Version 2.x messaging in the MOP segment.
trayType	HL7-defined code system of concepts which specify whether the type of diet. Used in HL7 Version 2.x messaging in the ODT segment.
natureOfServiceTestObservation	Code system of concepts specifying an identification of a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations, typically used as an indicator for Master Files. Used in HL7 Version 2.x messaging in the OM1 segment.
date-timeSelectionQualifier	HL7-defined code system of conceptss that allow the specification of certain types of values within the date/time range. Used in HL7 Vesion 2 messaging in the QRF segment.
addressExpirationReason	Code system of concepts specifying the reason this address was marked as "ended". Used in HL7 Version 2.x messaging in the XAD segment.
derivedSpecimen	HL7-defined code system of concepts which specify the parents and children for diagnostic studies, especially in microbiology, where the initial specimen (e.g., blood) is processed to produce results (e.g., the identity of the bacteria grown out of the culture). The process also produces new "specimens" (e.g., pure culture of staphylococcus, and E. coli), and these are studied by a second order process (bacterial sensitivities). The parents (e.g., blood culture) and children (e.g., penicillin MIC) are identified in such cases. Used in HL7 Version 2.x messaging in the OM4 segment.
administrationDevice	Code system of concepts which specify the mechanical device used to aid in the administration of the drug or other treatment. Common examples are IV-sets of different types. Used in HL7 Version 2.x messaging in the RXR segment.
incidentType	HL7-defined code system of concepts which specify a classification of types of incidents. Used in HL7 Version 2 messaging in the RMI segment.
specimenComponent	Code system of concepts that identify the specimen component, e.g., supernatant, sediment, etc. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
local-remoteControlState	HL7-defined code system of concepts that identify the current state of control associated with the equipment. Equipment can either work autonomously ('Local' control state) or it can be controlled by another system, e.g., LAS computer ('Remote' control state). Used in the Equipment Detail (EQU) segment in HL7 Version 2.x messaging.
signatorysRelationshipToSubject	Code system of concepts specifying the relationship of the consenter to the subject. Used in HL7 Version 2 messaging in the CON segment.
segmentAction	HL7-defined code system of concepts specifying actions to be applied for segments when an HL7 version 2 interface is operating in "action code mode" (a kind of update mode in the Standard). Used in HL7 Version 2.x messaging in the RXA, RXV, LCH, IAM, ARV, IN1 and OH1 segments.
Quantity Units	HL7-defined code system of concepts specifying the adjustment quantity.
orderStatus	HL7-defined code system of concepts specifying the status of an order. The purpose of these values are to report the status of an order either upon request (solicited), or when the status changes (unsolicited). The values are not intended to initiate action. It is assumed that the order status value always reflects the status as it is known to the sending application at the time that a message is sent. Only the filler can originate these values. Used in HL7 Version 2.x messaging in the ORC segment.
patientClass	Code system of concepts used by systems to categorize patients by site in HL7 Version 2.x interfaces in the PV1 segment.
itemStatus	Code system of concepts specifying the status (useful for reporting and item usage purposes) that applies to an item. Used in HL7 Version 2.x messaging in the ITM segment.
auto-DilutionType	Code system of vendor-defined codes that specify the pre‑configured dilution to be applied on the instrument, which can be used instead of a numeric declaration. Used in Version 2 messaging in the TCD segment.
reasonForStudy	HL7-defined code system of concepts that provide additional information to the universal service identifier on why a test, study or review was ordered. Initial values are to support the IHE LCC LAB-7 transaction.
orderStatusModifier	HL7-defined code system of concepts used to further define the status identified in ORC-5. Used in HL7 Version 2 messaging in the ORC segment.
drgProcedureRelevance	Code system of concepts specifying the relevance of this particular procedure for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the PR1 segment.
purgeStatus	Code system of concepts used to define the state of a visit relative to its place in a purge workflow. Used in HL7 Version 2.x messaging in the PV2 segment.
processingMode	HL7-defined code system of concepts that indicate an archival process or an initial load process. Used in HL7 Version 2.x messaging in the PT datatype.
product-servicesClarification	Code system of concepts used to specify the Product/Service Code. Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging.
continuationStyle	HL7-defined code system of concepts identifying whether it is a fragmented message or part of an interactive continuation message. Used in HL7 Version 2.x messaging in the Continuation Pointer (DSC) segment.
governmentReimbursementProgram	Code system of concepts which specify codes that indicate an agency that the practitioner is authorized to bill for medical services. Existing codes only for use in the United States. Used in HL7 Version 2.x messaging in the PRA segment.
alertLevel	HL7-defined code system of concepts that identify the highest level of the alert state (e.g.,highest alert severity) that is associated with the indicated equipment (e.g. processing event, inventory event, QC event). Used in the Equipment Detail (EQU) and Notification Detail (NDS) segments in HL7 Version 2.x messaging.
treatment	Code system of concepts that identify the specimen treatment performed during lab processing. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
drgTransferType	HL7-defined code system of concepts which specify a type of hospital receiving a transfer patient, which affects how a facility is reimbursed under diagnosis related group (DRG’s), for example, exempt or non-exempt. Used in HL7 Version 2 messaging in the DRG segment.
productionClass	Code system of concepts specifying the code and/or text indicating the primary use for which the living subject was bred or grown. Used in HL7 Version 2.x messaging in the PID segment.
package	Code system of concepts specifying the packaging unit in which this inventory supply item can be ordered or issued when purchased from the vendor in the related vendor segment. Used in HL7 Version 2.x messaging in the PKG segment.
administrationMethod	Code system of concepts which specify the specific method requested for the administration of the drug or treatment to the patient. Used in HL7 Version 2.x messaging in the RXR segment.
addressUsage	HL7-defined code system of concepts specifying how an address is intended to be used. Used in HL7 Version 2.x messaging in the XAD segment.
dietCodeSpecificationType	HL7-defined code system of concepts which specify whether the type of diet. Used in HL7 Version 2.x messaging in the ODS segment.
substitutionStatus	HL7-defined code system of concepts which specify the substitution status. Used in HL7 Version 2.x messaging in the RXE, RXD, and RXG segments.
coordinationOfBenefits	Code system of concepts specifying whether this insurance works in conjunction with other insurance plans or if it provides independent coverage and payment of benefits regardless of other insurance that might be available to the patient. Used in HL7 Version 2.x messaging in the IN1 segment.
userAuthenticationCredentialType	HL7-defined code system of concepts specifying a type of user authentication credential. Used in HL7 Version 2.x messaging in the UAC segment.
diagnosisPriority	Code system of concepts that identify the significance or priority of the diagnosis code. Note that the codes are numeric, and the number of the code represents the ordinal priority of the associated diagnosis. Used in the DG1 segment in HL7 Version 2.x messaging. The predefined codes are the most common, and just a starter set, as the codes are an unbounded list; additional ranked procedures may be signified by incrementing the code value as needed.
equipmentState	HL7-defined code system of concepts that identify the status the equipment was in at the time the transaction was initiated. Used in HL7 Version 2.x messaging in the EQU segment.
languageAbility	Code system of concepts which specify codes that indicate the ability that a Staff Member possesses with respect to the language. Used in HL7 Version 2.x messaging in the LAN segment.
tissueType	HL7-defined code system of concepts which specify a type of tissue removed from a patient during a procedure. Used in HL7 Version 2 messaging in the PR1 segment.
additivePreservative	HL7-defined code system of concepts specifying any additive introduced to the specimen before or at the time of collection. These additives may be introduced in order to preserve, maintain or enhance the particular nature or component of the specimen. Used in HL7 Version 2.x messaging in the SPM and SAC segments.
eventExpected	HL7-defined code system of concepts used to communicate whether an event has been judged to be expected or unexpected. Used in HL7 Version 2.x messaging in the PEO segment.
alternateCharacterSets	HL7-defined code system of concepts used to specify the character set(s) in use. Includes both single-byte and double-byte characters sets, and used in Version 2.x messaging in the MSH segment.
priceType	HL7-defined code system of concepts used to identify the intent for the dollar amount on a pricing transaction. Used in HL7 Version 2.x messaging in the CP datatype.
drgGroupingStatus	Code system of concepts specifying the status of the use of the gender information for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
admissionType	Code system of concepts specifying the circumstances under which the patient was or will be admitted. Used in HL7 Version 2.x messaging in the PV1 segment.
drgProcedureDeterminationStatus	Code system of concepts specifying the status of the use of this particular procedure for the diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the PR1 segment.
supplierType	Code system that Identifies the type of supplier that will distribute the supply items associated to a contract number. Used in HL7 Version 2.x messaging in the CTR segment.
religion2	Code system of concepts specifying a person's religion. Used in HL7 Version 2.x messaging in the PID segment.
stockLocation	Code system of concepts specifying a stock location for older Version 2 messaging systems; not used after version 2.2 of the Standard.
processingConsideration	Code system of concepts used to specify special processing requested of Payer for this Product/Service Line Item (e.g., hold until paper supporting documentation is received by Payer). Used in the Product/Service Line Item (PSL) segment in HL7 Version 2.x messaging.
organizationalNameType	Code system of concepts used to specify the type of name for an organization i.e., legal name, display name. Used in HL7 Version 2.x messaging in the XON and PD1 segments.
relationalConjunction	HL7-defined code system of concepts used with relationalOperator values to group more than one segment field name. Used in HL7 Version 2.x messaging in the QSC segment.
eventSeriousness	HL7-defined code system of concepts used by a sender to designate an event as serious or significant. Used in HL7 Version 2.x messaging in the PEO segment.
procedureDrgType	HL7-defined code system of concepts which specify a procedure’s priority ranking relative to its DRG. Used in HL7 Version 2 messaging in the PR1 segment.
containerStatus	HL7-defined code system of concepts that identify the status of the unique container in which the specimen resides at the time the transaction was initiated. Used in the Interaction Specimen Container Detail (SAC) segment in HL7 Version 2.x messaging.
commentType	Code system of concepts that identify the type of comment text being sent in the specific comment record. Used in the Notes and Comments (NTE) segment in HL7 Version 2.x messaging.
schoolType	Code system of concepts which specify a categorization of an academic institution that grants a degree to a Staff Member. Used in HL7 Version 2.x messaging in the EDU segment.
rxComponentType	HL7-defined code system of concepts which specify the RX component type. Used in HL7 Version 2.x messaging in the RXC segment.
deviceDataState	Code system of concepts that define the state of the data as provided from a device. Used in HL7 Version 2.x messaging in the SDD segment.
telecommunicationExpirationReason	Code system of concepts specifying the reason this contact number/email was marked as "ended". Used in HL7 Version 2.x messaging in the XTN segment.
name-addressRepresentation	HL7-defined code system of concepts specifying an indication of the representation provided by the data item. Used in HL7 Version 2.x messaging in the PPN, XAD, XCN and XON segments.
annotations	Code system of concepts specifying the coded entry associated with a given point in time during the waveform recording. Used in HL7 Version 2.x messaging in the Observation Result (OBX) Another Observation (ANO) segments.
appointmentType	Code system of concepts used in an appointment request to describe the kind of appointment. Used in HL7 Version 2.x messaging in the ARQ segment.
bpObservationStatusCodesInterpretation	HL7-defined code system of concepts used to specify the interpretation for the blood product observation status codes. A status is considered preliminary until a blood product has reached a final disposition for the patient. For example, when the product is first cross-matched and a status message is sent, it would be considered preliminary. When the product is dispensed to the patient, that status would also be considered preliminary. However, once the product is transfused, the status would be considered final. Used in the Blood Product Dispense Status (BPX) and Blood Product Transfusion/Disposition (BTX) segments in HL7 Version 2.x messaging.
cyclicEntryExitIndicator	HL7-defined code system of concepts used to specify if this service request is the first or last service request in a cyclic series of service requests. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging.
levelOfCare	Code system of concepts used to identify the level of care a patient may be afforded when assigned to this location definition. Used in HL7 Version 2.x messaging in the LCH segment.
checkDigitScheme	HL7-defined code system of concepts specifying the check digit scheme employed. Used in HL7 Version 2.x messaging in PPN, XCN and XON segments.
preferredSpecimen-AttributeStatus	HL7-defined code system of concepts that indicate whether a Specimen/Attribute is Preferred or Alternate for collection of a particular specimen. Used in HL7 Version 2.x messaging in Master Files (OM4 segment) to characterize information about specimens that are associated with certain observations.
certificationType	Code system of concepts specifying the code for the certification type. Used in HL7 Version 2.x messaging in the IN3 segment.
processInterruptionReason	HL7-defined code system of concepts specifying the reason for the process interruption. Used in HL7 Version 2.x messaging in the DON segment.
patientResultsReleaseCategorizationScheme	HL7-defined code system of concepts specifying the scheme for the patient results release categorization. Used in HL7 Version 2.x messaging in the OBX segment.
whatSubjectFilter	HL7-defined code system of concepts which specify the kind of information that is required to satisfy a query request. The values define the type of transaction inquiry. Used in HL7 Version 2 messaging in the URD segment.
diagnosticServiceSectionId	HL7-defined code system of concepts which specify a section of a diagnostic service where the observation may be performed. Used in HL7 Version 2.x messaging in the OBR and OM4 segments.
institutionRelationshipType	Code system of concepts specifying the relationship the staff person has with the institution for whom he/she provides services. Used in HL7 Version 2 messaging in the STF segment.
sequenceCondition	HL7-defined code system of concepts used to specify the relationship between the start/end of the related service request(s) (from TQ2-3, TQ2-4 or TQ2-5) and the current service request from ORC-2, 3 or 4. Used in HL7 Version 2.x messaging in the TQ2 segment.
privacyLevel	Code system of concepts used to identify the level of privacy a patient will be afforded when assigned to this location definition. Used in HL7 Version 2.x messaging in the LCH segment.
appointmentReason	Code system of concepts used to describe the kind of appointment or the reason why an appointment has been scheduled. Used in HL7 Version 2.x messaging in the ARQ segment.
bloodProductDispenseStatus	HL7-defined code system of concepts used to specify the current status of the specified blood product as indicated by the filler or placer. For example, the first status change of a product that may trigger a Blood Product Dispense Status Message occurs when it first becomes linked to a patient and is ready to dispense. The placer system may use the Blood Product Dispense Status Message to request the transfusion service to dispense the product. When the blood product is delivered or issued to a patient, the status of the blood product would be changed to indicate that it has now been "dispensed". Used in the Blood Product Dispense Status (BPX) segment in HL7 Version 2.x messaging.
reimbursementType	Code system of concepts specifying the fee schedule reimbursement type applied to the line item. Used in HL7 Version 2.x messaging in the GP2 segment.
organDonorCodes	Code system of concepts specifying whether the patient wants to donate his/her organs and whether an organ donor card or similar documentation is on file with the healthcare organization. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments.
allergySeverity	Code system of concepts which specify the general severity of an allergy. Used in HL7 Version 2.x messaging in the AL1 segment.
medicalRoleExecutingPhysician	Code system of concepts specifying the role of the physician ("self-employed" or "employed"). Used in HL7 Version 2.x messaging in the PSL segment.
invocationEvent	HL7-defined code system of concepts which specify codes for an event precipitating/triggering a charge activity. Used in HL7 Version 2.x messaging in the CCD and BLG segments.
bedStatus	Code system of concepts which specify the state of a bed in an inpatient setting, and is used to determine if a patient may be assigned to it or not. Used in HL7 Version 2.x messaging in the DLD and PV1 segments.
delayedAcknowledgmentType	HL7-defined code system of concepts which specify a response type used in deferred processing two phase reply for delayed acknowldgement mode of the original acknowledgement mechanism defined in HL7 Version 2.x messaging and used in the MSH segment.
sideOfBody	Code system of concepts specifying the side of the body ("left" or "right"). Used in HL7 Version 2.x messaging in the PSL segment.
tqConjunctionId	HL7-defined code system of concepts specifying that a second timing specification is to follow using the repeat delimiter. Used in HL7 Version 2.x messaging in the TQ1 segment.
ambulatoryPaymentClassification	Code system of concepts specifying the derived Ambulatory Payment Classification (APC) code. Used in HL7 Version 2.x messaging in the GP2 segment.
consentBypassReason	Code system of concepts specifying the reason the subject's consent was not sought. Used in HL7 Version 2.x messaging in the CON segment.
patientLocationType	Code system of concepts used to identify the kind of location described in the location definition. Used in HL7 Version 2.x messaging in the LOC segment.
serviceRequestRelationship	HL7-defined code system of concepts used to specify an additional or alternate relationship between this service request and other service requests. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging.
productSource	HL7-defined code system of concepts used to describe the evaluation state of a product identified in an incident. Used in HL7 Version 2.x messaging in the PCR segment.
eventReason	Code system of concepts which specify the reason for an event. Used in HL7 Version 2.x messaging in the EVN segment.
messageType	HL7-defined code system of concepts which specify message types. Used in HL7 Version 2.x messaging in the MSH segment.
processInterruption	HL7-defined code system of concepts specifying whether the process was interrrupted and whether the needle had been inserted in the donor's arm prior to the interruption. Used in HL7 Version 2.x messaging in the DON segment.
observationSubtype	HL7-defined code system of concepts specifying the observation sub-type. Used in HL7 Version 2.x messaging in the OBX segment.
observationType	HL7-defined code system of concepts specifying types of observations to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order. Used in HL7 Version 2.x messaging in the OBX segment.
certificationCategory	Code system of concepts specifying the code for the certification category. Used in HL7 Version 2.x messaging in the IN3 segment.
drgStatusPatient	Code system of concepts specifying whether the length of stay is normal or respectively shorter or longer than normal. Used in HL7 Version 2.x messaging in the DRG segment.
relationship	HL7-defined code system of concepts specifying an actual personal relationship that the next of kin/associated party has to a patient. Used in HL7 Version 2.x messaging in the NK1 and IN1 segments.
bloodProductTransfusion-dispositionStatus	HL7-defined code system of concepts used to specify the current status of the specified blood product as indicated by the placer. For example, the placer may return the blood product to the transfusion service unused because an IV could not be started. The blood component may have been entered, but the line was clogged and could not be used, in which case the component must be wasted. A final status would indicate that the product has actually been "transfused." Used in the Blood Product Transfusion/Disposition (BTX) segment in HL7 Version 2.x messaging.
documentStorageStatus	HL7-defined code system of concepts used to describe the availability of a document in relation to the type of storage. Used in HL7 Version 2.x messaging in the TXA segment.
locationEquipment	Code system of concepts used to identify the equipment available in a location definition identified as a room or bed. Used in HL7 Version 2.x messaging in the LOC segment.
observationResultHandling	Code system of concepts regarding the handling of a result. For example, an order may specify that the result (e.g., an x-ray film) should be given to the patient for return to the requestor. Used in HL7 Version 2.x messaging in the OBR segment.
consentStatus	HL7-code system of concepts specifying whether the consent has been sought and granted. Used in HL7 Version 2.x messaging in the TXA and CON segments.
quantityMethod	HL7-defined code system of concepts used to specify the method by which the quantity distributed is measured. Used in HL7 Version 2.x messaging in the Product Summary Header (PSH) segment.
universalIdType	HL7-defined code system of types of UID (Universal Identifiers). Used in HL7 Version 2.x messaging HD and EI datatypes.
livingWillCodes	Code system of concepts specifying whether or not the patient has a living will and, if so, whether a copy fo the living will is on file at the healthcare facility. If the patient does not have a living will, the value of this field indicates whether the patient was provided information on living wills. Used in HL7 Version 2.x messaging in the Patient Visit - Additional Information ( PV2) and Patient Additional Demographic (PD1) segments.
formularyStatus	Code system of concepts specifying whether or not the service (pharmaceutical) is in the formulary. Used in HL7 Version 2.x messaging in the OM7 segment.
roleExecutingPhysician	Code system of concepts specifying the account role of the physician, for example, only billing for the professional part, the technical part or both. Used in HL7 Version 2.x messaging in the PSL segment.
lotControl	Code system of concepts that define whether the sterilization load for a device is built in the sub-sterile area adjacent to an Operating Room or the Central Processing Department. Used in HL7 Version 2.x messaging in the SCP segment.
processingId	HL7-defined code system of concepts which specify whether the message is part of a production, training or debugging system. Used in HL7 Version 2.x messaging in the PT datatype.
deferredResponseType	HL7-defined code system of concepts which specify which type of deferred query resonse is desired, as specified with the query parameters. Used in HL7 Version 2 messaging in the QRD segment.
advancedBeneficiaryNotice	Code system of concepts specifying the status of the patient's or the patient's representative's consent for responsibility to pay for potentially uninsured services. This element was introduced to satisfy CMS Medical Necessity requirements for outpatient services in the United States. Includes concepts such as (a) whether the associated diagnosis codes for the service are subject to medical necessity procedures, (b) whether, for this type of service, the patient has been informed that they may be responsible for payment for the service, and (c) whether the patient agrees to be billed for this service. Used in HL7 Version 2.x messaging in the ORC and FT1 segments.
controlledSubstanceSchedule	Code system of concepts specifying the class of the drug or other substance if its usage is controlled by legislation. In the USA, such legislation includes the federal Controlled Substance Act (CSA) or a State Uniform Controlled Substance Act. Other countries should create their own versions of this table. Used in HL7 Version 2.x messaging in the RXE segment. The name of the table is taken from the Pharmacy Law Digest July 1988.
jobStatus	HL7-defined code system of concepts specifying the next of kin/associated party's job status. Used in HL7 Version 2.x messaging in the Next of Kin/Associated Parties (NK1) segment.
personLocationType	Code system of concepts specifying the categorization of the person's location. Used in HL7 Version 2.x messaging datatypes that contain location identifiers such as Person Location (PL), Location with address variation (LA) and Name with date and location (NDL).
specimenCollectionMethod	HL7-defined code system of concepts specifying the specimen collection method. Used in HL7 Version 2.x messaging in the SPM segment.
sequenceResultsFlag	HL7-defined code system of concepts used to specify the sequencing relationship between the current service request and the related service request(s) specified in this TQ2 segment. Used in the Timing/Quantity Relationship (TQ2) segment in HL7 Version 2.x messaging.
specialtyType	Code system of concepts used to identify the specialty of the care professional who is supported when using this location definition. Used in HL7 Version 2.x messaging in the LDP segment.
documentCompletionStatus	HL7-defined code system of concepts used to record the state of a document in a workflow. Used in HL7 Version 2.x messaging in the TXA segment.
informInstructions	Code system of concepts specifying who (if anyone) should or should not be informed of an error. Used in the Error (ERR) segment in HL7 Version 2.x messaging.
typeOfAgreement	Code system of concepts which specify codes to further identify an insurance plan. Used in HL7 Version 2.x messaging in the IN1 segment.
phlebotomyStatus	HL7-defined code system of concepts specifying the status of the phlebotomy. Used in HL7 Version 2.x messaging in the DON segment.
intendedProcedureType	HL7-defined code system of concepts specifying the type of intended procedure. Used in HL7 Version 2.x messaging in the DON segment.
armStick	HL7-defined code system of concepts specifying the arm(s) receiving the stick. Used in HL7 Version 2.x messaging in the DON segment.
employmentStatus	HL7-defined code system of concepts which specify an employment status of a person. Used in HL7 Version 2 messaging in the GT1 segment.
cclValue	Code system of concepts specifying the clinical complexity level (CCL) value for the determined diagnosis related group (DRG) for this diagnosis. US Realm. Used in HL7 Version 2.x messaging in the DG1 segment.
documentType	Code system of concepts used to identify the kind of patient document. Used in HL7 Version 2.x messaging in the TXA segment.
errorSeverity	HL7-defined code system of concepts specifying the severity of an application error as reported during acknowledgment of messages. Knowing if something is Error, Warning or Information is intrinsic to how an application handles the content and the information flow. Used in HL7 Version 2.x messaging acknowledgment in the ERR segment.
non-subjectConsenterReason	HL7-defined code system of concepts used to specify a reason consent was granted by a person other than the subject of the consent. Used in the Consent (CON) segment in HL7 Version 2.x messaging.
relationshipModifier	HL7-defined code system of concepts used in an observation definition to describe the subject of an observation in relation to a patient. Used in HL7 Version 2.x messaging in the OM1 segment.
risks	Code system of concepts specifying any known or suspected specimen hazards, e.g., exceptionally infectious agent or blood from a hepatitis patient. Used in HL7 Version 2.x messaging in the SPM and PAC segments.
queryResponseFormat	HL7-defined code system of concepts which specify which of several types of formats for data to be returned in response to a query. Used in HL7 Version 2 messaging in the EQL segment.
versionId	HL7-defined code system of concepts which are used to identify an HL7 version in the Version 2.x family of published standards. Used in HL7 Version 2.x messaging in the VID segment.
denialOrRejectionType	Code system of concepts specifying the OCE status of the line item. Used in HL7 Version 2.x messaging in the GP2 segment.
organizationUnitType	Code system of concepts specifying the classification of the organization unit. Used in HL7 Version 2.x messaging in the ORG segment.
eventRelatedPeriod	HL7-defined code system of concepts specifying a common (periodical) activity of daily living. Used in HL7 Version 2 messaging in the RPT segment.
transfusionAdverseReaction	Code system of concepts used to specify the type of adverse reaction that the recipient of the blood product experienced. Used in the Blood Product Transfusion/Disposition (BTX) segment in HL7 Version 2.x messaging.
documentConfidentialityStatus2	HL7-defined code system of concetps used to identify the degree to which special confidentiality protection should be applied to this information. Used in HL7 Version 2.x messaging in the TXA segment.
name-addressRepresentation	HL7-defined cdoe system of concepts 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 choices regarding what it has been sent and what it is capable of displaying.
consentDisclosureLevel	HL7-defined code system of concepts specifying how much information was disclosed to the subject as part of the informed consent process. Used in HL7 Version 2.x messaging in the CON segment.
encoding	HL7-defined code system of concept identifying the type of encoding used to represent successive octets of binary data as displayable ASCII characters. These are defined by IETF; more information may be found at https://www.ietf.org/rfc/rfc1521.txt. Used in HL7 Version 2.x messaging in the ED datatypes.
specimenSourceCodes	HL7-defined code system of concepts which specify sources for speciments for clinical testing. These concepts are used in HL7 Version 2.x messaging in the OBR segment prior to version 2.7, and was replaced by the concepts in code system 2.16.840.1.133883.18.311 specimenType and code system 2.16.840.1.133883.18.312 specimenCollectionMethod as of version 2.5 and thereafter.
cycleType	Code system of concepts specifying the type of cycle that is being executed. A cycle type is a specific sterilization method used for a specific type of supply item. Used in HL7 Version 2.x messaging in the SCD segment.
phlebotomyIssue	HL7-defined code system of concepts specifying the phlebotomy issue. Used in HL7 Version 2.x messaging in the DON segment.
exclusiveTest	HL7-defined code system of concepts that define if a test should be a specific event with no other tests to be performed with this test, or not, or other special circumstances. Used in HL7 Version 2.x messaging in Master Files (OM1 segment) to characterize observations in a master of such orderables.
pcaType	HL7-defined code system of concepts specifying the type of PCA. Used in HL7 Version 2.x messaging in the RXV segment.
cumulativeDosageLimitUom	Code system of concepts specifying the unit of measure (UoM) for the cumulative dosage limit. Used in HL7 Version 2.x messaging in the CDO segment.
specimenAction	HL7-defined code system of concepts which specify actions to be taken with respect to the specimens that accompany or precede an order. The purpose of these are to further qualify (when appropriate) the general action indicated by the order control code (code system xxxx). Used in HL7 Version 2.x messaging in the OBR segment.
accessRestrictionValue	Code system of concepts specifying the information to which access is restricted. Used in HL7 Version 2.x messaging in the ARV segment. Note that these new codes as of November 2018 have been temporarily loaded into this V2 code system pending availability of the currently unavailable new tooling, at which time this code systrem will be retired and a value set of codes from the HL7 V3 ActCode code system will be used instead for this table.
cpRangeType	HL7-defined code system of concepts used to define a type of range used in composite pricing in financial transacxtions. Used in HL7 Version 2 messaging in the CP datatype.
daysOfTheWeek	HL7-defined code system of concepts used to identify the day(s) of the week when a location may be scheduled for appointments. Used in HL7 Version 2.x messaging in the UVC and LDP segments.
consentNon-disclosureReason	Code system of concepts used to specify a reason the subject did not receive full disclosure. Used in the Consent (CON) segment in HL7 Version 2.x messaging.
documentAvailabilityStatus	HL7-defined code system of concepts used to define whether a patient document is appropriate or available for use in patient care. Used in HL7 Version 2.x messaging in the TXA segment.
precision	HL7-defined code system of concepts specifying the degree of precision of the time stamp (Y = year, L = month, D = day, H = hour, M = minute, S = second). Used in HL7 Version 2 messaging in the TS datatype. Note deprecated in 2.5.1 and retained only for backward compatibility, as the datatypes and architecture for the degree of precision for timestamps was changed.
chargeTypeReason	Code system of concepts specifying the choice of, and providing the clinical rationale for, a selected charge type. Used in HL7 Version 2.x messaging in the BLG segment.
sourceOfComment	HL7-defined code system of concepts which are used to specify the source of a comment. Used in HL7 Version 2.x messaging in the NTE segment.
queryResultsLevel	HL7-defined code system of concepts which are used to control level of detail in query results. Used in HL7 Version 2 messaging in the URD segment.
completionStatus	HL7-defined code system of concepts specifying the status of the treatment administration event segment. Used in HL7 Version 2.x messaging in the Pharmacy Order Administration (RXA) segment.
nameAssemblyOrder	Code system of concepts specifying the preferred display order of the components of this person name. Used in HL7 Version 2.x messaging in the PPN, XCN and XPN segments.
eventType	HL7-defined code system of concepts specifying the type of event of the message. Used in HL7 Version 2.x messaging in the EQP segment.
referralReason	Code system of concepts used to specify the reason for which the referral will take place. Used in HL7 Version 2.x messaging in the Referral Information (RF1) segment.
formularyStatus	HL7-defined code system of concepts specifying whether or not the pharmaceutical substance is part of the local formulary. Used in HL7 Version 2.x messaging in the RXE segment.
specimenType	HL7-defined code system of concepts that describe the precise nature of an entity that may be used as the source material for an observation. This is one of two code systems that are used instead of table 0070 (code system 2.16.840.1.113883.18.28) which conflated specimen types and specimen collection methods. Used in HL7 Version 2.x messaging in the SPM segment.
specimenCondition	Code system of concepts specifying a mode or state of being that describes the nature of the specimen. Used in HL7 Version 2.x messaging in the SPM segment.
timeDelayPostChallenge	HL7-defined code system of concepts used to classify an observation definition as being a component of a challenge test. Used in HL7 Version 2.x messaging in the OM1 segment.
organization-Agency-Department	Code system of concepts used to specify the agency or department that assigned the identifier in component 1. Used in the Performing Person Time Stamp (PPN), Extended Composite ID Number and Name for Persons (XCN) and Extended Composite ID with Check Digit (CX) segments in HL7 Version 2.x messaging.
sequenceCondition	HL7-defined code system of concepts that identify whether sequence conditions or a repeating cycle of orders is defined. This is part of the Order Sequence Definition used in HL7 Version 2.x messaaging in the OSD datatype.
primaryObserverQualification	HL7-defined code system of concepts used to provide a general description of the kind of health care professional who provided the primary observation. Used in HL7 Version 2.x messaging in the PEO and PCR segments.
overrideType	Code system of concepts used to specify what type of override can be used to override the specific error identified. Used in HL7 Version 2 messaging in the ERR and OVR segments.
referralType	Code system of concepts used to identify the general category of healthcare professional desired to satisfy a referral. Used in HL7 Version 2.x messaging in the RF1 segment.
outlierType	HL7-defined code system of concepts specifying the type of outlier (i.e. period of care beyond DRG-standard stay in facility) that has been paid. Used in HL7 Vesrion 2.x messaghing in the DRG segment.
rootCause	Code system of concepts specifying the root cause. Used in HL7 Version 2.x messaging in the OBX segment.
hospitalService	Code system of concepts specifying the treatment or type of surgery the patient is scheduled to receive. Used in HL7 Version 2.x messaging in the PV1 segment.
referralPriority	Code system of concepts used to designate the urgency of a referral. Used in HL7 Version 2.x messaging in the RF1 segment.
timeSelectionCriteriaParameterClass	Code system of concepts used to describe acceptable start and end times, as well as days of the week, for appointment or resource scheduling. Used in HL7 Version 2.x messaging in the SCV and APR segments.
identityMayBeDivulged	HL7-defined code system of concepts used to define whether the primary observer has given permission for their identification information to be provided to a product manufacturer. Used in HL7 Version 2.x messaging in the PEO segment.
natureOfChallenge	HL7-defined code system of concepts used to further describe an observation definition that is characterized as a challenge observation. Used in HL7 Version 2.x messaging in the OM1 segment.
specimenAppropriateness	Code system of concepts specifying the suitability of the specimen for the particular planned use as determined by the filler. Used in HL7 Version 2.x messaging in the SPM segment.
certificationStatus	HL7-defined code system of concepts used to specify the status of the practitioner's speciality certification. Used in HL7 Version 2.x messaging in the Specialty Description (SPD) value and Practitioner Detail (PRA) segment.
actionCodes	HL7-defined code system ofstatus codes of record operation. Used in Version 2 messaging, these are used in the RXA segment in the vaccine messages, where a method of correcting vaccination information transmitted with incorrect patient identifying information is needed. As of version 2.6, this table was replaced with table 0206, whose values are defined by code system xxxx.
identityReliability	Code system of concepts specifying the reliability of patient/person identifying data transmitted via a transaction. Used in HL7 Version 2.x messaging in the PID segment.
reportPriority	HL7-defined code system of concepts which specify the priority associated with a report or update run using a query. Used in HL7 Version 2 messaging in the URD segment.
assignmentOfBenefits	Code system of concepts which indicate whether an insured person agreed to assign the insurance benefits to the healthcare provider. If so, the insurance will pay the provider directly. Used in HL7 Version 2.x messaging in the IN1 segment.
dateFormat	Code system of concepts that identify the date format for a decontamination/sterilization instance. Used in HL7 Version 2.x messaging in the SCP segment.
responseFlag	HL7-defined code system of concepts allowing the placer (sending) application to determine the amount of information to be returned from the filler. Used in HL7 Version 2.x messaging in the ORC segment.
laborCalculationType	Code system of concepts that identify the method used to calculate employee labor and measure employee productivity. Used in HL7 Version 2.x messaging in the SCP segment.
mailClaimParty	Code system of concepts which specify a party to which a claim should be mailed when claims are sent by mail. Used in HL7 Version 2.x messaging in the IN2 segment.
resultStatus	HL7-defined code system of concepts which specify a status of results for an order. Used in HL7 Version 2.x messaging in the OBR segment.
repeatPattern	Code system of concepts used to specify the interval between repeated services. Used in HL7 Version 2.x messaging in the RI datatype and RPT segment.
dispenseMethod	HL7-definde code system of concepts specifying the method by which treatment is dispensed. Used in HL7 Version 2.x messaging in the Pharmacy/Treatment Encoded order (RXE) and Pharmacy/Treatment dispense (RXD) segments.
coverageType	Code system of concepts specifying the type of insurance coverage or what types of services are covered for the purposes of a billing system. For example, a physician billing system will only want to receive insurance information for plans that cover physician/professional charges. Used in HL7 Version 2.x messaging in the Insurance (IN1) segment.
specimenRejectReason	HL7-defined code system of reasons a specimen may be rejected for a specified observation/result/analysis. Used in HL7 Version 2.x messaging in the SPM segment.
dispenseType	Code system of concepts specifying the type of dispensing event that occurred. Used in HL7 Version 2.x messaging in the RXD segment.
patientOutcome	HL7-defined code system of concepts used to describe the overall state of a patient as a result of patient care. Used in HL7 Version 2.x messaging in the PEO segment.
calendarAlignment	HL7-defined code system of concepts used to specify an alignment of the repetition to a calendar (e.g., to distinguish every 30 days from "the 5th of every month"). Used in HL7 Version 2 messaging in the RPT segment.
durationCategories	Code system of concepts used to classify an observation definition as intended to measure a patient's state at a point in time. Used in HL7 Version 2.x messaging in the OM1 segment.
chargeOnIndicator	Code system of concepts used to define the event upon which a charge should be generated. Used in HL7 Version 2.x messaging in the PRC segment.
referralDisposition	Code system of concepts used to identify the expected response from the healthcare professional receiving a referral. Used in HL7 Version 2.x messaging in the RF1 segment.
drgDiagnosisDeterminationStatus	HL7-defined cCode system of concepts specifying the status of a diagnosis for a diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DG1 segment.
natureOfAbnormalTesting	HL7-defined code system of concepts specifying the nature of an abnormal test. Used in HL7 Version 2.x messaging in the OBX segment.
relevantClincialInformation	Code system of concepts specifying additional clinical information about the patient or specimen to report the supporting and/or suspected diagnosis and clinical findings on requests for interpreted diagnostic studies. Used in HL7 Version 2.x messaging in the OBR segment.
bolusType	HL7-defined code system of concepts specifying the type of bolus. Used in HL7 Version 2.x messaging in the RXV segment.
referralStatus	Code system of concepts used to define the state of a referral. Used in HL7 Version 2.x messaging in the RF1 segment.
override	Code system of concepts used to define whether a Charge Description Master description may be overridden or if it must be overridden. Used in HL7 Version 2.x messaging in the CDM and PRC segments.
expandedYes-NoIndicator	HL7-defined code system of concepts used to specify an expansion on the original Yes/No indicator table by including "flavors of null". It is intended to be applied to fields where the response is not limited to "yes" or "no". Used in numerous locations in HL7 Version 2.x messaging.
kindOfQuantity	HL7 published code system of concepts that describe categories of an underlying kind of property represented by an observation. These are intended to distinguish concentrations from total amounts, molar concentrations from mass concentrations, partial pressures from colors, and so forth. These are discussed more fully in the LOINC Users’ Manual. These defined categories are derived from the approach described in 1995 edition of the IUPAC Silver Book. These distinctions are used in IUPAC and LOINC standard codes. Needs review by OO and HTA to determined if this is a value set built on LOINC part codes or some other external vocabulary.
eventConsequence	HL7-defined code system of concepts used to describe the impact of an event on a patient. Used in HL7 Version 2.x messaging in the PEO segment.
extendedPriorityCodes	Code system of concepts describing the urgency of a request carried in an order. Used in HL7 Version 2.x messaging in timing/quantity; in older versions of the Standard was used in the TQ datatype, but in later versions it is used in the TQ1 segment (which replaced the TQ datatype which has been withdrawn).
specimenQuality	Code system of concepts specifying the degree or grade of excellence of the specimen at receipt. Used in HL7 Version 2.x messaging in the SPM segment.
disabilityInformationRelationship	Code system of concepts used to specify to which person the disability information relates in the message. For example, if the value is PT, the disability information relates to the patient. Used in HL7 Version 2.x messaging in the Disability (DB1) segment.
chargeType	HL7-defined code system of concepts which specify someone or something other than the patient to be billed for a service. Used in HL7 Version 2.x messaging in the BLG segment.
quantityLimitedRequest	HL7-defined code system of concepts which specify the maximum length of a query response that can be accepted by a requesting system, and are expressed as units of mesaure of query response objects. Used in HL7 Version 2.x messaging in the RCP segment.
marketingBasis	HL7-defined code system of concepts used to specify the basis for marketing approval. Used in HL7 Version 2.x messaging in the Product Detail Country (PDC) segment.
locationCharacteristic	Code system of concepts specifying an identifier code to show which characteristic is being communicated with the segment. Used in HL7 Version 2.x messaging in the Location Characteristic (LCH) segment.
locationServiceType	Code system of concepts specifying the types of services provided by the location. Used in HL7 Version 2.x messaging in the LOC segment.
bodySiteModifier	HL7-defined code system of concepts specifying the modifier for the body site. Used in HL7 Version 2.x messaging in the RXR segment.
fillerStatus	Code system of concepts used to describe an appointment status from the perspective of the entity assigned to fulfill the appointment. Used in HL7 Version 2.x messaging in the SCH segment.
relatednessAssessment	HL7-defined code system of concepts used to provide an estimate of whether an issue with a product was the cause of an event. Used in HL7 Version 2.x messaging in the PCR segment.
certificateStatus	Code system of concepts specifying the status of the certificate held by the health professional. Used in HL7 Version 2 messaging in the CER segment.
problem-goalAction	HL7-defined code system of concepts used in Patient Care for the intent of a problem or goal. Used in HL7 Version 2.x messaging in the GOL, ROL, PRB and PTH segments.
grouperStatus	Code system of concepts specifying the status of a grouper in general. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
diagnosisType	Code system of concepts specifying a type of diagnosis being sent. Used in HL7 Version 2.x messaging in the DG1 segment..
confidentiality	HL7-defined code system of concepts specifying the confidentiality for the shipment. Used in HL7 Version 2.x messaging in the SHP segment.
observationResultStatusCodesInterpretation	HL7-defined code system of concepts which specify observation result status. These codes reflect the current completion status of the results for one Observation Identifier. Used in HL7 Version 2.x messaging in the OBX segment.
queryPriority	HL7-defined code system of concepts which specify a time frame in which a querry response is expected. Used in HL7 Verson 2.x messaging in the RCP segment.
participation	HL7-defined code system of concepts that represent functional involvement of a caregiver or member of a care team with an activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Used in HL7 Version 2.x messaging in the PRT segment.
actpriority	HL7-defined code system of concepts specifying the priority for the shipment. Used in HL7 Version 2.x messaging in the SHP segment.
providerRole	Code system of concepts used to define the relationship between a referral recipient and a patient or between a referral initiator and a patient. Used in HL7 Version 2.x messaging in the PRD segment.
actionTakenInResponseToTheEvent	HL7-defined code system of concepts used to define the action taken as a result of an event related to a product issue. Used in HL7 Version 2.x messaging in the PCR segment.
computationType	HL7-defined code system of concepts used to specify if the change is computed as a percent change or as an absolute change. Used in the Delta (DLT) segment in HL7 Version 2.x messaging.
allowSubstitution	Code system of concepts used to indicate whether the appointment resource may be substituted for another by the entity assigned to fulfill the appointment. Used in HL7 Version 2.x messaging in the AIS and AIG segments.
pharmacyOrderTypes	HL7-defined code system of concepts specifying the general category of pharmacy order which may be used to determine the processing path the order will take. Used in HL7 Version 2.x messaging in the RXO, RXE, RXD, RXG and RXA segments.
specimenChildRole	HL7-defined code system of concepts specifying for child specimens the relationship between this specimen and the parent specimen. Used in HL7 Version 2.x messaging in the SPM segment.
locationRelationship	Code system of concepts specifying an identifier code to show which relationship is being communicated with the segment. Used in HL7 Version 2.x messaging in the Location Relationship (LRL) segment.
providerRole	Code system of concepts specifying the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Used in HL7 Version 2.x messaging in the ROL segment.
overallClaimDisposition	Code system of concepts specifying the final status of the claim. Used in HL7 Version 2.x messaging in the GP1 segment.
facilityType	HL7-defined code system of concepts used to specify the type of facility. Used in HL7 Version 2.x messaging in the Facility (FAC) segment.
deviceStatus	Code system of concepts that communicate the state of a device. Used in HL7 Version 2.x messaging in the SCD segment.
allergenType	Code system of concepts speciying a classification of general allergy categories (drug, food, pollen, etc.). Used in HL7 Version 2.x messaging in the AL1 segment.
procedurePractitionerIdentifierCodeType	HL7-defined table of concepts which specify the different types of practitioners associated with this procedure. This set of codes is known to be incomplete. Note that as of v2.6, this table and the field(s) it was used in was replaced by table 443 used in the ROL segment. Used in Version 2.x messaging in the PR1 segment, but was discontinued as of 2.6; usage replaced with code system 2.16.840.1.113883.18.283 providerRole.
loadStatus	Code system of concepts used to define the status of the information provided in a device sterilization or decontamination cycle. Used in HL7 Version 2.x messaging in the SDD segment.
orderControlCodes	HL7-defined code system of concepts which are used to determine the function of the order segment. Depending on the message, the action specified by one of these control codes may refer to an order or an individual service. Used in Version 2.x messaging of orders in the ORC segment.
deviceType	Code system of concepts that idenfity the kind of device as defined by the manufacturer. Used in HL7 Version 2.x messaging in the SCP segment.
contactRole2	Code system of concepts which specify a relationship role that the next of kin/associated parties plays with regard to the patient. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral. Used in HL7 Version 2 messaging in the NK1 and CTD segments after 2.5, when it replace 2.16.840.1.113883.18.57.
packagingStatus	Code system of concepts specifying the packaging status of the service. Used in HL7 Version 2.x messaging in the GP2 segment.
immunizationRegistryStatus	Code system of concepts specifying the immunization registry status of the patient. Used in HL7 Version 2.x messaging in the PD1 segment.
orderType	HL7-defined code system of concepts specifying whether the order is to be executed in an inpatient setting or an outpatient setting. Used in HL7 Version 2.x messaging in the ORC segment.
consentType	Code system of concepts specifying to what the subject is consenting, i.e. what type of service, surgical procedure, information access/release or other event. Used in HL7 Version 2.x messaging in the TXA and CON segments.
signatureType	Code system of concepts that indicate how a patient/subscriber authorization signature is obtained and how it is being retained by a provider. Used in HL7 Version 2.x messaging in the IN1 segment.
indirectExposureMechanism	HL7-defined code system of concepts used to identify the mechanism of product transmission when the product has not been directly applied to the patient. Used in HL7 Version 2.x messaging in the PCR segment.
statusOfEvaluation	HL7-defined code system of concepts that describes the status of product evaluation. Used in HL7 Version 2.x messaging in the PCR segment.
mimeBase64EncodingCharacters	HL7-defined code system of concepts specifying the characters used in the MIME Base 64 encoding mechanism. These are for reference only, as they are not carried as explicit code values in any HL7 coded field. This table was published only in releases 2.3, 2.3.1, and 2.4 of the Standard, and was removed thereafter.
referralCategory	Code system of concepts used to describe the patient care setting where a referral should take place. Used in HL7 Version 2.x messaging in the RF1 segment.
securityCheckScheme	HL7-defined code system of concepts specifying the scheme for the security check. Used in HL7 Version 2.x messaging in the CX datatypes and PPN and XCN segments.
re-admissionIndicator	Code system of concepts which are used to specify that a patient is being re admitted to a healthcare facilityin from which they were discharged, and indicates the circumstances around such re-admission. Used in HL7 Version 2.x messagine in the PV1 segment.
collectionEvent	HL7-defined code system of concepts specifying the limit for the collection event or process step. Used in HL7 Version 2.x messaging in the OMC segment.
communicationLocation	HL7-defined code system of concepts specifying the communication location. Used in HL7 Version 2.x messaging in the OMC segment.
shipmentStatus	HL7-defined code system of concepts specifying the status of the shipment. Used in HL7 Version 2.x messaging in the SHP segment.
subtypeOfReferencedData	Code system of a subset of the media subtypes of binary data that are encoded in an ascii structure or stream. Used in Version 2 messaging ED and RP datatypes, but only in standard 2.5.1 and earlier; after that, it was recommended that the IANA media types be used instead of this short list of HL7-defined codes. More information on the standard media types and subtypes may be found at http://www.iana.org/assignments/media-types/media-types.xhtml.
messageWaitingPriority	HL7-defined code system of concepts which specify the disposition of the patient at time of discharge (i.e., discharged to home, expired, etc.). Used in HL7 Version 2.x messaging in the MSA segment.
clergyNotificationType	Code system of concepts specifying whether the clergy should be notified. Used in HL7 Version 2 messaging in the PV2 segment.
causalityObservations	HL7-defined code system of concepts used to record event observations regarding what may have caused a product related event. Used in HL7 Version 2.x messaging in the PCR segment.
bloodProductProcessingRequirements	Code system of concepts used to specify additional information about the blood component class associated with the Universal Service ID. The placer of the order can specify any required processing of the blood product that must be completed prior to transfusion to the intended recipient. Used in the Blood Product Order (BPO) segment in HL7 Version 2.x messaging.
consentMode	HL7-defined code system of concepts specifying the method in which a subject provides consent. Used in HL7 Version 2.x messaging in the TXA and CON segments.
authorizationMode	HL7-defined code system of concepts of forms of authorization a recorder may receive from the responsible practitioner to create or change an order. Used in HL7 Version 2.x messaging in the ORC segment.
sourceType	HL7-defined code system of concepts used to specify the type of facility. Used in HL7 Version 2.x messaging in the Facility (FAC) segment.
dataTypes	HL7-defined code system of concepts specifying the format of the observation value in the Observation Result (OBX). Used in HL7 Version 2.x messaging in the OBX, OM1, OM3 and OMC segments.
visitIndicator	Code system of concepts specifying the level on which data are being sent. It is the indicator used to send data at two levels, visit and account. HL7 recommends sending an "A" or no value when the data in the message are at the account level or "V" to indicate that the data sent in the message are at the visit level. Used in HL7 Version 2.x messaging in the Patient Visit (PV1) segment.
paymentAdjustmentInformation	Code system of concepts specifying any payment adjustment due to drugs or medical devices. Used in HL7 Version 2.x messaging in the GP2 segment.
supplyRisk	Code system of concepts specifying any known or suspected hazard associated with this material item. Used in HL7 Version 2.x messaging in the ITM segment.
visitUserCodes	Code system of concepts which specify categories of a patient's visit with respect to an individual institution's needs, and is expected to be different on a site-specific basis. Used in HL7 Version 2.x messaging in the PV2 segment.
transportationMode	HL7-defined code system of concepts which specify how (or whether) to transport a patient, when applicable, for an ordered service. Used in HL7 Version 2.x messaging in the OBR segment.
reorderTheory	Code system of concepts that identify the calculation method used to determine the resupply schedule. Used in HL7 Version 2.x messaging in the IVT segment.
itemStatus	Code system of concepts that identify the state of an inventory item within the context of an inventory location. Used in HL7 Version 2.x messaging in the IVT segment.
whichDate-timeStatusQualifier	HL7-defined code system of concepts that specify the status type of objects selected in a date range. Used in HL7 Vesion 2 messaging in the QRF segment.
masterfileActionCode	HL7-defined code system of concepts specifying an action for a master file record. Used in HL7 Version 2.x messaging in the MFE segment.
riskManagementIncident	HL7-defined code system of concepts which specify a type of incident that occurs during a patient’s stay. Used in HL7 Version 2 messaging in the RMI segment.
primaryKeyValueType	HL7-defined code system of concepts used to specify the type for the master file record identifier. Used in HL7 Version 2.x messaging in the Master File Entry (MFE) segment.
precaution	Code system of concepts specifying non-clincal precautions that need to be taken with the patient. Used in HL7 Version 2.x messaging in the PV2 segment.
specimenRole	HL7-defined code system of concepts that identify the role of a sample. Used in HL7 Version 2.x messaging in the Specimen (SPM) and Observation Request (OBR) segments.
codingSystem	HL7-defined code system of concepts specifying the coding system. This table is maintained outside of the published Version 2 standards, and may be found at http://www.hl7.org/Special/committees/vocab/table_0396/index.cfm. Used in HL7 Version 2.x messaging in the CWE segment.
invoiceControl	Code system of concepts used to specify what action is being performed by this message. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging.
reportSource	HL7-defined code system of concepts used to identify where a report sender learned about an event. Used in HL7 Version 2.x messaging in the PES segment.
jurisdictionalBreadth	Code system of concepts specifying the breadth/extent of the jurisdiction where the qualification is valid. Used in HL7 Version 2 messaging in the CER segment.
relationalOperator	HL7-defined code system of concepts used to define the relationship between HL7 segment field names identified in a query construct. Used in HL7 Version 2.x messaging in the QSC segment.
rulingAct	Code system of concepts specifying an act containing a rule that the item is legally required to be included in notification reporting. Used in HL7 Version 2.x messaging in the ITM segment.
itemType	Code system of concepts specifying a classification of material items into like groups as defined and utilized within an operating room setting for charting procedures. Used in HL7 Version 2.x messaging in the ITM segment.
queryResponseStatus	HL7-defined code system of concepts defining precise response status concepts in support of HL7 Version 2 query messaging. It is commonly used to indicate no data is found that matches the query parameters, but no error. Used in HL7 Version 2.x messaging in the QAK segment.
livingArrangement	Code system of concepts characterizing the situation that patient-associated parties live in at their residential address. Used in HL7 Version 2.x messaging in the NK1 and PD1 segments.
reportTiming	HL7-defined code system of concepts used to identify the time span of a report or the reason for a report sent to a regulatory agency. Used in HL7 Version 2.x messaging in the PES segment.
sequencing	HL7-defined code system of concepts identifying how the field or parameter will be sorted and, if sorted, whether the sort will be case sensitive (the default) or not. Used in HL7 Version 2.x messaging in the Sort Order (SRT) value.
substanceStatus	HL7-defined code system of concepts identifying the status of the inventoried item. The status indicates the current status of the substance. Used in HL7 Version 2.x messaging in the Inventory Detail (INV) segment.
remoteControlCommand	Code system of concepts that identify the comment the component is to initiate. Used in the Equipment Command (ECD) and Interaction Status Detail (ISD) segments in HL7 Version 2.x messaging.
messageStructure	HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment.
admissionLevelOfCare	Code system of concepts specifying the acuity level assigned to the patient at the time of admission. Used in HL7 Version 2.x messaging in the PV2 segment.
bloodProduct	HL7-defined code system of concepts which specify a type of blood product. Used in HL7 Version 2 messaging in the BLC segment.
mfnRecord-levelErrorReturn	Code system of concepts specifying the status of the requested update. Site-defined table, specific to each master file being updated via this transaction. Used in HL7 Version 2.x messaging in the MFA segment.
protection	Code system of concepts specifying that an address needs to be treated with special care or sensitivity. Used in HL7 Version 2.x messaging in the XAD and XTN segments.
whichDate-timeQualifier	HL7-defined code system of concepts that specify a type of date referred to in query specifications. Used in HL7 Version 2 messaging in the QRF segment.
militaryStatus	Code system of concepts which specify the military status of the patient. This field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the PD1 segment.
militaryService	Code system of concepts which specify the military branch. This field is defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the PD1 segment.
processingPriority	HL7-defined code system of concepts which specify one or more available priorities for performing the observation or test. Used in HL7 Version 2.x messaging in the OM1 segment.
active-inactive	HL7-defined code system of concepts specifying whether a person is currently a valid staff member. Used in HL7 Version 2.x messaging in the STF segment.
arrivalMode	Code system of concepts specifying how the patient was brought to the healthcare facility. Used in HL7 Version 2.x messaging in the PV2 segment.
alternateCharacterSetHandlingScheme	HL7-defined code system of concept that specify the scheme used when any alternative character sets are specified in the second or later iterations of MSH-18 Character Set, and if any special handling scheme is needed. Used in HL7 Version 2.x messaging in the MSH segment.
gestationCategory	HL7-defined code system of concepts which specify the status of a birth in relation to the gestation. Used in HL7 Version 2 messaging in the ABS segment.
procedurePriority	HL7-defined code system of concepts which specify the significance or priority of a procedure code. Used in HL7 Version 2 messaging in the PR1 segment. Note that this is a post-coordinated code system, where additional ordinal priorities are created by incrementing the numericinteger code value as needed. Only the first 2 ordinal values are predefined in the code system.
modifyIndicator	HL7-defined code system of concepts identifying whether the subscription is new or is being modified. Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment.
containerCondition	HL7-defined code system of concepts used to specify at each receipt the status of the container in which the specimen is shipped in chain of custody cases where specimens are moved from lab to lab. If the container is compromised in any way (seal broken, container cracked or leaking, etc.), then this status needs to be recorded for legal reasons. Used in the Specimen (SPM), Shipment (SHP) and Shipment Package (PAC) segments in HL7 Version 2.x messaging.
eventReportedTo	HL7-defined code system of concepts used to identify the type of entity to which the even has been reported. Used in HL7 Version 2.x messaging in the PES segment.
bodyParts	HL7-defined code system of concepts specifying the part of the body. Used in HL7 Version 2 messaging in the RXR segment.
siteAdministered	HL7-defined code system of concepts used for medication administration sites. Used only in HL7 releases 2.1 and 2.2; as of 2.3 the model for this was changed and the field using this code system was removed from the Standard.
acknowledgmentCodes	HL7-defined code system of concepts specifying acknowledgment codes. For details of usage, see message processing rules in the published Standard. Used in HL7 Version 2.x messaging in the MSA segment.
orderControlCodeReason	HL7-defined code system of concepts that describe reasons for the chosen order control codes. Used in HL7 Version 2 messaging in the ORC segment.
v2CS-relationshipType	HL7-defined code system of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4) and the Target Information Instance (REL-5).
approvingRegulatoryAgency	Code system of concepts specifying the regulatory agency by which the item has been approved, such as the FDA or AMA. Used in HL7 Version 2.x messaging in the ITM segment.
ambulatoryStatus	Code system of concepts specifying permanent or transient handicapped conditions of a person. Used in HL7 Version 2.x messaging in the PV1 segment.
eventQualification	HL7-defined code system of concepts used to qualify an event related to a product experience. Used in HL7 Version 2.x messaging in the PEO segment.
livingDependency2	HL7-defined code system of concepts that identify specific living conditions (e.g., spouse dependent on patient, walk-up) that are relevant to an evaluation of the patient’s healthcare needs. This information can be used for discharge planning. Examples might include Spouse Dependent, Medical Supervision Required, Small Children Dependent. Used in Version 2.s messaging in the NK1 segment.
responseModality	HL7-defined code system of concepts identifying the timing and grouping of the response message(s). Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment.
newbornType	HL7-defined code system of concepts which specify whether the baby was born in or out of a specified facility. Used in HL7 Version 2 messaging in the ABS segment.
recreationalDrugType	Code system of concepts specifying what recreational drugs the patient uses. Used in HL7 Version 2.x messaging in the PV2 segment.
messageErrorCondition	HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging.
reportingPriority	HL7-defined code system of concepts which specify the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority. Used in HL7 Version 2.x messaging in the OM1 segment.
accept-applicationAcknowledgmentConditions	HL7-defined code system of concepts which identify conditions under which accept acknowledgments are required to be returned in response to a message, and required for enhanced acknowledgment mode. Used in HL7 Versions 2 messaging in the MSH segment.
responseLevel	HL7-defined code system of concepts specifying application response levels defined for a given Master File Message at the MFE segment level, and used for MFN-Master File Notification message. Specifies additional detail (beyond MSH-15 - Accept Acknowledgment Type and MSH-16 - Application Acknowledgment Type) for application-level acknowledgment paradigms for Master Files transactions. Used in HL7 Version 2.x messaging in the MFI segment.
roomType	Code system of concepts which specify the room type. Used in HL7 Version 2.x messaging in the RMC segment.
applicationChangeType	HL7-defined code system of concepts which specify the type of change being requested (if NMR query) or announced (if NMD unsolicited update) during application status changes. It is assumed that a "new" version starts up with no loss or duplication of data as the "old" one is shutting down (if possible). Used in HL7 Version 2 Messaging in the NSC segment.
cweStatuses	HL7-defined code system of comcepts that represent an exception identifier code; that is, a code that is not defined in the value set (either model or site-extended). These are occationsally referred to a 'flavors of null' although this set of concepts is specific to the CWE datatype used in HL7 Version 2.x messaging, and the codes may be used in the 'identifier' component of the 'triplets' in that datatype.
advanceDirective	Code system of concepts specifying the patient's instructions to the healthcare facility. Used in HL7 Version 2.x messaging in the PV2 and PD1 segments.
severityOfIllness	HL7-defined code system of concepts which specify the ranking of a patient’s illness. Used in HL7 Version 2 messaging in the ABS segment.
substanceType	HL7-defined code system of concepts identifying the type of substance. Used in HL7 Version 2.x messaging in the Inventory Detail (INV) segment.
adjustmentAction	Code system of concepts used to specify the action requested of the party that receives an adjustment. Used in the Adjustment (ADJ) segment in HL7 Version 2.x messaging.
invoiceType	Code system of concepts used to specify the type of invoice. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging.
drgStatusRespirationMinutes	Code system of concepts specifying the status of the use of the respiration minutes information for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
onlineVerificationResult	Code values used to indicate the result of an online verification of insurance data.
onlineVerificationResultErrorCodes	Code values representing a type of error from a failed operation to perform online verification of insurance data.
drgStatusFinancialCalculation	Code system of concepts specifying the status of the diagnosis related group (DRG) calculation regarding the financial aspects. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
invoiceReason	Code system of concepts used to specify the reason for this invoice. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging.
insuranceCompanyContactReason	Code system of concepts used to describe why an insurance company has been contacted. Used in HL7 Version 2.x messaging in the IN2 segment.
inactiveReason	Code system of concepts specifying the reason the staff member is inactive. Used in HL7 Version 2 messaging in the STF segment.
segmentGroup	HL7-defined code system of concepts specifying the optional segment groups which are to be included in the response. This is a repeating field, to accommodate inclusion of multiple segment groups. The default for this field, not present, means that all relevant groups are included. Used in HL7 Version 2.x messaging in the Response Control Parameter (RCP) segment.
patientCondition	Code system of concepts specifying the patient's current medical condition for the purpose of communicating to non-medical outside parties, e.g. family, employer, religious minister, media, etc. Used in HL7 Version 2.x messaging in the PV2 segment.
providerBilling	HL7-defined code system of concepts specifying how provider services are billed. Used in HL7 Version 2.x messaging in the PRA segment.
amountClass	Code system of concepts specifying the amount quantity class. Used in HL7 Version 2.x messaging in the PTA segment.
eligibilitySource	Code system of concepts which specify the source of information about the insured's eligibility for benefits. Used in HL7 Version 2.x messaging in the IN2 segment.
certificationPatientType	Code system of concepts which specify the category or type of patient for which this certification is requested. Used in HL7 Version 2.x messaging in the ICD segment.
file-levelEvent	HL7-defined code system of concepts specifying file-level events for master files. Used in HL7 Version 2 messaging in the MFI segment.
amountType	Code system of concepts which specify amount quantity type. Used in HL7 Version 2.x messaging in the RMC segment.
itemImportance	Code system of concepts that denote a level or importance of an inventory item within the context of an inventory location. Used in HL7 Version 2.x messaging in the IVT segment.
preferredMethodOfContact	HL7-defined code system of concepts specifying which of a group of multiple phone numbers is the preferred method of contact for this person. Used in HL7 Version 2.x messaging in the STF, PRD, and CTD segments.
typeOfReferencedData	HL7-defined code system of concepts declaring the general type of media data that is encoded. Used in v2.5.1 interfaces and earlier, and replaced with the full set of IANA media types as a standard coding system for this after HL7 version 2.6 (see value set 2.16.840.1.113883.21.425 hl7VS-mimeTypes for HL7 table 0834 built on MIME types). More information may be found at http://www.iana.org/assignments/media-types/media-types.xhtml
patientsRelationshipToInsured	Code system of concepts used to specify the relationship of the patient to the insured, as defined by CMS or other regulatory agencies. Used in HL7 Version 2.x messaging in the Insurance Additional Information (IN2) segment.
triageType	HL7-defined code system of concepts which specify a patient’s prioritization within the context of a transmitted abstract. Used in HL7 Version 2 messaging in the ABS segment.
sensitivityToCausativeAgent	Code system of concepts specifying the reason the patient should not be exposed to a substance. Used in HL7 Version 2.x messaging in the IAM segment.
commandResponse	Code system of concepts identifying the response of the previously issued command. Used in HL7 Version 2.x messaging in the Equipment Command Response (ECR) and Interaction Status Detail (ISD) segments.
matchAlgorithms	Code system of concepts identifying the name or identity of the specific search algorithm to which the RCP-5 Search Confidence Threshold and the QRI-1 Candidate Confidence refer. Used in HL7 Version 2.x messaging in the Query Response Instance (QRI) segment.
procedureFunctionalType	Code system of concepts used to classify a procedure. Used in HL7 Version 2.x messaging in the PR1 segment.
benefitGroup	Code system of concepts used to specify the benefit group. Used in the Invoice (IVC) segment in HL7 Version 2.x messaging.
transportArranged	HL7-defined code system of concepts defining whether patient transportation preparations are in place. Used in HL7 Version 2.x messaging in the OBR segment.
priority	HL7-defined code system of concepts specifying the allowed priorities for obtaining the specimen. Used in HL7 Version 2.x messaging in the OM4 segment.
drgstatusWeightAtBirth	Code system of concepts specifying the status of the use of the weight at birth for diagnosis related group (DRG) determination. US Realm. Used in HL7 Version 2.x messaging in the DRG segment.
route	HL7-defined code system of concepts that indicate a means of administrating a medication dose. Used in HL7 Version 2 messaging in the RX1 segment (which was withdrawn after version 2.2). As of HL7 version 2.3, it was replaced by 2.16.840.1.113883.18.80 routeOfAdministration and 2.16.840.1.113883.18.83 administrationMethod. Used in the RX1 segment.
escortRequired	HL7-defined code system of concepts defining whether patient transportation preparations are in place. Used in HL7 Version 2.x messaging in the OBR segment.
studentStatus	Code system of concepts used to designate whether a guarantor is a full or part time student. Used in HL7 Version 2.x messaging in the GT1, NK1 and PD1 segments.
payeeType	Code system of concepts used to specify the type of payee (e.g., organization, person). Used in the Payee Information (PYE) segment in HL7 Version 2.x messaging.
matchReason	Code system of concepts identifying what search components (e.g., name, birthdate, social security number) of the record returned matched the original query where the responding system does not assign numeric match weights or confidence levels. It provides a method for passing a descriptive indication of the reason a particular record was found. Used in HL7 Version 2.x messaging in the Query Response Instance (QRI) segment.
alertDevice	Code system of concepts specifying any type of allergy alert device the patient may be carrying or wearing. Used in HL7 Version 2.x messaging in the IAM segment.
caseCategory	HL7-defined code system of concepts which specify reasons that a non-urgent patient presents to the Emergency Room for treatment instead of a clinic or physician office. Used in HL7 Version 2 messaging in the ABS segment.
addressType	HL7-defined code system of concepts specifying types or kinds of addresses. Used in HL7 Version 2.x messaging in the XAD segment.
sterilizationType	Code system of concepts specifying the type of sterilization used for sterilizing the inventory supply item in the ITM segment. Used in HL7 Version 2.x messaging in the STZ segment.
policyType	Code system of concepts which specify the policy type. Used in HL7 Version 2.x messaging in the PTA segment.
NullFlavor	A collection of codes specifying why a valid value is not present.
TableRules	These values are defined within the XHTML 4.0 Table Model
ActRelationshipCheckpoint
Race	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.
ActReason	A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. *Examples:* Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".
ActPriority	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.
ContextControl	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).
EntityRisk	Kinds of risks associated with the handling of the material..
GTSAbbreviation	*Open Issue:* It appears that the printnames are suboptimal and should be improved for many of the existing codes.
DataOperation
HL7VoteResolution	**Description:** Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).
PaymentTerms	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.
EncounterAdmissionSource
HL7PublishingSection	**Description:** Codes for HL7 publishing sections (major business categories)
EntityClass	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.
LocalRemoteControlState
HL7 Coded Concept Status	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
HL7StandardVersionCode	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.
ActUncertainty	*OpenIssue:* Missing Description
AcknowledgementCondition	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
EquipmentAlertLevel
HL7CommitteeIDInRIM	Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
ManagedParticipationStatus	Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine.
AddressUse	Codes that provide guidance around the circumstances in which a given address should be used.
MessageCondition	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.This isn't referenced in the RIM and is a copy of old v2 codes. It's superseded by AcknowledgementDetailCode
OrganizationNameType	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. All of these are maintained under EntityNameType. This was created in error and should never be used.
LanguageAbilityProficiency	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.
IdentifierReliability	Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.
CodeSystem	Code systems used in HL7 standards.
Dentition
ActRelationshipSubset	<ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>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.</ns1:p>
EntityNamePartTypeR2	**Description:**Indicates whether the name part is a given name, family name, prefix, suffix, etc.
MDFAttributeType	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
TribalEntityUS	INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS
CompressionAlgorithm
MdfHmdRowType	The row type codes for the tabular representation of a Hierarchical Message Description. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
AmericanIndianAlaskaNativeLanguages	American Indian and Alaska Native languages currently being used in the United States.
Possible Concept Code Relationships	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
LocalMarkupIgnore	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"
TableCellHorizontalAlign	These values are defined within the XHTML 4.0 Table Model
ObservationInterpretation	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.
EncounterReferralSource	This domain is defined in UB92 and applies to US realm only **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. We've deprecated all of the codes.
ActExposureLevelCode	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.
EntityDeterminer	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.
Substance Admin Substitution	Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.
Trigger Event ID	**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.
ActSite	An anatomical location on an organism which can be the focus of an act.
HL7V3Conformance	**Description:** Identifies allowed codes for HL7aTMs v3 conformance property.
RoleStatus	Codes representing the defined possible states of an Role, as defined by the Role class state machine.
QueryParameterValue	The domain of coded values used as parameters within QueryByParameter queries.
IdentifierScope	**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.
EntityStatus	Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.
Ethnicity	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.
RoleLinkType
ResponseLevel	Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include
Orderable Drug Form	*OpenIssue:* Missing description.
QueryStatusCode	A code specifying the state of the Query.
HL7PublishingSubSection	**Description:** Codes for HL7 publishing sub-sections (business sub-categories)
EntityNamePartType
ActRelationshipSplit
ParticipationFunction	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).
EntityNamePartQualifier	*OpenIssue:* Needs description
MdfRmimRowType	The row types for the tabular representation of an R-MIM. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
Universal Resource Locator Scheme	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.
HL7ConformanceInclusion	These concepts represent theconformance requirments defined for including or valuing an element of an HL7 message. The concepts apply equally to conformance profiles defined for Version 2.x messgaes as defined by the Conformance SIG, and to the conformance columns for Version 3 messages as specified in the HMD. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
TableCellScope	These values are defined within the XHTML 4.0 Table Model
DeviceAlertLevel	Domain values for the Device.Alert\_levelCode
ConceptGenerality	Indicates whether the concept that is the target should be interpreted as itself, or whether it should be expanded to include its child concepts, or both when it is included in the source domain/valueset. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
EntityNameUse
GenderStatus
ActRelationshipType	The source is an excerpt from the target.
CommunicationFunctionType	Describes the type of communication function that the associated entity plays in the associated transmission.
ObservationValue	This code system covers all concepts of HL7-defined values for the Observation value element, when it has a coded datatype.
EmployeeJobClass
ActStatus	Codes representing the defined possible states of an Act, as defined by the Act class state machine.
QueryRequestLimit	**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.
ActInvoiceElementModifier	Processing consideration and clarification codes.
RoleLinkStatus	**Description:**Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.
HL7UpdateMode	The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.
TelecommunicationCapabilities	**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.
ProcessingID	Codes used to specify whether a message is part of a production, training, or debugging system.
AcknowledgementDetailCode	*OpenIssue:*Missing description.
HL7ApprovalStatus	**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.
SetOperator
QueryResponse	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.
ModifyIndicator
ContentProcessingMode	**Description:**Identifies the order in which content should be processed.
Religious Affiliation	Assigment of spiritual faith affiliation
EditStatus	The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database.
ObservationMethod	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.
ResponseModality	Defines the timing and grouping of the response instances. *OpenIssue:* Description copied from Concept Domain of same name. Must be verified.
HL7DefinedRoseProperty	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.
ParameterizedDataType	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
HL7 Value Set and Coded Concept Property Codes	**Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
ContainerSeparator	A material in a blood collection container that facilites the separation of of blood cells from serum or plasma
TableCellVerticalAlign	These values are defined within the XHTML 4.0 Table Model
LivingArrangement	A code depicting the living arrangements of a person
ObservationCategory	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.
AcknowledgementDetailType	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'
ActCode	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.
ExposureMode	Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.
Education Level	Years of education that a person has completed
ActUSPrivacyLaw	A jurisdictional mandate in the US relating to privacy. ***Deprecation Comment:*** Content moved to ActCode under \_ActPrivacyLaw; use that instead.
HL7 ITS Version Code	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.
Confidentiality	A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality".
PostalAddressUse	*Deprecation Comment:* This code system was deprecated as of the November 2007 harmonization meeting. The content was folded into AddressUse (2.16.840.1.113883.5.1119), which replaces this code system.
RelationalOperator
ActRelationshipJoin
Charset	Internet Assigned Numbers Authority (IANA) Charset Types
SpecimenType
HL7 Code System Type
DocumentStorage	Identifies the storage status of a document.
RoleCode	A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.
RouteOfAdministration	The path the administered medication takes to get into the body or into contact with the body.
HL7Realm	**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.
MdfHmdMetSourceType	Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
QueryPriority
CodingRationale	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.
Calendar Cycle Codes	Calendar cycle identifiers
MDFSubjectAreaPrefix	The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used.
EntityNamePartQualifierR2	**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.
EncounterSpecialCourtesy
VaccineManufacturer	The manufacturer of a vaccine.
Work Classification (Occupational Data for Health)	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.).
SubstitutionCondition	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.
PatientImportance	Patient VIP code
MapRelationship	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
RelationshipConjunction
TargetAwareness
EntityHandling
TableFrame	These values are defined within the XHTML 4.0 Table Model
HL7ITSType	**Description:** Codes identifying types of HL7 Implementation Technology Specifications
RoleClass	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.
AcknowledgementType	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.
QueryQuantityUnit	Values in this domain specify the units of a query quantity limited request. **Deprecation Comment:** Deprecated as per 11/2008 Harmonization cleanup; internal and obsolete HL7 usage, no longer used. This is a holdover. It is not referenced. It is superseded by QueryRequestLimit.
AdministrativeGender	The gender of a person used for adminstrative purposes (as opposed to clinical gender)
HL7ContextConductionStyle	The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.
HL7CMETAttribution
Media Type	Internet Assigned Numbers Authority (IANA) Mime Media Types. Identifies the type of the encapsulated data and identifies a method to interpret or render the data. The IANA defined domain of media types is established by the Internet standard RFC 2045 \[http://www.ietf.org/rfc/rfc2045.txt\] and 2046 \[http://www.ietf.org/rfc/rfc2046.txt\]. RFC 2046 defines the media type to consist of two parts: 1. top level media type, and 2. media subtype However, this HL7 datatypes specification treats the entire media type as one atomic code symbol in the form defined by IANA, i.e., top level type followed by a slash "/" followed by media subtype. Currently defined media types are registered in a database \[http://www.iana.org/assignments/media-types/index.html\] maintained by IANA. Currently several hundred different MIME media types are defined, with the list growing rapidly. In general, all those types defined by the IANA syntax MAY be used. This code system is a substet of all possible media type codes which are used in HL7 Standaards and Implementation Guides. More information and documentation of this content can be found at Multipurpose Internet Mail Extensions (MIME) Part Four - BCP 13. \[http://tools.ietf.org/html/bcp13\]
LanguageAbilityMode	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.
ParticipationMode	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.
TransmissionRelationshipTypeCode	**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.
TimingEvent
Sequencing	Specifies sequence of sort order.
HtmlLinkType	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
HL7PublishingDomain	**Description:** Codes for HL7 publishing domains (specific content area)
Style Type	<ns1:p>The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style</ns1:p>
MessageWaitingPriority	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.
ContainerCap	The type of cap associated with a container
ResponseMode	Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.
AddressPartType	**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"
EntityNameUseR2	**Description:**A set of codes advising a system or user which name in a set of names to select for a given purpose.
PersonDisabilityType	A code identifying a person's disability.
ParticipationType
ActMood	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.
MaritalStatus	\* \* \* 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.
ParticipationSignature	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.)
CalendarType
VaccineType	The kind of vaccine.
ProbabilityDistributionType
TelecommunicationAddressUse	*Deprecation Comment:* This code system was deprecated as of the November 2007 harmonization meeting. The content was folded into AddressUse (2.16.840.1.113883.5.1119), which replaces this code system.
IntegrityCheckAlgorithm
EntityCode	*OpenIssue:* Missing description.
ProcessingMode
Calendar
ActClass
DocumentCompletion	Identifies the current completion state of a clinical document.

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming with this implementation guide

NamingSystem/icpc-DAN	The International Classification of Primary Care (ICPC). Danish Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/nanda	The terminology consists of standardized terms and codes for patient problems or life processes expressed as nursing diagnoses. These data elements would be classified by HL7 as "observations". The taxonomy is multi-axial. It consists of 12 domains and 36 classes. All domains and classes are defined. There are 7 axes with definitions for each. Each nursing diagnosis consists of: a concept label or term expressed as a noun or a noun phrase; a definition of the term; a set of defining characteristics (signs and symptoms) of the diagnostic term; an approved list of modifiers of the term; a set of risk factors with definitions; and a set of related factors (or etiologies) for the term. The system preserves semantics by having robust review procedures and policies to ensure against semantic drift in the meanings of the encoded terms over time. NANDA as an organization is committed to updating the terminology on a regular biannual basis. NANDA has been in existence since 1973 and is thus the oldest developer of standardized language in nursing. Most other nursing language systems use many of the older NANDA terms in their vocabularies. The express purpose of the organization is to develop a comprehensive standardized nursing language that captures the conclusions that nurses make based on observations - in effect, the nursing diagnoses. The work is a continuing effort and diagnoses are revised, retired or added bi-annually. The codes are simple integers and are not linked to each other. If a diagnostic term is retired, the code is also retired. If a new diagnosis is added a new code is given to that term. If a diagnostic term is revised, the code is kept intact but the date of the revision is published alongside the term. Domains and classes are not coded.
NamingSystem/v3-iso3166-1	Identifies the coding system published in the ISO 3166-1 Standard for Country codes. This standard is released periodically, and a new OID will be assigned by ISO for new editions.
NamingSystem/MDREX	Medical Dictionary for Regulatory Activities Terminology (MedDRA), with expanded abbreviations, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004.
NamingSystem/icd9	ICD9
NamingSystem/EPSG-GeodeticParameterDataset	**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. **Deprecation Comment:** This has been superceded by the two code systems EPSG-CRS and EPSG-CA
NamingSystem/v3-cpt-4	American Medical Association's Current Procedure Terminology 4 (CPT-4) codes.
NamingSystem/CDS	CDC Surveillance
NamingSystem/CD2	American Dental Association's Current Dental Terminology 2 (CDT-2) codes.
NamingSystem/FDBHICCode	The FDB Hierarchical Ingredient Code is a six character identifier that represents an active ingredient and its specific therapeutic classification.
NamingSystem/icd10CM	The International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM), describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases. The ICD-10-CM codes can be used as the value of the Act.cd attribute.
NamingSystem/icd10ae	International Statistical Classification of Diseases and Related Health Problems (ICD-10): Americanized Version. 10th rev. Geneva (Switzerland): World Health Organization, 1998.
NamingSystem/pclocd	The pan Canadian LOINC Observation Code Database (pCLOCD) is the Canadian version of the LOINC(tm) database. It was created using the LOINC(tm) records and attributes that were constrained for Canadian use and supplemented to specifically meet Canadian requirements. It contains the core LOINC(tm) attributes as required by Regenstrief copyright rules. The LOINC(tm) Component has been customized to meet Canadian requirements and is displayed as the pan Canadian Component Name. This component name is the basis for the pan Canadian Display Name. Core attributes are include both English and Canadian French. This code system contains supplemental "X" codes defined in the pCLOCD that do not yet exist in the LOINC code system.
NamingSystem/PHRaceAndEthnicityCDC	Codes for Race, authored and maintained by the CDC
NamingSystem/ICD-9DualCoding	ICD-9 Dual Coding Expression Syntax", description: ICD-9 allows dual coding. Refer to Section ?? of the ICD-9 Instruction Manual (ref?). This OID identifies the code system that describes how to encode Dual Coding in a CD compatible expression (for Datatypes R2 CD only). An ICD-9 dual code expression SHALL consist of two ICD-9 codes separated by space. This code system SHALL NOT be used for single ICD-9 codes; the normal ICD-9 code system oid which is 2.16.840.1.113883.6.3 should be used in this case. DisplayName SHALL not be used. Dual code expressions SHALL only be used per the rules described in the ICD-9 instruction manual. **An example CD:**<br></br><example code="989.5 E905.9" codeSystem="2.16.840.1.113883.6.261"><br></br><originalText value="ANAPHYLAXIS DUE TO BITE OR STING"/><br></br></example><br></br>Where 989.5 is: "Toxic effect of venom" and E905.9 is: "Bite or sting"
NamingSystem/icpc-GER	The International Classification of Primary Care (ICPC). German Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/snm	Systemized Nomenclature in Medicine (SNOMED)
NamingSystem/v3-hc-AIC	**Description:** A code assigned to any component that has medicinal properties, and supplies pharmacological activity or other direct effect in the diagnosis, cure, mitigation, treatment or prevention of disease, or to affect the structure or any function of the body of man or other animals. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
NamingSystem/DEEDS416	Glasgow motor component assessment
NamingSystem/DEEDS402	Mode of transport to ED
NamingSystem/read-Codes	Clinical Terms Version 3 contains over 200,000 coded concepts arranged in a sub-type hierarchical structure. Top level hierarchy sections: Disorders Findings Morphology Surgical procedures Regimes & therapies Investigations Stages & scales Occupations Organisms Units Drugs Appliances & equipment
NamingSystem/NHSNProcedureCategory	NHSN Procedure Category
NamingSystem/iso3166-2	Identifies the coding system published in the ISO 3166-2 Standard for Country Subdivision codes. This standard is released periodically, and a new OID will be assigned by ISO for new editions.
NamingSystem/standardBillingUnit	NCPDP standard product billing codes of NCPDP field Unit of Measure (600-28). This billing code is assigned per product, placed in the Structured Product Label, and used in the pharmacy billing processing for consistent billing unit.
NamingSystem/whoARTfl	WHO Adverse Drug Reaction Terminology (WHOART). Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. This branch node OID contains identifiers for the different foreign language versions of this terminology. For more information, see http://www.umc-products.com/graphics/3149.pdf
NamingSystem/usEPAsrs	The United States Environmental Protection Agency's (US EPA) Substance Registry System (SRS) provides information on substances and how they are represented in US environmental statutes, in US EPA information systems, and in information systems owned by other organizations. The SRS provides standardized identification for each substance to improve data quality in US EPA systems and elsewhere.
NamingSystem/DEEDS414	Glasgow eye opening assessment
NamingSystem/epsg-crs	**Description:** The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.
NamingSystem/icd10PCS	ICD Procedure Coding System (ICD 10 PCS)
NamingSystem/MDRDUT	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Dutch Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the Dutch language version as encapsulated in the UMLS..
NamingSystem/v3-hgnc	HUGO Gene Nomenclature Committee (HGNC) is committee jointly funded by the US National Human Genome Research Institute and the Wellcome Trust (UK). It operates under the auspices of HUGO, with key policy advice from an International Advisory Committee, and is responsible for approving gene names and symbols. All approved symbols are stored in the HGNC database. Each symbol is unique and each gene is only given one approved gene symbol. More than 28,000 human gene symbols and names have been approved so far. The vast majority of these is for protein-coding genes, but also includes symbols for peudogenes, non-coding RNAs, phenotypes and genomic features. HGNC gene symbols can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model Implementation Guide, HGNC gene symbols can be used to as the observation values for gene identifiers. For example, OBX|1|CWE|48018-6^Gene identifier^||BRCA1^HGNC| Versioning Information: The version of the HGNC database is reported using the last updated date and timestamp. The last updated date and timestamp is posted on the main HGNC Search screen in the format like "Monday March 30 23:00:56 2009". HGNC is updated daily. HGNC is a free database for the public.
NamingSystem/dicomMDLTY	DICOM modality codes
NamingSystem/USCOC	Coding system of United States Census Occupation Codes, published by the US Governmetn Bureau of the Census. Doucmentation and Crosswalk mapping between the COC and the SOC and NAICS code systems available at http://www.census.gov/hhes/www/ioindex/view.html
NamingSystem/ICSD	International Classification of Sleep Disorders
NamingSystem/rcV2	The Read Codes Version 2 contains over 70,000 coded concepts arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs
NamingSystem/v3-hgvs	HGVS nomenclatures are the guidelines for mutation nomenclature made by the Human Genome Variation Society. HGVS nomenclature can be used with the HL7 coded data type (code data type that accepts expression data, or a coded expression data type). This coded data type should be able to distinguish expressions in HGVS nomenclature from coded concepts. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, HGVS nomenclature can be used to as the observation values for DNA sequence variations. For example, OBX|1|CWE|48004-6^DNA Sequence Variation^LN||c.1129C>T^^HGVS| Versioning information: The HGVS nomenclature for the description of sequence variants was last modified Feb 20, 2008. The HGVS nomenclature for the description of protein sequence variants was last modified May 12, 2007. The HGVS nomenclature for the description of DNA sequence variants was last modified June 15, 2007 The HGVS nomenclature for the description of RNA sequence variants was last modified May 12, 2007 HGVS nomenclatures can be used freely by the public.
NamingSystem/fipspub92	FIPSPUB92 - GUIDELINE FOR STANDARD OCCUPATIONAL CLASSIFICATION (SOC) CODES, version 1983 February 24. This entry is now obsolete, as FIPS92 was withdrawn from use in February 2005 by the US Government. It has been replaced by 2.16.840.1.113883.6.243; please use that OID instead.
NamingSystem/MDDX	Medispan Diagnostic Codes
NamingSystem/abcCodes	Five character alphabetic codes fit into current claims processing software or onto standard paper claim forms. ABC Codes give business parity to licensed CAM and nurse providers who file claims to insurance companies. .
NamingSystem/NHSNOccasionOfDetection	NHSN Occasion Of Detection
NamingSystem/DEEDS415	Glasgow verbal component assessment
NamingSystem/UMD	MDNS
NamingSystem/iso4217	ISO 4217 currency codes.
NamingSystem/DEEDS405	ED Source of Referral
NamingSystem/ietf3066	from OID registry
NamingSystem/v3-scptype	This code system contains the list of provider types used in the pan-Canadian specifications.
NamingSystem/v3-hc-AIGN	**Description:** Codes for particular collections of active ingredients combined at specific strengths. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
NamingSystem/csaid	Nature of injury (NOI) codes, which are part of the Work Injury or Disease Information coding system (CAN/CSA-Z795-96 - R2003). The CSA code set includes 3 parts: Nature of injury (NOI), body part (BP), side of body (SB). For example: * NOI - Cut or laceration Injury = 03400 * BP - Upper Arm body part = 31100 * SOB - Left Side of Body = L The Body Part codes are qualified by the Side of Body codes code system, to be more precise in specifying the location of the injury being coded. Code set is maintained by the Canadian Standards Association (CSA). set is maintained by the Canadian Standards Association (CSA). The Canadian Standards Association 5060 Spectrum Way Mississauga, Ontario Canada L4W 5N6 Phone: (416) 747-4000 1-800-463-6727 Fax: (416) 747-2473
NamingSystem/medcin	MEDCIN contains more than 175,000 clinical data elements arranged in a hierarchy, with each item having weighted links to relevant diagnoses. The clinical data elements are organized into six basic termtypes designed to accommodate information relevant to a clinical encounter. The basic termtypes in MEDCIN's terminological hierarchy are as follows: Symptoms History Physical Examination Tests Diagnoses Therapy Within this basic structure, MEDCIN terms are further organized in a ten level terminological hierarchy, supplemented by an optional, multi-hierarchical diagnostic index. For example, the symptom of "difficulty breathing" is placed in the terminological hierarchy as a subsidiary (or "child") finding of "pulmonary symptoms," although the presence (or absence) of difficulty breathing can related to conditions as diverse as myocardial infarction, bronchitis, pharyngeal foreign bodies, asthma, pulmonary embolism, etc. MEDCIN's diagnostic index provides more than 800 such links for difficulty breathing.
NamingSystem/ENZC	Enzyme Codes
NamingSystem/JC8	Japanese Chemistry
NamingSystem/naics	North American Industry Classification System(NAICS) for the United States, a new economic classification system that replaces the 1987 Standard Industrial Classification (SIC) for statistical purposes. NAICS is a system for classifying establishments by type of economic activity. Its purposes are: (1) to facilitate the collection, tabulation, presentation, and analysis of data relating to establishments, and (2) to promote uniformity and comparability in the presentation of statistical data describing the economy. NAICS will be used by Federal statistical agencies that collect or publish data by industry.
NamingSystem/whoGER	WHO Adverse Drug Reaction Terminology (WHOART). German Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
NamingSystem/FDDC	First DataBank Drug Codes
NamingSystem/UC	UCDS
NamingSystem/v3-snomed-CT	SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid "semantic drift" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT's concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique "fully-specified name," a preferred term, and, optionally, synonyms. The descriptions include English, Spanish, and German.
NamingSystem/NHSNSSIAnatomicSite	NHSN Surgical Site Infection Anatomic Site
NamingSystem/DEEDS412	ED Responsiveness Assessment
NamingSystem/NHSNInfectionType	NHSN Infection Type
NamingSystem/GCRT	GCRT Route of Administration Code (1-character) a one-character alphanumeric column that provides the normal site or method by which a drug is administered, such as oral, injection, or topical. A GCRT is associated to each GCN\_SEQNO to identify that component of the generic drug formulation.
NamingSystem/v3-brazilianProcedureCodesSUS	Brazilian Procedure Codes used in the National Health System
NamingSystem/v3-fda-FCE	Entered erroneously - do not use. The correct OID for this identifier system is 2.16.840.1.113883.4.345.
NamingSystem/DEEDS407	Code for Initial Healthcare Encounter for Chief Complaint
NamingSystem/dicomqry	DICOM Query Label
NamingSystem/icd10-CA	Canadian Coding Standards ICD-10 CA. These standards are a compilation of international rules of coding as established by the World Health Organization (International Classification of Diseases, 10th Revision, Volume 2) and the Diagnosis Typing Standard developed to denote case complexity for application in Canadian facilities. For example: * L40 Psoriasis * L40.0 Psoriasis vulgaris * Nummular psoriasis * Plaque psoriasis * L40.1 Generalized pustular psoriasis * Impetigo herpetiformis * Von ZumbuschaTMs disease * L40.2 Acrodermatitis continua * L40.3 Pustulosis palmaris et plantaris * L40.4 Guttate psoriasis * L40.5\* Arthropathic psoriasis (M07.0-M07.3\*)(M09.0\*) * L40.8 Other psoriasis * Erythroderma psoraticum * Erythrodermic psoriasis * Flexural psoriasis * L40.9 Psoriasis unspecified They are maintained by CIHI (Canadian Institute for Health Information). CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca
NamingSystem/cpnum	Gold Standard's Clinical Pharmacology Monograph Number
NamingSystem/MGPI	Medispan GPI
NamingSystem/iso639-1ret	Codes for the Representation of Names of Languages Part 1: Alpha-2 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. *DeprecationComment:* This code system is being deprecated, as the OID identifying it has been replaced with the correct ISO OID of 1.0.639.1
NamingSystem/CCC	Clinical Care Classification System (formerly Home Health Care Classification system) codes. The Clinical Care Classification (CCC) consists of two taxonomies: CCC of Nursing Diagnoses and CCC of Nursing Interventions both of which are classified by 21 Care Components. Each of these are classified by Care Components which provide a standardized framework for documenting patient care in hospitals, home health agencies, ambulatory care clinics, and other health care settings.
NamingSystem/icpc-ITA	The International Classification of Primary Care (ICPC). Italian Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/DEEDS508	Safety Equipment Use
NamingSystem/MDRFRE	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, French Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the French language version as encapsulated in the UMLS..
NamingSystem/oms	The Omaha System provides standardized terms, definitions, and codes for observations and procedures, specifically for client problems, multidisciplinary interventions including those focusing on assessment and care, and problem-specific client outcomes.
NamingSystem/SDM	SNOMED-DICOM Microglossary
NamingSystem/MDRAE	Medical Dictionary for Regulatory Activities Terminology (MedDRA), American English Equivalents, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004 This is the English language version as encapsulated in the UMLS..
NamingSystem/MEDX	Medical Economics Diagnostic Codes
NamingSystem/AS4E	AS4 Neurophysiology Codes
NamingSystem/v3-rxNorm	RxNorm provides standard names for clinical drugs (active ingredient + strength + dose form) and for dose forms as administered to a patient. It provides links from clinical drugs, both branded and generic, to their active ingredients, drug components (active ingredient + strength), and related brand names. NDCs (National Drug Codes) for specific drug products (where there are often many NDC codes for a single product) are linked to that product in RxNorm. RxNorm links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software, including those of First Databank, Micromedex, MediSpan, and Multum. By providing links between these vocabularies, RxNorm can mediate messages between systems not using the same software and vocabulary. RxNorm is one of a suite of designated standards for use in U.S. Federal Government systems for the electronic exchange of clinical health information.
NamingSystem/IUPP	IUPAC/IFCC Property Codes
NamingSystem/NHSNLCBIPathways	NHSN Laboratory Confirmed Bloodstream Infection Pathways
NamingSystem/MDRSPA	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Spanish Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004. This is the Spanish language version as encapsulated in the UMLS..
NamingSystem/MVX	CDC Vaccine Manufacturer Codes
NamingSystem/hc-NPN	A unique identifier assigned to natural health products that have been issued a product licence by Health Canada. http://www.hc-sc.gc.ca/dhp-mps/prodnatur/applications/licen-prod/lnhpd-bdpsnh-eng.php
NamingSystem/CDCM	CDC Methods/Instruments Codes
NamingSystem/NHSNKneeReplacement	NHSN Knee Replacement
NamingSystem/v3-lrg	In collaboration with NCBI, the European Bioinformatics Institute (EBI) is developing the Locus Reference Genomic Sequences (LRG) database, which is a database of reference sequences. LRG is a system for providing a genomic DNA sequence representation of a single gene that is idealized, has a permanent ID (with no versioning), and core content that never changes. LRG is not a nomenclature system. More than one LRG could be created for a region of interest, should that need arise. Additional annotations will be present that may change with time (each item carrying its own date stamp), so that the latest ancillary knowledge about a gene is directly available. In other words, an LRG sequence and its core annotation are not meant to represent current biology knowledge, but to provide a standard for reporting variation in a stable coordinate system. The combination of the LRG plus the updatable-annotation layer will be used to support the biological interpretation of variants. LRG identifiers can be used with the HL7 coded data type (code data type that accepts expression data, or a coded expression data type). This coded data type will be gene symbols can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, LRG identifiers can be used to as the observation values for Genomic Reference Sequence Identifier (LOINC code: 48013-7). LRG is a database that can be used freely by the public.
NamingSystem/NHSNSpinalFusionApproach	NHSN Spinal Fusion Approach
NamingSystem/PHIndustryCDCCensus2010	2010 Industry coding system used by CDC (NIOSH and NCHS) for coding industry text. Industry describes an economic/business sector comprised of businesses/ enterprises concerned with the output of a specified category of products or services.
NamingSystem/icpc2-icd10-THSRS	A diagnostic Terminology for semi-automatic Double Coding in Electronic Patient Records The thesaurus is a part of the CD Rom: "ICPC in the Amsterdam Transition Project. Extended Version. IM Okkes, SK Oskam, H. Lamberts. Amsterdam: Academic Medical Center/University of Amsterdam. Department of Family Medicine", see also the web site http://www.transitieproject.nl for this application of the thesaurus. This bilingual (English/Dutch) ICPC2-ICD10 thesaurus is derived from an extended version of the CD-Rom ICPC in the Amsterdam Transition Project, that was published as a companion to ICPC-2-R by Oxford University Press (2005). As was the case with the former thesaurus (published in Dutch in 2003), the content of this new thesaurus may be copied for academic purposes, and be used for teaching and research under the usual referencing conditions. Any other and/or commercial use requires prior permission from the authors, represented by Dr. Inge Okkes (see below). It is strongly recommended that you first go through the ICPC Tutorial, the Manual and the Glossary, and consider printing them. Becker, H.W., C. van Boven, S.K. Oskam, I.M. Okkes, W. Hirs, H. Lamberts. ICPC2 - ICD10 Thesaurus, Version March, 2004. Amsterdam: Project "Adaptation ICPC, integration and implementation of ICPC2 and ICD10(-CM)." Department of General Practice, Academic
NamingSystem/mddid	Medispan Drug Descriptor ID Entry autogenerated to support Sources from the UMLS. Full metadata set still incomplete.
NamingSystem/IETF1766	Codes representing languages for which a person has some level of proficiency for written or spoken communication. *Examples:* Spanish, Italian, German, English, American Sign, etc.
NamingSystem/MDRPOR	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Portuguese Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004. This is the Portuguese language version as encapsulated in the UMLS..
NamingSystem/metabolicSyndrome	A collection of metabolic risk factors in one individual. The root causes of metabolic syndrome are overweight / obesity, physical inactivity, and genetic factors. Various risk factors have been included in metabolic syndrome. Factors generally accepted as being characteristic of this syndrome include abdominal obesity, atherogenic dyslipidemia, raised blood pressure, insulin resistence with or without glucose intolerance, prothrombotic state, and proinflammatory state.
NamingSystem/iso639-1	**Description:** Codes for the Representation of Names of Languages Part 1: Alpha-2 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. This part of ISO 639 provides a code consisting of language code elements comprising two-letter language identifiers for the representation of names of languages. The language identifiers according to this part of ISO 639 were devised originally for use in terminology, lexicography and linguistics, but may be adopted for any application requiring the expression of language in two- letter coded form, especially in computerized systems. The alpha-2 code was devised for practical use for most of the major languages of the world that are not only most frequently represented in the total body of the world's literature, but which also comprise a considerable volume of specialized languages and terminologies. Additional language identifiers are created when it becomes apparent that a significant body of documentation written in specialized languages and terminologies exists. Languages designed exclusively for machine use, such as computer-programming languages, are not included in this code. The code set is available from http://www.iso.org/iso/iso\_catalogue/catalogue\_ics/catalogue\_detail\_ics.htm? csnumber=22109&ICS1=1&ICS2=140&ICS3=20
NamingSystem/dmdICD10	Internationale Klassifikation der Krankheiten 10 \[German translation of ICD10\]. Germany: Deutsches Institut fuer Medizinische Dokumentation und Information, 1998.
NamingSystem/camncvs	CAM & Nursing Coding Vocabulary Set
NamingSystem/IUPC	IUPAC/IFCC Component Codes
NamingSystem/icd9cm	International Classification of Diseases revision 9, with Clinical Modifications (ICD 9 CM)
NamingSystem/icpc2E-ENG	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
NamingSystem/MTHMDRSPA	Metathesaurus Forms of Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, Spanish Edition. Bethesda, MD: National Library of Medicine, March 2004.
NamingSystem/ICD10dut	Hirs, W., H.W. Becker, C. van Boven, S.K. Oskam, I.M. Okkes, H. Lamberts. ICD-10, Dutch Translation, 200403. Amsterdam: Department of General Practice, Academic Medical Center/University of Amsterdam, Dutch College of General Practitioners (NHG), March 20
NamingSystem/iso639-3	**Description:** ISO 639-3 is a code that aims to define three-letter identifiers for all known human languages. At the core of ISO 639-3 are the individual languages already accounted for in ISO 639-2. The large number of living languages in the initial inventory of ISO 639-3 beyond those already included in ISO 639-2 was derived primarily from Ethnologue (15th edition). Additional extinct, ancient, historic, and constructed languages have been obtained from Linguist List. SIL International has been designated as the ISO 639-3/RA for the purpose of processing requests for alpha-3 language codes comprising the International Standard, Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages. The ISO 639-3/RA receives and reviews applications for requesting new language codes and for the change of existing ones according to criteria indicated in the standard. It maintains an accurate list of information associated with registered language codes which can be viewed on or downloaded from this website, and processes updates of registered language codes. Notification of pending and adopted updates are also distributed on a regular basis to subscribers and other parties.
NamingSystem/nddf	National Drug Data File Plus Source Vocabulary 2004. San Bruno, CA: First DataBank, March 11, 2004. This entry was generated to support the Sources in the UMLS. Additional metadata is still missing.
NamingSystem/icpc2-icd10-DUT	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
NamingSystem/v3-refSeq	The Reference Sequence (RefSeq) is one of the NCBI projects, the RefSeq collection aims to provide a comprehensive, integrated, non-redundant, well-annotated set of sequences, including genomic DNA, transcripts, and proteins. ReqSeq is accessible via BLAST, Entrez, and the NCBI FTP site. Information is also available in Entrez Genomes and Entrez Gene, and for some genomes additional information is available in the Map Viewer. RefSeq entries can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, RefSeq entries can be used to as the observation values for genomic reference sequence identifiers (LOINC \#: 48013-7). More information may be found at: http://www.ncbi.nlm.nih.gov/RefSeq Versioning informaiton: The latest release of RefSeq was released on May 13, 2009 with the release number of 35. RefSeq generates new releases roughly every two months. The dates of the three previous releases were: Release 34, March 12, 2009 Release 33, January 20, 2009 Release 32, November 17, 2008 RefSeq is a free database for the public.
NamingSystem/PHOccupationalDataForHealthODH	The concepts representing the values supporting Occupational Data for Health, including Job Supervisory Level or Pay Grade (ODH) code system consists of data elements that describe a person's work information, structured to facilitate individual, population, and public health use; not intended to support billing.).
NamingSystem/DEEDS519	Clinical Finding Data Source
NamingSystem/DEEDS210	Code for ED Practitioner Role
NamingSystem/icpc-ENG	The International Classification of Primary Care (ICPC). Swedish Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/ACR	American College of Radiology finding codes
NamingSystem/v3-scpqual	This code system contains the list of provider qualifications used in the pan-Canadian specifications.
NamingSystem/v3-loinc	Logical Observation Identifier Names and Codes (LOINC)
NamingSystem/v3-fda-FFRN	Entered in error originally - do not use. Correct OID for this item is 2.16.840.1.113883.4.344.
NamingSystem/nmmds	The NMMDS is the minimum set of items of information with uniform definitions and categories concerning the specific dimension of the context of patient care delivery. It represents the minimum data used to support the management and administration of patient/nursing care delivery across all types of settings. The NMMDS is composed of seventeen (17) data elements organized into three categories: environment, nurse resources, and financial resources. See Tables 1-3 for the elements and related definitions organized by each categories. The NMMDS most appropriately focuses at the first level of accountability for patient/client/family/community nursing care: this may be the delivery unit, service, or center of excellence level. The NMMDS supports numerous constructed variables as well as aggregation of data at the unit, institution, network, and system, etc levels. This minimum data set provides the structure for the collection of uniform information that influences quality of patient care, directly and indirectly.
NamingSystem/iso639-2	**Description:** Codes for the representation of names of languages, 3 character alphabetic codes. This has been superceded by ISO 639-3 for many purposes. ISO 639-2 was released in 1998. The code set is available from http://www.iso.org/iso/iso\_catalogue/catalogue\_tc/catalogue\_detail.htm?csnumber=4767
NamingSystem/hi	Health Outcomes
NamingSystem/v3-icpc2E	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
NamingSystem/v3-ndc	National drug codes
NamingSystem/icd10	International Classification of Diseases revision 10 (ICD 10)
NamingSystem/iso3166-1edition2numeric	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, numeric codes.
NamingSystem/NHSNHipReplacement	NHSN Hip Replacement
NamingSystem/E5	Euclides quantity codes
NamingSystem/hsloc	A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the National Healthcare Safety Network (NHSN) location code system that has been developed over a number of years through CDC's 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. The HSLOC content, including relationships can be acced at the following location: http://www.cdc.gov/phin/activities/standards/vocabulary/index.html
NamingSystem/fdk	FDA K10
NamingSystem/v3-nciThesaurus	NCI Thesaurus NCI Thesaurus is a biomedical thesaurus created specifically to meet the needs of the cancer research community, especially those engaged in translational research NCI Thesaurus is produced by the NCI Enterprise Vocabulary Services project. The NCI Thesaurus is provided under an open content license.
NamingSystem/icnp	ICNP(r) is a combinatorial terminology, using a multi-axial structure. ICNP(r) provides standardized terms and codes for terms in two classifications that can be used to compose or create pre-coordinated concepts to represent observations and procedures, specifically, patient problems/nursing diagnoses, nursing interventions including those focused on assessment and actual or expected (goal) outcomes. The ICNP(r) Classification for Nursing Phenomena is used to compose concepts or statements to represent observations (nursing diagnoses, patient problems, patient status, patient outcomes). The ICNP(r) Nursing Actions Classification is used to compose concepts or statements to represent procedures (nursing interventions)
NamingSystem/NHSNVocabulary	NHSN HAI Vocabulary used for Single Value bindingsto Observation Identifier
NamingSystem/sic	The Standard Industrial Classification Codes that appear in a company's disseminated EDGAR filings indicate the company's type of business. These codes are also used in the Division of Corporation Finance as a basis for assigning review responsibility for the company's filings. For example, a company whose business was Metal Mining (SIC 1000) would have its filings reviewed by staffers in A/D Office 4. Note that this code system is published both by the US Bureau of Labor Statistics (BLS) at http://www.sec.gov/info/edgar/siccodes.htm, and by the US Occupational & Safety Health Administration (OSHA) at http://www.osha.gov/pls/imis/sic\_manual.html.
NamingSystem/hhcc	HHCC - Home Health Codes
NamingSystem/icpc-SPA	The International Classification of Primary Care (ICPC). Spanish Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/icpc2E-P-AE	International Classification of Primary Care, Version 2-Plus, Australian Modification. Americanized English Equivalents, January, 2000. Produced by NLM. Bethesda (MD): National Library of Medicine, UMLS project
NamingSystem/iso21000-6-2004E-RDD	ISO/IEC 21000-6:2004 describes a Rights Data Dictionary which comprises a set of clear, consistent, structured, integrated and uniquely identified terms to support the MPEG-21 Rights Expression Language (REL), ISO/IEC 21000-5. Annex A specifies the methodology for and structure of the RDD Dictionary, and specifies how further Terms may be defined under the governance of a Registration Authority, requirements for which are described in Annex C. Taken together, these specifications and the RDD Dictionary and Database make up the RDD System. Use of the RDD System will facilitate the accurate exchange and processing of information between interested parties involved in the administration of rights in, and use of, Digital Items, and in particular it is intended to support ISO/IEC 21000-5 (REL). Clause 6 describes how ISO/IEC 21000-6:2004 relates to ISO/IEC 21000-5. As well as providing definitions of terms for use in ISO/IEC 21000-5, the RDD System is designed to support the mapping of terms from different namespaces. Such mapping will enable the transformation of metadata from the terminology of one namespace (or Authority) into that of another namespace. Mapping, to ensure minimum ambiguity or loss of semantic integrity, will be the responsibility of the Registration Authority. Provision of automated trm look-up is also a requirement. The RDD Dictionary is a prescriptive dctionary, in the sense that it defines a single meaning for a trm represented by a particular RddAuthorized TermName, but it is also inclusive in that it can recognize the prescription of other Headwords and definitions by other Authorities and incorporates them through mappings. The RDD Dictionary also supports the circumstance that the same name may have different meanings under different Authorities. ISO/IEC 21000-6:2004describes audit provisions so that additions, amendments and deletions to Terms and their attributes can be tracked. ISO/IEC 21000-6:2004 recognizes legal definitions as and only as Terms from other Authorities that can be mapped into the RDD Dictionary. Therefore Terms that are directly authorized by the RDD Registration Authority neither define nor prescribe intellectual property rights or other legal entities.
NamingSystem/whoPOR	WHO Adverse Drug Reaction Terminology (WHOART). Portuguese Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
NamingSystem/USZIPCODES	Coding system of defined postal zip codes for the United States of America.
NamingSystem/DEEDS	root for the DEEDS code sets
NamingSystem/E6	Euclides Lab method codes
NamingSystem/icpc-FIN	The International Classification of Primary Care (ICPC). Finnish Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/icpc-HEB	The International Classification of Primary Care (ICPC). Hebrew Translation, Denmark: World Organisation of Family Doctors, 1993
NamingSystem/rcFB	The Read Codes Four Byte Set consists of 4 alphanumeric characters. This version contains approximately 40,000 codes arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs
NamingSystem/v3-cci	CCI - Canadian Classification of Health Interventions, developed to accompany ICD-10-CA, maintained by CIHI (Canadian Institute for Health Information). For example: sections 3.AA-3.BZ Diagnostic Imaging Interventions on the Nervous System 3.AN.^ ^.^ ^ Diagnostic Imaging Interventions on the Brain 3.AN.40. ^ ^ Magnetic Resonance Imaging, Brain Incudes: That for meninges, ventricles, cerebellum, brain stem, cisterna \[of brain\], posterior fossa MRI, brain 3.AN.40.VA without contrast 3.AN.40.VC following intravenous injection of contrast 3.AN.40.VZ following percutaneous injection of contrast CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca
NamingSystem/icpc2E-P	International Classification of Primary Care, Version 2-Plus. Produced by NLM. Bethesda (MD): National Library of Medicine, UMLS project. This node has the various modifications and translations produced under it.
NamingSystem/atc	American Type Culture Collection
NamingSystem/CLP	CLIP
NamingSystem/deeds-old	retired root for DEEDs from earlier work. Superceded.
NamingSystem/E7	Euclides Lab equipment codes
NamingSystem/CDARUS	Coding system intended for use in the Russian clinical documents
NamingSystem/mth-icpc2-icd10-AE	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
NamingSystem/mth-icpc2-icd10-7B	International Classification of Primary Care / prepared by the Classification Committee of the World Organization of National Colleges, Academies and Academic Associations of General Practitioners/Family Physicians (WONCA), known more briefly as the World
NamingSystem/ib	ISBT 128 is a coding system for blood components, hematopoietic progenitor cells and other tissues. It is comprised of an overall Application Specification, and labeling and coding documents for the separate sections: blood components, hematopoietic progenitor cells (draft), source plasma (draft) and tissues (draft). The documentation is supported by databases: Country/Collection Facility, Product Code (blood components), Product Code (hematopoietic progenitor sells), Product Code (source plasma), Product Code (tissues) and Special Testing. ISBT 128 is designed as a series of data structures that are designed to be technology-independent and can be used for bar coding, radio frequency tag encoding and electronic data interchange. The HL7 Blood Bank SIG is currently designing example messages that incorporate ISBT 128 coding. No changes of any kind will be needed to use ISBT 128 in HL7 messages.
NamingSystem/X12.3	X12.3 Data Elementary Dictionary This is the root OID for vocabulary defined internally by X12N. OIDS for each vocabulary will be assigned underneath this oid by appending the X12N data element id to the root OID. Data Element 1336 is Insurance Type Code, so the OID for the X12N Insurance Type Code vocabulary will be 2.16.840.1.113883.6.255.1336
NamingSystem/hibccHIN	HIBCC
NamingSystem/v3-hc-DIN	**Description:** A Drug Identification Number (DIN) is a number assigned by Health Canada to a drug product prior to being marketed in Canada. It consists of eight digits (numbers) generated by a computer system in the Submission and Information Policy Division. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
NamingSystem/icpc-FRE	The International Classification of Primary Care (ICPC). French Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/url	Universal Resource Locator (URL) schemes Currently there is no single authority for URL schemes. The authority for URL scheme assignments clearly lies within IANA or W3C and it is likely that a formal URL/URI assigning authority will be formed soon.
NamingSystem/externalCodeSystems	External coding systems registered in HL7 with an HL7 OID
NamingSystem/ICD-9CM-procedurecodes	The International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II (diagnoses) and III (procedures) describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases and procedures. The ICD-9-CM codes can be used as the value of the Act.cd attribute.
NamingSystem/v3-sctemp	These pan-Canadian codes are maintained in circumstances where the desired code is not yet available in another code system (HL7 code systems, LOINC, SNOMED, etc.) In general, the codes will be deprecated once an equivalent code is available in the preferred code system.
NamingSystem/icd-o-3	International Classification of Diseases for Oncology, version 3. For more information see http://www.who.int/classifications/icd/adaptations/oncology/en/.
NamingSystem/CAS	Chemical abstract codes
NamingSystem/DEEDS506	Injury Activity
NamingSystem/whoSPA	WHO Adverse Drug Reaction Terminology (WHOART). Spanish Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
NamingSystem/CDCA	CDC Analyte Codes
NamingSystem/NHSNSummaryData	NHSN Summary Data
NamingSystem/NHSNBSIRiskFactors	NHSN Blood Stream Infection Risk Factors
NamingSystem/v3-dbSNP	In collaboration with the National Human Genome Research Institute, The National Center for Biotechnology Information has established the dbSNP database to serve as a central repository for both single base nucleotide substitutions and short deletion and insertion polymorphisms. The entries in the dbSNP database can be used with the HL7 coded data type. For example, in the HL7 messages specified according to the HL7 V2 Clinical Genomics Fully LOINC-Qualified Genetic Variation Model, dbSNP entries can be used to as the observation values for DNA sequence variation identifiers. For example, OBX|1|CWE|48004-6^DNA Sequence Variation Identifier^LN||rs55538123^^dbSNP Versioning is identified by the build id. A new build is released approximately every six months or every year. The latest build id is 130, and the dbSNP web query for built 130 was available on Apr 30, 2009. dbSNP is a database that can be used freely by the public. More information may be fouond at: http://www.ncbi.nlm.nih.gov/projects/SNP/
NamingSystem/nic	NIC provides names and values for procedures/orders/service intent related to the treatment activities of nurses and other providers who may perform the same treatment activities. Names, definitions, and associated codes are attached for 486 interventions. Defining activities (anywhere from ten to several dozen) are listed for each of the interventions in the NIC classification book but are not attached to this document.
NamingSystem/IC2	ICHPPC-2
NamingSystem/ics	ICCS
NamingSystem/UPC	Universal Product Code
NamingSystem/naaccrCodes	NAACCR Cancer Registry
NamingSystem/ICD-10DualCoding	ICD-10 allows dual coding. Refer to Section 3.1.3 of the ICD-10 Instruction Manual (2nd Edition, http://www.who.int/entity/classifications/icd/ICD-10\_2nd\_ed\_volume2.pdf). This OID identifies the code system that describes how to encode Dual Coding in a CD compatible expression (for Datatypes R2 CD only). An ICD-10 dual code expression SHALL consist of two ICD-10 codes separated by space. This code system SHALL NOT be used for single ICD-10 codes; the normal ICD-10 code system oid which is 2.16.840.1.113883.6.3 should be used in this case. Dual code expressions SHALL only be used per the rules described in the ICD-10 instruction manual. **An example CD:**<br></br> <example code="J21.8 B95.6" codeSystem="2.16.840.1.113883.6.260"><br></br> <originalText value="Staph aureus bronchiolitis"/><br></br> </example><br></br><br></br> Where:<br></br> J21.8 is: Acute bronchiolitis due to other specified organisms<br></br> B95.6 is: Staphylococcus aureus as the cause of diseases classified to other chapters
NamingSystem/icpc-POR	The International Classification of Primary Care (ICPC). Portuguese Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/CVX	CDC Vaccine Codes
NamingSystem/whoFRE	WHO Adverse Drug Reaction Terminology (WHOART). French Translation. Uppsala (Sweden): WHO Collaborating Centre for International Drug Monitoring, 1997. For more information, see http://www.umc-products.com/graphics/3149.pdf
NamingSystem/nubc-UB92	National Uniform Billing Council, UB 92
NamingSystem/POS	POS Codes
NamingSystem/MEDC	Medical Economics Drug Codes
NamingSystem/icpc2E-P-AUS	International Classification of Primary Care, Version 2-Plus, Australian Modification. January, 2000
NamingSystem/DEEDS422	Heart rate method
NamingSystem/NHSNSSILocationType	NHSN SSI LocationType
NamingSystem/PHOccupationCDCCensus2010	2010 Occupation coding system used by CDC (NIOSH and NCHS) for coding occupation text. Occupation describes a set of activities or tasks that individuals are paid to perform or, if unpaid, define a person's contribution to a household/family business/community.
NamingSystem/VHA	VHA Enterprise Reference Terminology is based on CHI standard terminologies (e.g., SNOMED-CT, LOINC, HL7, NDF-RT, etc.) when available and on VHA own code sets when necessary (e.g., allergens). All concepts used within the VHA clinical environment receive a VHA Unique IDentifier or VUID. VHA Enterprise Reference Terminology complies with the semantics of the HL7 message structure
NamingSystem/icpc	The International Classification of Primary Care (ICPC). Denmark: World Organisation of Family Doctors, 1993. Various language translations are identified beneath this OID.
NamingSystem/icpc2E-DUT	Hirs, W., H.W. Becker, C. van Boven, S.K. Oskam, I.M. Okkes, H. Lamberts. International Classification of Primary Care 2E: 2nd ed. electronic. Dutch Translation. Amsterdam: Department of General Practice, Academic Medical Center/University of Amsterdam, D
NamingSystem/cdcNHSN	CDC - National Healthcare Safety Network (NHSN) code system - A set of patient safety and healthcare personnel safety vocabulary concepts and associated identifiers maintained as a code system by the CDC's National Healthcare Safety Network. CDC NHSN is planning to use these code system concepts in the HAI implementation guide. These concepts would be submitted for the HL7 Ballot (Dec 2008). CDC NHSN can provide complete list of concepts, identifiers and extended attributes for this code system.
NamingSystem/SCDHEC-GISSpatialAccuracyTiers	**Description:** The South Carolina Department of Health and Environmental Control GIS Spatial Data Accuracy Tiers have been derived from the National Standard for Spatial Data Accuracy as a means to categorize the accuracy of spatial data assignment utilizing a variety of tools for capturing coordinates including digitizers, geocoding software and global positioning system devices.
NamingSystem/v3-mdc	The nomenclature relates primarily to vital signs monitoring, but also includes semantics of other medical devices that are commonly used in acute care settings. There are multiple coding partitions each of which has a systematic name consisting of a set of base concepts and differentiating criteria.
NamingSystem/art	WHO Adverse Reaction Terms
NamingSystem/icpc-DUT	The International Classification of Primary Care (ICPC). Dutch Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/icpc2-icd10-ENG	Becker, H.W., C. van Boven, S.K. Oskam, I.M. Okkes, W. Hirs, H. Lamberts. ICPC2 - ICD10 Thesaurus, Version March, 2004. Amsterdam: Project "Adaptation ICPC, integration and implementation of ICPC2 and ICD10(-CM)." Department of General Practice, Academic
NamingSystem/icpc-HUN	The International Classification of Primary Care (ICPC). Hungarian Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/iso3166-1edition2alpha2	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, 2-character alphabetic codes.
NamingSystem/MDRGER	Medical Dictionary for Regulatory Activities Terminology (MedDRA) Version 7.0, German Edition. International conference on Harmonization of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH). Reston, VA: MedDRA MSSO, March 1, 2004 This is the German language version as encapsulated in the UMLS..
NamingSystem/ICD-9CM-diagnosiscodes	The International Classification of Diseases, 9th Revision, Clinical Modification (ICD-9-CM), Volumes I, II (diagnoses) and III (procedures) describes the classification of morbidity and mortality information for statistical purposes and for the indexing of healthcare records by diseases and procedures. The ICD-9-CM codes can be used as the value of the Act.cd attribute.
NamingSystem/UML	Unified Medical Language
NamingSystem/v3-mime	IETF MIME media types
NamingSystem/C5	CPT-5
NamingSystem/umls	UMLS codes as CUIs making up the values in a coding system. More information may be found at http://www.nlm.nih.gov/research/umls/
NamingSystem/DCL	DICOM Class Label
NamingSystem/nciVersionOfNDF-RT	The National Drug File RT (NDF-RT) is published by the US Veterans' Administration (VA). NDF-RT covers clinical drugs used at the VA. The NCI version of NDF-RT is used by NCI to provide automated terminology access to the Food and Drug Administration (FDA) Structured Product Label (SPL) initiative. NCI makes its version of NDF-RT available publicly thru the Web, download via FTP and via open APIs for Java, SOAP and HTTP.
NamingSystem/MSH	Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004
NamingSystem/v3-hc-AIGC	**Description:** Codes for particular grouping of active ingredients. This is the first 5 characters of active ingredient group number. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index\_e.html
NamingSystem/mthicpc2E-AE	Henk Lamberts and Inge Hofmans-Okkes. International Classification of Primary Care 2nd Edition, Electronic, 2E, American English Equivalents. Amsterdam: International Classification of Primary Care / prepared by the Classification Committee of the World Health Organization. Entry derived from the UMLS Metathesaurus.
NamingSystem/GMDN	http://www.gmdnagency.com/
NamingSystem/v3-DCM	Coded concepts defined in PS 3.16 Digital Imaging and Communications in Medicine (DICOM): Part 16: Content Mapping Resource, Annex D: DICOM Controlled Terminology Definition
NamingSystem/soc	The Standard Occupational Classification (SOC) system is used by Federal statistical agencies to classify workers into occupational categories for the purpose of collecting, calculating, or disseminating data. All workers are classified into one of over 820 occupations according to their occupational definition. To facilitate classification, occupations are combined to form 23 major groups, 96 minor groups, and 449 broad occupations. Each broad occupation includes detailed occupation(s) requiring similar job duties, skills, education, or experience. This code system replaced the older FIPSPUB92, which was withdrawn in February 2005.
NamingSystem/icpc-NOR	The International Classification of Primary Care (ICPC). Norwegian Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/DEEDS408	Code for Acuity Assessment
NamingSystem/icpc-SWE	The International Classification of Primary Care (ICPC). Swedish Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/W1-W2	WHO rec\# drug codes
NamingSystem/epsg-ca	**Description:**The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.
NamingSystem/iso3166-1edition2alpha3	Identifies the coding system published in the ISO 3166-1 Standard for Country codes, 2nd edition, 3-character alphabetic codes.
NamingSystem/FDDX	First DataBank Diagnostic Codes
NamingSystem/v3-WC	WHO ATC
NamingSystem/v3-nuccProviderCodes	The Provider Taxonomy Code List is published (released) twice a year on July 1st and January 1st. The July publication is effective for use on October 1st and the January publication is effective for use on April 1st. The time between the publication release and the effective date is considered an implementation period to allow providers, payers and vendors an opportunity to incorporate any changes into their systems. This listing includes Active codes approved for use effective April 1st, 2003, version 3.0; and codes that are New and approved for use effective October 1st, 2003, version 3.1. It was identified that there is an IP licensure issue with the republishing of the content for this code system by HL7, so the content was removed as of the July 2016 Harmonization cycle release. This external code system content may be accessed from the web page located at http://www.nucc.org/index.php/code-sets-mainmenu-41/provider-taxonomy-mainmenu-40. Multiple formats and means of accessing the content are available from this page.
NamingSystem/DEEDS424	Respiratory rate special circumstances codes
NamingSystem/DEEDS418	Systolic blood pressure special situation
NamingSystem/SNT	SNOMED topology codes (anatomic sites)
NamingSystem/opinions	**Description:** Codes to identify products and services that do not have DIN's and which need to be billed. http://www.atlanticpharmaceutical.ca/default.asp?mn=5.23
NamingSystem/pnds	The PNDS provides standardized terms and codes for patient problems/nursing diagnoses, nursing interventions including actual or expected (goal) outcomes. The PNDS provides standardized terms and codes for nursing diagnoses (a subset of NANDA), nursing interventions and outcomes. The outcomes and interventions are in a relational database. The PNDS intervention and outcome statements are attached in an Access Database. The NANDA diagnoses in the PNDS have already been registered by HL7.
NamingSystem/v3-ucum	Unified Code for Units of Measure
NamingSystem/CST	COSTART
NamingSystem/iso639-2ret	Codes for the Representation of Names of Languages Part 2: Alpha-3 Code. Used as part of the IETF 3066 specification for languages throughout the HL7 specification. *DeprecationComment:* This code system is being deprecated, as the OID identifying it has been replaced with the correct ISO OID of 1.0.639.2
NamingSystem/icpc-BAQ	The International Classification of Primary Care (ICPC). Basque Translation. Denmark: World Organisation of Family Doctors, 1993.
NamingSystem/gtin	The GS1 GTIN is a globally unique identifier of trade items. A trade item is any item (product or service) upon which there is a need to retrieve pre-defined information and that may be priced, or ordered, or invoiced at any point in any supply chain.
NamingSystem/euclides	EUCLIDES
NamingSystem/mdr	MedDRA is a five-level hierarchy of terms. MedDRA was developed as an ICH initiative and is maintained and distributed by the MedDRA Maintenance and Support Services Organization (MSSO). Versions - Versions are released twice per year and are identified by 2 numbers separated by a decimal point (e.g., 7.0, 7.1, 8.0, and 8.1). .0 releases may contain changes to the hierarchy. .1 releases will only contain additions, moves, and modifications of medical concept terms (Preferred Terms) and coding level terms (Lowest Level Terms). Concepts - Concepts are represented by a MedDRA code and a MedDRA term name. The MedDRA code is an eight digit numeric code. MedDRA codes are unique and are never reused. The MedDRA term name is a 100 character alphanumeric field used to describe the concept or term. Hierarchies - MedDRA is structured as a five level hierarchy. System Organ Classes (SOCs) are the broadest terms (e.g., Cardiac disorders, Investigations). The lowest level of the terminology is the Lowest Level Term (LLT) level. There are 26 SOCs and over 60,000 LLTs
NamingSystem/MDREA	Medical Dictionary for Regulatory Activities Terminology (MedDRA), American English Equivalents with expanded abbreviations, Version 7.0. Bethesda, MD: National Library of Medicine, March 1, 2004.
NamingSystem/multum	Broadly, the fields and values in the Multum Lexicon and the VantageRx Database are intended to be available for use in any HL7 message that includes a reference to non-veterinary drug products or active ingredients that are either approved for sale by the FDA or readily available in the United States. The following inter-related definitions recently circulated by us to the HL7 Vocabulary Technical Committee explain the scope of what we mean by "drug product" and "active ingredient". (A definition for "drug ingredient" is also provided here because the definition of "active ingredient" is reliant on this term.) Drug Product A drug product is a manufactured or extemporaneously-compounded physiologically-active material intended by the preparer to achieve therapeutic, diagnostic, or preventative effects via biochemical mechanisms when applied to an epithelial surface or placed in an internal body space of a targeted organism. Drug Ingredient A drug ingredient is a chemical compound or biologic agent that occurs in a drug product. Active Ingredient An active ingredient is a drug ingredient that mediates one or more of the intended therapeutic, diagnostic, or preventative effects of a drug product and is present in sufficient quantities to achieve such effects according to the allopathic tradition of healthcare practice.
NamingSystem/W4	WHO rec\# code with ASTM extension
NamingSystem/iso3166-1edition2	This OID identifies the coding system published in the ISO 3166-1 Standard for Country codes. It contains 3 sets of synonyms for the country codes: 2-character alphabetic, 3-character alphabetic, and numeric. Note that this is the 2nd edition of the standard.
NamingSystem/ahfs	**Description:** The AHFS Pharmacologic-Therapeutic Classification has been in use in hospitals in the United States since its inception in 1959. An integral part of the American Hospital Formulary Service, the AHFS classification allows the grouping of drugs with similar pharmacologic, therapeutic, and/or chemical characteristics. Today, the AHFS classification is used by many people outside of hospitals.
NamingSystem/DEEDS427	Patient temperature route
NamingSystem/CE	CEN ECG diagnostic codes
NamingSystem/GCDF	GCDF Dosage Form Code (2-character) a two-character alphanumeric column that represents a dosage form. The dosage form of a generic drug formulation describes the physical presentation of a drug, such as tablet, capsule, or liquid. It may also incorporate the delivery and release mechanism of the drug. A GCDF is associated to each GCN\_SEQNO to identify that component of the generic drug formulation.
NamingSystem/SNM3	SNOMED International
NamingSystem/NHSNSpinalFusionLevel	NHSN Spinal Fusion Level
NamingSystem/nmds	The NMDS is the minimum set of items of information with uniform definitions and categories concerning the specific dimension of the context of patient care delivery. It represents the minimum data used to support the management and administration of patient/nursing care delivery across all types of settings.
NamingSystem/AS4	ASTM E1238/ E1467 Universal
NamingSystem/icd-o	International Classification of Diseases for Oncology)
NamingSystem/noc	NOC - Nursing Outcome Codes
NamingSystem/v3-UnitOfMeasurePrefix	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.
NamingSystem/v3-SpecialArrangement	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.
NamingSystem/v3-ProcedureMethod	Identifies the technique used to perform a procedure.
NamingSystem/v3-policyHolderRole	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.
NamingSystem/v3-PeriodicIntervalOfTimeAbbreviation

Other

These are resources that are used within this implementation guide that don't fit into one of the other categories

FHIR Normative Manifest
V2 Rendering Manifest
FHIR Rendering Manifest
V3 Rendering Manifest
V2 Publishing Manifest
Retired Manifest
Unified Rendering Manifest
CDA Rendering Manifest
External Rendering Manifest
Bundle/hxutg1-1-0-4
Bundle/hxutg1-1-0-1
Bundle/hxutg1-1-0-0
Bundle/hxutg1-1-0-3
Bundle/hxutg1-1-0-2
Bundle/hxutg1-1-0-5