This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Code systems used in HL7 standards.
<ValueSet xmlns="http://hl7.org/fhir"> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p>Release Date: 2014-08-07</p> <h2>Description</h2> <p> Code systems used in HL7 standards. <br/> </p> <hr/> <table class="grid"> <tr> <td> <b>Level</b> </td> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> </tr> <tr> <td>1</td> <td>ABCcodes <a name="ABCcodes"> </a> </td> <td>ABCcodes</td> <td> 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. . <br/> </td> </tr> <tr> <td>1</td> <td>AcknowledgementCondition <a name="AcknowledgementCondition"> </a> </td> <td>AcknowledgementCondition</td> <td/> </tr> <tr> <td>1</td> <td>AcknowledgementDetailCode <a name="AcknowledgementDetailCode"> </a> </td> <td>AcknowledgementDetailCode</td> <td> A site specific problem code <br/> </td> </tr> <tr> <td>1</td> <td>AcknowledgementDetailType <a name="AcknowledgementDetailType"> </a> </td> <td>Acknowledgement Detail Type</td> <td/> </tr> <tr> <td>1</td> <td>AcknowledgementType <a name="AcknowledgementType"> </a> </td> <td>AcknowledgementType</td> <td> Acknowledgement code as described in HL7 message processing rules. <br/> </td> </tr> <tr> <td>1</td> <td>ACR <a name="ACR"> </a> </td> <td>American College of Radiology finding codes</td> <td> Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA. <br/> </td> </tr> <tr> <td>1</td> <td>ActClass <a name="ActClass"> </a> </td> <td>ActClass</td> <td/> </tr> <tr> <td>1</td> <td>ActCode <a name="ActCode"> </a> </td> <td>ActCode</td> <td> The table that provides the detailed or rich codes for the Act classes. <br/> </td> </tr> <tr> <td>1</td> <td>ActExposureLevelCode <a name="ActExposureLevelCode"> </a> </td> <td>ActExposureLevelCode</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>ActInvoiceElementModifier <a name="ActInvoiceElementModifier"> </a> </td> <td>ActInvoiceElementModifier</td> <td> Processing consideration and clarification codes. <br/> </td> </tr> <tr> <td>1</td> <td>ActMood <a name="ActMood"> </a> </td> <td>ActMood</td> <td/> </tr> <tr> <td>1</td> <td>ActPriority <a name="ActPriority"> </a> </td> <td>ActPriority</td> <td/> </tr> <tr> <td>1</td> <td>ActReason <a name="ActReason"> </a> </td> <td>ActReason</td> <td/> </tr> <tr> <td>1</td> <td>ActRelationshipCheckpoint <a name="ActRelationshipCheckpoint"> </a> </td> <td>ActRelationshipCheckpoint</td> <td/> </tr> <tr> <td>1</td> <td>ActRelationshipJoin <a name="ActRelationshipJoin"> </a> </td> <td>ActRelationshipJoin</td> <td/> </tr> <tr> <td>1</td> <td>ActRelationshipSplit <a name="ActRelationshipSplit"> </a> </td> <td>ActRelationshipSplit</td> <td/> </tr> <tr> <td>1</td> <td>ActRelationshipSubset <a name="ActRelationshipSubset"> </a> </td> <td>ActRelationshipSubset</td> <td> Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets. <br/> 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. <br/> </td> </tr> <tr> <td>1</td> <td>ActRelationshipType <a name="ActRelationshipType"> </a> </td> <td>ActRelationshipType</td> <td> The source is an excerpt from the target. <br/> </td> </tr> <tr> <td>1</td> <td>ActSite <a name="ActSite"> </a> </td> <td>ActSite</td> <td> An anatomical location on an organism which can be the focus of an act. <br/> </td> </tr> <tr> <td>1</td> <td>ActStatus <a name="ActStatus"> </a> </td> <td>ActStatus</td> <td> Contains the names (codes) for each of the states in the state-machine of the RIM Act class. <br/> </td> </tr> <tr> <td>1</td> <td>ActUncertainty <a name="ActUncertainty"> </a> </td> <td>ActUncertainty</td> <td/> </tr> <tr> <td>1</td> <td>ActUSPrivacyLaw <a name="ActUSPrivacyLaw"> </a> </td> <td>Act US Privacy Law</td> <td> Description: A jurisdictional mandate in the US relating to privacy. <br/> </td> </tr> <tr> <td>1</td> <td>AddressPartType <a name="AddressPartType"> </a> </td> <td>AddressPartType</td> <td> Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line" <br/> </td> </tr> <tr> <td>1</td> <td>AddressUse <a name="AddressUse"> </a> </td> <td>AddressUse</td> <td> Description: Uses of Addresses. Lloyd to supply more complete description. <br/> </td> </tr> <tr> <td>1</td> <td>AdministrativeGender <a name="AdministrativeGender"> </a> </td> <td>AdministrativeGender</td> <td> The gender of a person used for adminstrative purposes (as opposed to clinical gender) <br/> </td> </tr> <tr> <td>1</td> <td>AHFS <a name="AHFS"> </a> </td> <td>AHFS Pharmacologic-Therapeutic Classification</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>AmericanIndianAlaskaNativeLanguages <a name="AmericanIndianAlaskaNativeLanguages"> </a> </td> <td>AmericanIndianAlaskaNativeLanguages</td> <td> American Indian and Alaska Native languages currently being used in the United States. <br/> </td> </tr> <tr> <td>1</td> <td>ART <a name="ART"> </a> </td> <td>WHO Adverse Reaction Terms</td> <td> WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden. <br/> </td> </tr> <tr> <td>1</td> <td>AS4 <a name="AS4"> </a> </td> <td>ASTM E1238/ E1467 Universal</td> <td> American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467). <br/> </td> </tr> <tr> <td>1</td> <td>AS4E <a name="AS4E"> </a> </td> <td>AS4 Neurophysiology Codes</td> <td> ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2. <br/> </td> </tr> <tr> <td>1</td> <td>ATC <a name="ATC"> </a> </td> <td>American Type Culture Collection</td> <td> Reference cultures (microorganisms, tissue cultures, etc.), related biological materials and associated data. American Type Culture Collection, 12301 Parklawn Dr, Rockville MD, 20852. (301) 881-2600. http://www.atcc.org <br/> </td> </tr> <tr> <td>1</td> <td>BindingRealm <a name="BindingRealm"> </a> </td> <td>BindingRealm</td> <td> Description: Coded concepts representing the Binding Realms used for Context Binding of terminology in HL7 models. Where concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the codes. For those realms where they do not,. codes are created for the concepts. These codes are generally carried in InfrastructureRoot.realmcode, and are used in Context Binding statements. <br/> </td> </tr> <tr> <td>1</td> <td>BodySite <a name="BodySite"> </a> </td> <td>HL7 table 0163 - Body site</td> <td> Description: HL7 version 2.x Body site used in chapter(s) 4; HL7 table 0163 <br/> </td> </tr> <tr> <td>1</td> <td>C4 <a name="C4"> </a> </td> <td>CPT-4</td> <td> American Medical Association, P.O. Box 10946, Chicago IL 60610. <br/> </td> </tr> <tr> <td>1</td> <td>C5 <a name="C5"> </a> </td> <td>CPT-5</td> <td> American Medical Association, P.O. Box 10946, Chicago IL 60610. <br/> </td> </tr> <tr> <td>1</td> <td>Calendar <a name="Calendar"> </a> </td> <td>Calendar</td> <td/> </tr> <tr> <td>1</td> <td>CalendarCycle <a name="CalendarCycle"> </a> </td> <td>CalendarCycle</td> <td/> </tr> <tr> <td>1</td> <td>CalendarType <a name="CalendarType"> </a> </td> <td>CalendarType</td> <td/> </tr> <tr> <td>1</td> <td>CAMNCVS <a name="CAMNCVS"> </a> </td> <td>CAMNCVS</td> <td> CAM & Nursing Coding Vocabulary Set <br/> </td> </tr> <tr> <td>1</td> <td>CAS <a name="CAS"> </a> </td> <td>Chemical abstract codes</td> <td> These include unique codes for each unique chemical, including all generic drugs. The codes do not distinguish among different dosing forms. When multiple equivalent CAS numbers exist, use the first one listed in USAN. USAN 1990 and the USP dictionary of drug names, William M. Heller, Ph.D., Executive Editor, United States Pharmacopeial Convention, Inc., 12601 Twinbrook Parkway, Rockville, MD 20852. <br/> </td> </tr> <tr> <td>1</td> <td>CCI <a name="CCI"> </a> </td> <td>Canadian Classification of Health Interventions</td> <td> CCI - Canadian Classification of Health Interventions, developed to accompany ICD-10-CA, maintained by CIHI (Canadian Institute for Health Information). <br/> 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 <br/> CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 <br/> Phone: (416) 481.2002 Fax: (416) 481-2950 <br/> www.cihi.ca <br/> </td> </tr> <tr> <td>1</td> <td>CD2 <a name="CD2"> </a> </td> <td>CDT-2 Codes</td> <td> American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611. <br/> </td> </tr> <tr> <td>1</td> <td>CDCA <a name="CDCA"> </a> </td> <td>CDC Analyte Codes</td> <td> Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/la boratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA <br/> </td> </tr> <tr> <td>1</td> <td>CDCM <a name="CDCM"> </a> </td> <td>CDC Methods/Instruments Codes</td> <td> Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/la boratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA <br/> </td> </tr> <tr> <td>1</td> <td>CDS <a name="CDS"> </a> </td> <td>CDC Surveillance</td> <td> CDC Surveillance Codes. For data unique to specific public health surveillance requirements. Epidemiology Program Office, Centers for Disease Control and Prevention, 1600 Clifton Rd, Atlanta, GA, 30333. (404) 639-3661. <br/> </td> </tr> <tr> <td>1</td> <td>CE <a name="CE"> </a> </td> <td>CEN ECG diagnostic codes</td> <td> CEN PT007. A quite comprehensive set of ECG diagnostic codes (abbreviations) and descriptions published as a pre-standard by CEN TC251. Available from CEN TC251 secretariat, c/o Georges DeMoor, State University Hospital Gent, De Pintelaan 185-5K3, 9000 Ge <br/> </td> </tr> <tr> <td>1</td> <td>Charset <a name="Charset"> </a> </td> <td>Charset</td> <td> Internet Assigned Numbers Authority (IANA) Charset Types <br/> </td> </tr> <tr> <td>1</td> <td>CLP <a name="CLP"> </a> </td> <td>CLIP</td> <td> Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports. <br/> </td> </tr> <tr> <td>1</td> <td>CodeSystem <a name="CodeSystem"> </a> </td> <td>CodeSystem</td> <td> Code systems used in HL7 standards. <br/> </td> </tr> <tr> <td>1</td> <td>CodeSystemType <a name="CodeSystemType"> </a> </td> <td>HL7 Code System Type</td> <td/> </tr> <tr> <td>1</td> <td>CodingRationale <a name="CodingRationale"> </a> </td> <td>CodingRationale</td> <td> 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: <br/> SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) <br/> 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. <br/> </td> </tr> <tr> <td>1</td> <td>CommunicationFunctionType <a name="CommunicationFunctionType"> </a> </td> <td>CommunicationFunctionType</td> <td> Describes the type of communication function that the associated entity plays in the associated transmission. <br/> </td> </tr> <tr> <td>1</td> <td>CompressionAlgorithm <a name="CompressionAlgorithm"> </a> </td> <td>CompressionAlgorithm</td> <td/> </tr> <tr> <td>1</td> <td>ConceptCodeRelationship <a name="ConceptCodeRelationship"> </a> </td> <td>Possible Concept Code Relationships</td> <td/> </tr> <tr> <td>1</td> <td>ConceptGenerality <a name="ConceptGenerality"> </a> </td> <td>ConceptGenerality</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>ConceptProperty <a name="ConceptProperty"> </a> </td> <td>HL7 Value Set and Coded Concept Property Codes</td> <td/> </tr> <tr> <td>1</td> <td>ConceptStatus <a name="ConceptStatus"> </a> </td> <td>HL7 Coded Concept Status</td> <td/> </tr> <tr> <td>1</td> <td>Confidentiality <a name="Confidentiality"> </a> </td> <td>Confidentiality</td> <td/> </tr> <tr> <td>1</td> <td>ContainerCap <a name="ContainerCap"> </a> </td> <td>ContainerCap</td> <td> The type of cap associated with a container <br/> </td> </tr> <tr> <td>1</td> <td>ContainerSeparator <a name="ContainerSeparator"> </a> </td> <td>ContainerSeparator</td> <td> A material in a blood collection container that facilites the separation of of blood cells from serum or plasma <br/> </td> </tr> <tr> <td>1</td> <td>ContentProcessingMode <a name="ContentProcessingMode"> </a> </td> <td>ContentProcessingMode</td> <td> Description:Identifies the order in which content should be processed. <br/> </td> </tr> <tr> <td>1</td> <td>ContextConductionStyle <a name="ContextConductionStyle"> </a> </td> <td>ContextConductionStyle</td> <td>The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.</td> </tr> <tr> <td>1</td> <td>ContextControl <a name="ContextControl"> </a> </td> <td>ContextControl</td> <td> This table contains the control codes that are used to manage the propagation and scope of a particular ActRelationship or Participation within a set of Acts. <br/> </td> </tr> <tr> <td>1</td> <td>CSAID <a name="CSAID"> </a> </td> <td>CAN/CSA-Z795-96 (R2001)</td> <td> CAN/CSA-Z795-96 (R2001) - This Standard provides a framework for consistent recording and classification of information on work-related injuries and diseases in Canada (injury coding). <br/> It is constituted of Nature of injury, body part, side of body. For example: Cut or laceration of the Upper Arm, Left Injury = 03400; body part = 31100; side of body = L <br/> Code set is maintained by the Canadian Standards Association (CSA). <br/> The Canadian Standards Association 5060 Spectrum Way Mississauga, Ontario Canada L4W 5N6 <br/> Phone: (416) 747-4000 1-800-463-6727 Fax: (416) 747-2473 <br/> </td> </tr> <tr> <td>1</td> <td>CST <a name="CST"> </a> </td> <td>COSTART</td> <td> International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD. <br/> </td> </tr> <tr> <td>1</td> <td>Currency <a name="Currency"> </a> </td> <td>Currency</td> <td> The currency unit as defined in ISO 4217 <br/> </td> </tr> <tr> <td>1</td> <td>CVX <a name="CVX"> </a> </td> <td>CDC Vaccine Codes</td> <td> National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333 <br/> </td> </tr> <tr> <td>1</td> <td>DataOperation <a name="DataOperation"> </a> </td> <td>DataOperation</td> <td/> </tr> <tr> <td>1</td> <td>DataType <a name="DataType"> </a> </td> <td>DataType</td> <td/> </tr> <tr> <td>1</td> <td>DCL <a name="DCL"> </a> </td> <td>DICOM Class Label</td> <td> From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034 <br/> </td> </tr> <tr> <td>1</td> <td>DCM <a name="DCM"> </a> </td> <td>DICOM modality codes</td> <td> Dean Bidgood, MD; Duke University Medical Center, Durham NC. Digital Imaging and Communications in Medicine (DICOM). From NEMA Publications PS-3.1 - PS 3.12: The ACR-NEMA DICOM Standard. National Electrical Manufacturers Association (NEMA). Rosslyn, VA, <br/> </td> </tr> <tr> <td>1</td> <td>Dentition <a name="Dentition"> </a> </td> <td>Dentition</td> <td/> </tr> <tr> <td>1</td> <td>DeviceAlertLevel <a name="DeviceAlertLevel"> </a> </td> <td>DeviceAlertLevel</td> <td> Domain values for the Device.Alert_levelCode <br/> </td> </tr> <tr> <td>1</td> <td>DocumentCompletion <a name="DocumentCompletion"> </a> </td> <td>DocumentCompletion</td> <td> Identifies the current completion state of a clinical document. <br/> </td> </tr> <tr> <td>1</td> <td>DocumentStorage <a name="DocumentStorage"> </a> </td> <td>DocumentStorage</td> <td> Identifies the storage status of a document. <br/> </td> </tr> <tr> <td>1</td> <td>DQL <a name="DQL"> </a> </td> <td>DICOM Query Label</td> <td> HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI. <br/> </td> </tr> <tr> <td>1</td> <td>E <a name="E"> </a> </td> <td>EUCLIDES</td> <td> Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. <br/> </td> </tr> <tr> <td>1</td> <td>E5 <a name="E5"> </a> </td> <td>Euclides quantity codes</td> <td> Available from Euclides Foundation International nv (see above) <br/> </td> </tr> <tr> <td>1</td> <td>E6 <a name="E6"> </a> </td> <td>Euclides Lab method codes</td> <td> Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. <br/> </td> </tr> <tr> <td>1</td> <td>E7 <a name="E7"> </a> </td> <td>Euclides Lab equipment codes</td> <td> Available from Euclides Foundation International nv (see above) <br/> </td> </tr> <tr> <td>1</td> <td>EditStatus <a name="EditStatus"> </a> </td> <td>EditStatus</td> <td> The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database. <br/> </td> </tr> <tr> <td>1</td> <td>EducationLevel <a name="EducationLevel"> </a> </td> <td>Education Level</td> <td> Years of education that a person has completed <br/> </td> </tr> <tr> <td>1</td> <td>EmployeeJobClass <a name="EmployeeJobClass"> </a> </td> <td>EmployeeJobClass</td> <td/> </tr> <tr> <td>1</td> <td>EncounterAccident <a name="EncounterAccident"> </a> </td> <td>EncounterAccident</td> <td/> </tr> <tr> <td>1</td> <td>EncounterAcuity <a name="EncounterAcuity"> </a> </td> <td>Encounter Acuity</td> <td> The level of resource intensiveness of patient care. <br/> </td> </tr> <tr> <td>1</td> <td>EncounterAdmissionSource <a name="EncounterAdmissionSource"> </a> </td> <td>EncounterAdmissionSource</td> <td/> </tr> <tr> <td>1</td> <td>EncounterReferralSource <a name="EncounterReferralSource"> </a> </td> <td>EncounterReferralSource</td> <td> This domain is defined in UB92 and applies to US realm only <br/> </td> </tr> <tr> <td>1</td> <td>EncounterSpecialCourtesy <a name="EncounterSpecialCourtesy"> </a> </td> <td>EncounterSpecialCourtesy</td> <td/> </tr> <tr> <td>1</td> <td>EntityClass <a name="EntityClass"> </a> </td> <td>EntityClass</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EntityCode <a name="EntityCode"> </a> </td> <td>EntityCode</td> <td/> </tr> <tr> <td>1</td> <td>EntityDeterminer <a name="EntityDeterminer"> </a> </td> <td>EntityDeterminer</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EntityHandling <a name="EntityHandling"> </a> </td> <td>EntityHandling</td> <td/> </tr> <tr> <td>1</td> <td>EntityNamePartQualifier <a name="EntityNamePartQualifier"> </a> </td> <td>EntityNamePartQualifier</td> <td/> </tr> <tr> <td>1</td> <td>EntityNamePartQualifierR2 <a name="EntityNamePartQualifierR2"> </a> </td> <td>EntityNamePartQualifierR2</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EntityNamePartType <a name="EntityNamePartType"> </a> </td> <td>EntityNamePartType</td> <td/> </tr> <tr> <td>1</td> <td>EntityNamePartTypeR2 <a name="EntityNamePartTypeR2"> </a> </td> <td>EntityNamePartTypeR2</td> <td> Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc. <br/> </td> </tr> <tr> <td>1</td> <td>EntityNameUse <a name="EntityNameUse"> </a> </td> <td>EntityNameUse</td> <td/> </tr> <tr> <td>1</td> <td>EntityNameUseR2 <a name="EntityNameUseR2"> </a> </td> <td>EntityNameUseR2</td> <td> Description:A set of codes advising a system or user which name in a set of names to select for a given purpose. <br/> </td> </tr> <tr> <td>1</td> <td>EntityRisk <a name="EntityRisk"> </a> </td> <td>EntityRisk</td> <td> The vocabulary table for the Entity.riskCode attribute <br/> </td> </tr> <tr> <td>1</td> <td>EntityStatus <a name="EntityStatus"> </a> </td> <td>EntityStatus</td> <td> The status of an instance of the RIM Entity class. <br/> </td> </tr> <tr> <td>1</td> <td>ENZC <a name="ENZC"> </a> </td> <td>Enzyme Codes</td> <td> Enzyme Committee of the International Union of Biochemistry and Molecular Biology. Enzyme Nomenclature: Recommendations on the Nomenclature and Classification of Enzyme-Catalysed Reactions. London: Academic Press, 1992. <br/> </td> </tr> <tr> <td>1</td> <td>EPSG_CA <a name="EPSG_CA"> </a> </td> <td>European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EPSG_CRS <a name="EPSG_CRS"> </a> </td> <td>European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EPSG-GeodeticParameterDataset <a name="EPSG-GeodeticParameterDataset"> </a> </td> <td>EPSG Geodetic Parameter Dataset</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>EquipmentAlertLevel <a name="EquipmentAlertLevel"> </a> </td> <td>EquipmentAlertLevel</td> <td/> </tr> <tr> <td>1</td> <td>Ethnicity <a name="Ethnicity"> </a> </td> <td>Ethnicity</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>ExposureMode <a name="ExposureMode"> </a> </td> <td>ExposureMode</td> <td> Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure. <br/> </td> </tr> <tr> <td>1</td> <td>FDDC <a name="FDDC"> </a> </td> <td>First DataBank Drug Codes</td> <td> National Drug Data File. Proprietary product of First DataBank, Inc. (800) 633-3453, or http://www.firstdatabank.com. <br/> </td> </tr> <tr> <td>1</td> <td>FDDX <a name="FDDX"> </a> </td> <td>First DataBank Diagnostic Codes</td> <td> Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC. <br/> </td> </tr> <tr> <td>1</td> <td>FDK <a name="FDK"> </a> </td> <td>FDA K10</td> <td> Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes). <br/> </td> </tr> <tr> <td>1</td> <td>GenderStatus <a name="GenderStatus"> </a> </td> <td>GenderStatus</td> <td/> </tr> <tr> <td>1</td> <td>GTSAbbreviation <a name="GTSAbbreviation"> </a> </td> <td>GTSAbbreviation</td> <td/> </tr> <tr> <td>1</td> <td>HB <a name="HB"> </a> </td> <td>HIBCC</td> <td> Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018. <br/> </td> </tr> <tr> <td>1</td> <td>HC-AIC <a name="HC-AIC"> </a> </td> <td>Active Ingredient Code</td> <td> Description: <br/> 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 <br/> </td> </tr> <tr> <td>1</td> <td>HC-AIGC <a name="HC-AIGC"> </a> </td> <td>Active Ingredient Group Code</td> <td> 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/p rodpharma/databasdon/index_e.html <br/> </td> </tr> <tr> <td>1</td> <td>HC-AIGN <a name="HC-AIGN"> </a> </td> <td>Active Ingredient Group Number</td> <td> 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 <br/> </td> </tr> <tr> <td>1</td> <td>HC-DIN <a name="HC-DIN"> </a> </td> <td>Health Canada Drug Id Number</td> <td> 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 <br/> </td> </tr> <tr> <td>1</td> <td>HC-NPN <a name="HC-NPN"> </a> </td> <td>Health Canada Natural Product Number</td> <td> Description: 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/p rodnatur/applications/licen-prod/lnhpd-bdpsnh-eng.php <br/> </td> </tr> <tr> <td>1</td> <td>HealthcareProviderTaxonomyHIPAA <a name="HealthcareProviderTaxonomyHIPAA"> </a> </td> <td>HealthcareProviderTaxonomyHIPAA</td> <td/> </tr> <tr> <td>1</td> <td>HealthcareServiceLocation <a name="HealthcareServiceLocation"> </a> </td> <td>Healthcare Service Location</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>HHC <a name="HHC"> </a> </td> <td>Home Health Care</td> <td> Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC. <br/> </td> </tr> <tr> <td>1</td> <td>HI <a name="HI"> </a> </td> <td>Health Outcomes</td> <td> Health Outcomes Institute codes for outcome variables available (with responses) from Stratis Health (formerly Foundation for Health Care Evaluation and Health Outcomes Institute), 2901 Metro Drive, Suite 400, Bloomington, MN, 55425-1525; (612) 854-3306 (voice); (612) 853-8503 (fax); dziegen@winternet.com. See examples in the Implementation Guide. <br/> </td> </tr> <tr> <td>1</td> <td>hl7ApprovalStatus <a name="hl7ApprovalStatus"> </a> </td> <td>HL7ApprovalStatus</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>hl7CMETAttribution <a name="hl7CMETAttribution"> </a> </td> <td>HL7CMETAttribution</td> <td/> </tr> <tr> <td>1</td> <td>HL7CommitteeIDInRIM <a name="HL7CommitteeIDInRIM"> </a> </td> <td>HL7CommitteeIDInRIM</td> <td> Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables. <br/> </td> </tr> <tr> <td>1</td> <td>HL7ConformanceInclusion <a name="HL7ConformanceInclusion"> </a> </td> <td>HL7ConformanceInclusion</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>HL7DefinedRoseProperty <a name="HL7DefinedRoseProperty"> </a> </td> <td>HL7DefinedRoseProperty</td> <td> The property Ids that HL7 has defined for customizing Rational Rose. <br/> </td> </tr> <tr> <td>1</td> <td>hl7ITSType <a name="hl7ITSType"> </a> </td> <td>HL7ITSType</td> <td> Description: Codes identifying types of HL7 Implementation Technology Specifications <br/> </td> </tr> <tr> <td>1</td> <td>HL7ITSVersionCode <a name="HL7ITSVersionCode"> </a> </td> <td>HL7 ITS Version Code</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>hl7PublishingDomain <a name="hl7PublishingDomain"> </a> </td> <td>HL7PublishingDomain</td> <td> Description: Codes for HL7 publishing 'domain's (specific content area) <br/> </td> </tr> <tr> <td>1</td> <td>hl7PublishingSection <a name="hl7PublishingSection"> </a> </td> <td>HL7PublishingSection</td> <td> Description: Codes for HL7 publishing 'section's (major business categories) <br/> </td> </tr> <tr> <td>1</td> <td>hl7PublishingSubSection <a name="hl7PublishingSubSection"> </a> </td> <td>HL7PublishingSubSection</td> <td> Description: Codes for HL7 publishing 'sub-section's (business sub-categories) <br/> </td> </tr> <tr> <td>1</td> <td>HL7StandardVersionCode <a name="HL7StandardVersionCode"> </a> </td> <td>HL7StandardVersionCode</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>HL7UpdateMode <a name="HL7UpdateMode"> </a> </td> <td>HL7UpdateMode</td> <td> The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute. <br/> </td> </tr> <tr> <td>1</td> <td>hl7V3Conformance <a name="hl7V3Conformance"> </a> </td> <td>HL7V3Conformance</td> <td> Description: Identifies allowed codes for HL7aTMs v3 conformance property. <br/> </td> </tr> <tr> <td>1</td> <td>hl7VoteResolution <a name="hl7VoteResolution"> </a> </td> <td>HL7VoteResolution</td> <td> Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM). <br/> </td> </tr> <tr> <td>1</td> <td>HPC <a name="HPC"> </a> </td> <td>HCFA Procedure Codes (HCPCS)</td> <td> Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) modifiers. <br/> </td> </tr> <tr> <td>1</td> <td>HtmlLinkType <a name="HtmlLinkType"> </a> </td> <td>HtmlLinkType</td> <td> 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 <br/> </td> </tr> <tr> <td>1</td> <td>I10 <a name="I10"> </a> </td> <td>ICD-10</td> <td> World Health Publications, Albany, NY. <br/> </td> </tr> <tr> <td>1</td> <td>I10P <a name="I10P"> </a> </td> <td>ICD-10 Procedure Codes</td> <td> Procedure Coding System (ICD-10-PCS). See http://www/hcfa.gov/stats/icd10.i cd10.htm for more information. <br/> </td> </tr> <tr> <td>1</td> <td>I9 <a name="I9"> </a> </td> <td>ICD9</td> <td> World Health Publications, Albany, NY. <br/> </td> </tr> <tr> <td>1</td> <td>I9C <a name="I9C"> </a> </td> <td>ICD-9CM</td> <td> Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests). <br/> </td> </tr> <tr> <td>1</td> <td>IBT <a name="IBT"> </a> </td> <td>ISBT</td> <td> International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169. <br/> </td> </tr> <tr> <td>1</td> <td>IC2 <a name="IC2"> </a> </td> <td>ICHPPC-2</td> <td> International Classification of Health Problems in Primary Care, Classification Committee of World Organization of National Colleges, Academies and Academic Associations of General Practitioners (WONCA), 3rd edition. An adaptation of ICD9 intended for use in General Medicine, Oxford University Press. <br/> </td> </tr> <tr> <td>1</td> <td>ICD-10-CA <a name="ICD-10-CA"> </a> </td> <td>CanadianDiagnosisCodesICD-10-CA</td> <td> 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. <br/> For example: <br/> L40 Psoriasis <br/> L40.0 Psoriasis vulgaris <br/> Nummular psoriasis <br/> Plaque psoriasis <br/> L40.1 Generalized pustular psoriasis <br/> Impetigo herpetiformis <br/> Von ZumbuschaTMs disease <br/> L40.2 Acrodermatitis continua <br/> L40.3 Pustulosis palmaris et plantaris <br/> L40.4 Guttate psoriasis <br/> L40.5* Arthropathic psoriasis (M07.0-M07.3*)(M09.0*) <br/> L40.8 Other psoriasis <br/> Erythroderma psoraticum <br/> Erythrodermic psoriasis <br/> Flexural psoriasis <br/> L40.9 Psoriasis unspecified <br/> They are maintained by CIHI (Canadian Institute for Health Information). <br/> CIHI Toronto <br/> Attn: Director of Standards <br/> 90 Eglinton Avenue, Suite 300 <br/> Toronto, Ontario <br/> Canada <br/> M4P 2Y3 <br/> Phone: (416) 481.2002 <br/> Fax: (416) 481-2950 <br/> www.cihi.ca <br/> </td> </tr> <tr> <td>1</td> <td>ICDO <a name="ICDO"> </a> </td> <td>International Classification of Diseases for Oncology</td> <td> International Classification of Diseases for Oncology, 2nd Edition. World Health Organization: Geneva, Switzerland, 1990. Order from: College of American Pathologists, 325 Waukegan Road, Northfield, IL, 60093-2750. (847) 446-8800. <br/> </td> </tr> <tr> <td>1</td> <td>ICS <a name="ICS"> </a> </td> <td>ICCS</td> <td> Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105. <br/> </td> </tr> <tr> <td>1</td> <td>ICSD <a name="ICSD"> </a> </td> <td>International Classification of Sleep Disorders</td> <td> International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902 <br/> </td> </tr> <tr> <td>1</td> <td>IdentifierReliability <a name="IdentifierReliability"> </a> </td> <td>IdentifierReliability</td> <td> Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms. <br/> </td> </tr> <tr> <td>1</td> <td>IdentifierScope <a name="IdentifierScope"> </a> </td> <td>IdentifierScope</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>IETF1766 <a name="IETF1766"> </a> </td> <td>IETF RFC 1766</td> <td> Language identifiers as defined by IETF RFC 1766: Tags for the Identification of Languages, or its successor on the IETF Standards Track. The biblio ref for RFC 1766 is: IETF (Internet Engineering Task Force), RFC 1766: Tag <br/> </td> </tr> <tr> <td>1</td> <td>IETF3066 <a name="IETF3066"> </a> </td> <td>Tags for the Identification of Languages</td> <td> from OID registry <br/> </td> </tr> <tr> <td>1</td> <td>IntegrityCheckAlgorithm <a name="IntegrityCheckAlgorithm"> </a> </td> <td>IntegrityCheckAlgorithm</td> <td/> </tr> <tr> <td>1</td> <td>iso21000-6-2004E-RDD <a name="iso21000-6-2004E-RDD"> </a> </td> <td>ISO/IEC 21000-6:2004(E) Rights Data Dictionary</td> <td> 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. <br/> 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. <br/> 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. <br/> 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. <br/> 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. <br/> </td> </tr> <tr> <td>1</td> <td>ISO3166-1 <a name="ISO3166-1"> </a> </td> <td>ISO 3166 2 Character Country Codes</td> <td> Two character country codes <br/> </td> </tr> <tr> <td>1</td> <td>ISO3166-2 <a name="ISO3166-2"> </a> </td> <td>ISO 3166 3 Character Country Codes</td> <td> Three character country codes <br/> </td> </tr> <tr> <td>1</td> <td>ISO3166-3 <a name="ISO3166-3"> </a> </td> <td>ISO 3166 Numeric country Codes</td> <td> Numeric country codes <br/> </td> </tr> <tr> <td>1</td> <td>ISO4217 <a name="ISO4217"> </a> </td> <td>ISO4217</td> <td> ISO 4217 currency code <br/> </td> </tr> <tr> <td>1</td> <td>IUPC <a name="IUPC"> </a> </td> <td>IUPAC/IFCC Component Codes</td> <td> Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP. <br/> </td> </tr> <tr> <td>1</td> <td>IUPP <a name="IUPP"> </a> </td> <td>IUPAC/IFCC Property Codes</td> <td> International Union of Pure and Applied Chemistry/International Federation of Clinical Chemistry. The Silver Book: Compendium of terminology and nomenclature of properties in clinical laboratory sciences. Oxford: Blackwell Scientific Publishers, 1995. Henrik Olesen, M.D., D.M.Sc., Chairperson, Department of Clinical Chemistry, KK76.4.2, Rigshospitalet, University Hospital of Copenhagen, DK-2200, Copenhagen. http://inet.uni-c.dk/~qukb76 42/ <br/> </td> </tr> <tr> <td>1</td> <td>JC8 <a name="JC8"> </a> </td> <td>Japanese Chemistry</td> <td> Clinical examination classification code. Japan Association of Clinical Pathology. Version 8, 1990. A multiaxial code including a subject code (e.g., Rubella = 5f395, identification code (e.g., virus ab IGG), a specimen code (e.g., serum =023) and a method code (e.g., ELISA = 022) <br/> </td> </tr> <tr> <td>1</td> <td>LanguageAbilityMode <a name="LanguageAbilityMode"> </a> </td> <td>LanguageAbilityMode</td> <td/> </tr> <tr> <td>1</td> <td>LanguageAbilityProficiency <a name="LanguageAbilityProficiency"> </a> </td> <td>LanguageAbilityProficiency</td> <td/> </tr> <tr> <td>1</td> <td>LivingArrangement <a name="LivingArrangement"> </a> </td> <td>LivingArrangement</td> <td> A code depicting the living arrangements of a person <br/> </td> </tr> <tr> <td>1</td> <td>LN <a name="LN"> </a> </td> <td>Logical Observation Identifier Names and Codes (LOINC)</td> <td> Regenstrief Institute, c/o LOINC, 1050 Wishard Blvd., 5th floor, Indianapolis, IN 46202. 317/630-7433. Available from the Regenstrief Institute server at http://www.regenstrief.org/loinc/loinc.htm. Also available via HL7 file server: FTP/Gopher (www.mcis.duke.edu/standards/ termcode/loinclab and www.mcis.duke.edu/standards/termcode/loinclin) and World Wide Web (http:// www.mcis.duke.edu/ standards/termcode/loincl.htm). January 2000 version has identifiers, synonyms and cross-reference codes for reporting over 26,000 laboratory and related observations and 1,500 clinical measures. <br/> </td> </tr> <tr> <td>1</td> <td>LocalMarkupIgnore <a name="LocalMarkupIgnore"> </a> </td> <td>LocalMarkupIgnore</td> <td> 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" <br/> </td> </tr> <tr> <td>1</td> <td>LocalRemoteControlState <a name="LocalRemoteControlState"> </a> </td> <td>LocalRemoteControlState</td> <td/> </tr> <tr> <td>1</td> <td>ManagedParticipationStatus <a name="ManagedParticipationStatus"> </a> </td> <td>ManagedParticipationStatus</td> <td> The status of an instance of the RIM Participation class. <br/> </td> </tr> <tr> <td>1</td> <td>MapRelationship <a name="MapRelationship"> </a> </td> <td>MapRelationship</td> <td> 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 <br/> </td> </tr> <tr> <td>1</td> <td>MaritalStatus <a name="MaritalStatus"> </a> </td> <td>MaritalStatus</td> <td/> </tr> <tr> <td>1</td> <td>MaterialType <a name="MaterialType"> </a> </td> <td>MaterialType</td> <td/> </tr> <tr> <td>1</td> <td>MDC <a name="MDC"> </a> </td> <td>ISO 11073-10101 Health informatics - Point-of-care</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>MDDX <a name="MDDX"> </a> </td> <td>Medispan Diagnostic Codes</td> <td> Codes Used for drug-diagnosis interaction checking. Proprietary product. Hierarchical drug codes for identifying drugs down to manufacturer and pill size. MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel: (800) 428-4495. WWW: http://www.espan.com/medispan/pages/ medhome.html. As above for MGPI. <br/> </td> </tr> <tr> <td>1</td> <td>MDFAttributeType <a name="MDFAttributeType"> </a> </td> <td>MDFAttributeType</td> <td/> </tr> <tr> <td>1</td> <td>MdfHmdMetSourceType <a name="MdfHmdMetSourceType"> </a> </td> <td>MdfHmdMetSourceType</td> <td> Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD. <br/> </td> </tr> <tr> <td>1</td> <td>MdfHmdRowType <a name="MdfHmdRowType"> </a> </td> <td>MdfHmdRowType</td> <td> The row type codes for the tabular representation of a Hierarchical Message Description. <br/> </td> </tr> <tr> <td>1</td> <td>MdfRmimRowType <a name="MdfRmimRowType"> </a> </td> <td>MdfRmimRowType</td> <td> The row types for the tabular representation of an R-MIM. <br/> </td> </tr> <tr> <td>1</td> <td>MDFSubjectAreaPrefix <a name="MDFSubjectAreaPrefix"> </a> </td> <td>MDFSubjectAreaPrefix</td> <td> The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area. <br/> </td> </tr> <tr> <td>1</td> <td>MEDC <a name="MEDC"> </a> </td> <td>Medical Economics Drug Codes</td> <td> Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc. (800) 223-0581. <br/> </td> </tr> <tr> <td>1</td> <td>MEDCIN <a name="MEDCIN"> </a> </td> <td>MEDCIN</td> <td> 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: <br/> Symptoms History Physical Examination Tests Diagnoses Therapy <br/> 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. <br/> </td> </tr> <tr> <td>1</td> <td>MediaType <a name="MediaType"> </a> </td> <td>MediaType</td> <td> Internet Assigned Numbers Authority (IANA) Mime Media Types <br/> </td> </tr> <tr> <td>1</td> <td>MEDR <a name="MEDR"> </a> </td> <td>Medical Dictionary for Drug Regulatory Affairs (MEDRA)</td> <td> Dr. Louise Wood, Medicines Control Agency, Market Towers, 1 Nine Elms Lane, London SW85NQ, UK Tel: (44)0 171-273-0000 WWW: http://www.open.gov.uk/mca/mcahome.htm <br/> </td> </tr> <tr> <td>1</td> <td>MEDX <a name="MEDX"> </a> </td> <td>Medical Economics Diagnostic Codes</td> <td> Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc. (800) 223-0581. <br/> </td> </tr> <tr> <td>1</td> <td>MessageCondition <a name="MessageCondition"> </a> </td> <td>MessageCondition</td> <td/> </tr> <tr> <td>1</td> <td>MessageWaitingPriority <a name="MessageWaitingPriority"> </a> </td> <td>Message Waiting Priority</td> <td> Indicates that the receiver has messages for the sender <br/> </td> </tr> <tr> <td>1</td> <td>MGPI <a name="MGPI"> </a> </td> <td>Medispan GPI</td> <td> Medispan hierarchical drug codes for identifying drugs down to manufacturer and pill size. Proprietary product of MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel: (800) 428-4495. <br/> </td> </tr> <tr> <td>1</td> <td>MIME <a name="MIME"> </a> </td> <td>MIME</td> <td> IETF MIME media types <br/> </td> </tr> <tr> <td>1</td> <td>ModifyIndicator <a name="ModifyIndicator"> </a> </td> <td>ModifyIndicator</td> <td/> </tr> <tr> <td>1</td> <td>MSH <a name="MSH"> </a> </td> <td>MeSH</td> <td>Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004</td> </tr> <tr> <td>1</td> <td>MULTUM <a name="MULTUM"> </a> </td> <td>Multum Lexicon</td> <td> 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.) <br/> 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. <br/> Drug Ingredient A drug ingredient is a chemical compound or biologic agent that occurs in a drug product. <br/> 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. <br/> </td> </tr> <tr> <td>1</td> <td>MVX <a name="MVX"> </a> </td> <td>CDC Vaccine Manufacturer Codes</td> <td> National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333 <br/> </td> </tr> <tr> <td>1</td> <td>NAACCR <a name="NAACCR"> </a> </td> <td>NAACCR</td> <td> NAACCR Cancer Registry <br/> </td> </tr> <tr> <td>1</td> <td>NAICS <a name="NAICS"> </a> </td> <td>North American Industry Classification System</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>NDA <a name="NDA"> </a> </td> <td>NANDA</td> <td> North American Nursing Diagnosis Association, Philadelphia, PA. <br/> </td> </tr> <tr> <td>1</td> <td>NDC <a name="NDC"> </a> </td> <td>National drug codes</td> <td> These provide unique codes for each distinct drug, dosing form, manufacturer, and packaging. (Available from the National Drug Code Directory, FDA, Rockville, MD, and other sources.) <br/> </td> </tr> <tr> <td>1</td> <td>NIC <a name="NIC"> </a> </td> <td>Nursing Intervention Classification</td> <td> Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa <br/> </td> </tr> <tr> <td>1</td> <td>NMMDS <a name="NMMDS"> </a> </td> <td>Nursing Management Minimum Data Set</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>NOC <a name="NOC"> </a> </td> <td>NOC</td> <td> NOC - Nursing Outcome Codes <br/> </td> </tr> <tr> <td>1</td> <td>NUBC-UB92 <a name="NUBC-UB92"> </a> </td> <td>National Uniform Billing Council, UB 92</td> <td> The UB-92 data element specifications are developed and maintained by the NUBC. The data element specifications are for use in EDI billing and payment transactions and related business applications. There is a proprietary fee. Available from the National Uniform Billing Committee of the American Hospital Association, One North Franklin, Chicago, IL 60606. "UB-92 National Uniform Billing Data Element Specifications as developed by the National Uniform Billing Committee as of August 13, 1999". url: http://www.nubc.org <br/> </td> </tr> <tr> <td>1</td> <td>NUCCProviderCodes <a name="NUCCProviderCodes"> </a> </td> <td>NUCC Health Care Provider Taxonomy</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>NullFlavor <a name="NullFlavor"> </a> </td> <td>NullFlavor</td> <td/> </tr> <tr> <td>1</td> <td>ObservationInterpretation <a name="ObservationInterpretation"> </a> </td> <td>ObservationInterpretation</td> <td/> </tr> <tr> <td>1</td> <td>ObservationMethod <a name="ObservationMethod"> </a> </td> <td>ObservationMethod</td> <td/> </tr> <tr> <td>1</td> <td>ObservationValue <a name="ObservationValue"> </a> </td> <td>ObservationValue</td> <td> This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. <br/> </td> </tr> <tr> <td>1</td> <td>OHA <a name="OHA"> </a> </td> <td>Omaha System</td> <td> Omaha Visiting Nurse Association, Omaha, NB. <br/> </td> </tr> <tr> <td>1</td> <td>OPINIONS <a name="OPINIONS"> </a> </td> <td>Online Product Identification Number Index of Nova Scotia</td> <td> 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.2 3 <br/> </td> </tr> <tr> <td>1</td> <td>OrderableDrugForm <a name="OrderableDrugForm"> </a> </td> <td>OrderableDrugForm</td> <td/> </tr> <tr> <td>1</td> <td>OrganizationNameType <a name="OrganizationNameType"> </a> </td> <td>OrganizationNameType</td> <td/> </tr> <tr> <td>1</td> <td>ParameterizedDataType <a name="ParameterizedDataType"> </a> </td> <td>ParameterizedDataType</td> <td/> </tr> <tr> <td>1</td> <td>ParticipationFunction <a name="ParticipationFunction"> </a> </td> <td>ParticipationFunction</td> <td> 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). <br/> </td> </tr> <tr> <td>1</td> <td>ParticipationMode <a name="ParticipationMode"> </a> </td> <td>ParticipationMode</td> <td> Identifies the primary means by which an Entity participates in an Act. <br/> </td> </tr> <tr> <td>1</td> <td>ParticipationSignature <a name="ParticipationSignature"> </a> </td> <td>ParticipationSignature</td> <td/> </tr> <tr> <td>1</td> <td>ParticipationType <a name="ParticipationType"> </a> </td> <td>ParticipationType</td> <td/> </tr> <tr> <td>1</td> <td>PatientImportance <a name="PatientImportance"> </a> </td> <td>PatientImportance</td> <td> Patient VIP code <br/> </td> </tr> <tr> <td>1</td> <td>PaymentTerms <a name="PaymentTerms"> </a> </td> <td>PaymentTerms</td> <td> Describes payment terms for a financial transaction, used in an invoice. <br/> This is typically expressed as a responsibility of the acceptor or payor of an invoice. <br/> </td> </tr> <tr> <td>1</td> <td>PeriodicIntervalOfTimeAbbreviation <a name="PeriodicIntervalOfTimeAbbreviation"> </a> </td> <td>PeriodicIntervalOfTimeAbbreviation</td> <td/> </tr> <tr> <td>1</td> <td>PersonDisabilityType <a name="PersonDisabilityType"> </a> </td> <td>PersonDisabilityType</td> <td> A code identifying a person's disability. <br/> </td> </tr> <tr> <td>1</td> <td>PNDS <a name="PNDS"> </a> </td> <td>Perioperative Nursing Data Set</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>POS <a name="POS"> </a> </td> <td>POS Codes</td> <td> HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov /medicare/poscode.htm). <br/> </td> </tr> <tr> <td>1</td> <td>PostalAddressUse <a name="PostalAddressUse"> </a> </td> <td>PostalAddressUse</td> <td/> </tr> <tr> <td>1</td> <td>ProbabilityDistributionType <a name="ProbabilityDistributionType"> </a> </td> <td>ProbabilityDistributionType</td> <td/> </tr> <tr> <td>1</td> <td>ProcedureMethod <a name="ProcedureMethod"> </a> </td> <td>ProcedureMethod</td> <td> Identifies the technique used to perform a procedure. <br/> </td> </tr> <tr> <td>1</td> <td>ProcessingID <a name="ProcessingID"> </a> </td> <td>ProcessingID</td> <td/> </tr> <tr> <td>1</td> <td>ProcessingMode <a name="ProcessingMode"> </a> </td> <td>ProcessingMode</td> <td/> </tr> <tr> <td>1</td> <td>QueryParameterValue <a name="QueryParameterValue"> </a> </td> <td>QueryParameterValue</td> <td> The domain of coded values used as parameters within QueryByParameter queries. <br/> </td> </tr> <tr> <td>1</td> <td>QueryPriority <a name="QueryPriority"> </a> </td> <td>QueryPriority</td> <td/> </tr> <tr> <td>1</td> <td>QueryQuantityUnit <a name="QueryQuantityUnit"> </a> </td> <td>QueryQuantityUnit</td> <td> Values in this domain specify the units of a query quantity limited request. <br/> </td> </tr> <tr> <td>1</td> <td>QueryRequestLimit <a name="QueryRequestLimit"> </a> </td> <td>QueryRequestLimit</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>QueryResponse <a name="QueryResponse"> </a> </td> <td>QueryResponse</td> <td> Values in this domain allow a query response system to return a precise response status. <br/> </td> </tr> <tr> <td>1</td> <td>QueryStatusCode <a name="QueryStatusCode"> </a> </td> <td>QueryStatusCode</td> <td> State attributes for Query event <br/> </td> </tr> <tr> <td>1</td> <td>Race <a name="Race"> </a> </td> <td>Race</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>RC <a name="RC"> </a> </td> <td>Read Classification</td> <td> The Read Clinical Classification of Medicine, Park View Surgery, 26 Leicester Rd., Loughborough LE11 2AG (includes drug procedure and other codes, as well as diagnostic codes). <br/> </td> </tr> <tr> <td>1</td> <td>RCFB <a name="RCFB"> </a> </td> <td>The Read Codes Four Byte Set:</td> <td> The Read Codes Four Byte Set consists of 4 alphanumeric characters. This version contains approximately 40,000 codes arranged in a hierarchical structure. <br/> Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs <br/> </td> </tr> <tr> <td>1</td> <td>RCV2 <a name="RCV2"> </a> </td> <td>The Read Codes Version 2</td> <td> The Read Codes Version 2 contains over 70,000 coded concepts arranged in a hierarchical structure. <br/> Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs <br/> </td> </tr> <tr> <td>1</td> <td>RelationalOperator <a name="RelationalOperator"> </a> </td> <td>RelationalOperator</td> <td/> </tr> <tr> <td>1</td> <td>RelationshipConjunction <a name="RelationshipConjunction"> </a> </td> <td>RelationshipConjunction</td> <td/> </tr> <tr> <td>1</td> <td>ReligiousAffiliation <a name="ReligiousAffiliation"> </a> </td> <td>Religious Affiliation</td> <td> Assigment of spiritual faith affiliation <br/> </td> </tr> <tr> <td>1</td> <td>ResponseLevel <a name="ResponseLevel"> </a> </td> <td>ResponseLevel</td> <td> Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include <br/> </td> </tr> <tr> <td>1</td> <td>ResponseModality <a name="ResponseModality"> </a> </td> <td>ResponseModality</td> <td/> </tr> <tr> <td>1</td> <td>ResponseMode <a name="ResponseMode"> </a> </td> <td>ResponseMode</td> <td> Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities. <br/> </td> </tr> <tr> <td>1</td> <td>RoleClass <a name="RoleClass"> </a> </td> <td>RoleClass</td> <td/> </tr> <tr> <td>1</td> <td>RoleCode <a name="RoleCode"> </a> </td> <td>RoleCode</td> <td> Specific classification codes for further qualifying RoleClass codes. <br/> </td> </tr> <tr> <td>1</td> <td>RoleLinkStatus <a name="RoleLinkStatus"> </a> </td> <td>RoleLink Status</td> <td> Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine. <br/> </td> </tr> <tr> <td>1</td> <td>RoleLinkType <a name="RoleLinkType"> </a> </td> <td>RoleLinkType</td> <td/> </tr> <tr> <td>1</td> <td>RoleStatus <a name="RoleStatus"> </a> </td> <td>RoleStatus</td> <td> The status of an instance of the RIM Role class. <br/> </td> </tr> <tr> <td>1</td> <td>RouteOfAdministration <a name="RouteOfAdministration"> </a> </td> <td>RouteOfAdministration</td> <td/> </tr> <tr> <td>1</td> <td>SCDHEC-GISSpatialAccuracyTiers <a name="SCDHEC-GISSpatialAccuracyTiers"> </a> </td> <td>SCDHEC GIS Spatial Accuracy Tiers</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>SDM <a name="SDM"> </a> </td> <td>SNOMED- DICOM Microglossary</td> <td> College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM). <br/> </td> </tr> <tr> <td>1</td> <td>Sequencing <a name="Sequencing"> </a> </td> <td>Sequencing</td> <td/> </tr> <tr> <td>1</td> <td>SetOperator <a name="SetOperator"> </a> </td> <td>SetOperator</td> <td/> </tr> <tr> <td>1</td> <td>SNM <a name="SNM"> </a> </td> <td>Systemized Nomenclature of Medicine (SNOMED)</td> <td> Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL. <br/> </td> </tr> <tr> <td>1</td> <td>SNM3 <a name="SNM3"> </a> </td> <td>SNOMED International</td> <td> SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034.. <br/> </td> </tr> <tr> <td>1</td> <td>SNT <a name="SNT"> </a> </td> <td>SNOMED topology codes (anatomic sites)</td> <td> College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034. <br/> </td> </tr> <tr> <td>1</td> <td>SpecialArrangement <a name="SpecialArrangement"> </a> </td> <td>SpecialArrangement</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>SpecimenType <a name="SpecimenType"> </a> </td> <td>SpecimenType</td> <td/> </tr> <tr> <td>1</td> <td>StyleType <a name="StyleType"> </a> </td> <td>StyleType</td> <td> The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style <br/> </td> </tr> <tr> <td>1</td> <td>SubstanceAdminSubstitution <a name="SubstanceAdminSubstitution"> </a> </td> <td>SubstanceAdminSubstitution</td> <td> Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided. <br/> </td> </tr> <tr> <td>1</td> <td>SubstitutionCondition <a name="SubstitutionCondition"> </a> </td> <td>SubstitutionCondition</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>TableCellHorizontalAlign <a name="TableCellHorizontalAlign"> </a> </td> <td>TableCellHorizontalAlign</td> <td> These values are defined within the XHTML 4.0 Table Model <br/> </td> </tr> <tr> <td>1</td> <td>TableCellScope <a name="TableCellScope"> </a> </td> <td>TableCellScope</td> <td> These values are defined within the XHTML 4.0 Table Model <br/> </td> </tr> <tr> <td>1</td> <td>TableCellVerticalAlign <a name="TableCellVerticalAlign"> </a> </td> <td>TableCellVerticalAlign</td> <td> These values are defined within the XHTML 4.0 Table Model <br/> </td> </tr> <tr> <td>1</td> <td>TableFrame <a name="TableFrame"> </a> </td> <td>TableFrame</td> <td> These values are defined within the XHTML 4.0 Table Model <br/> </td> </tr> <tr> <td>1</td> <td>TableRules <a name="TableRules"> </a> </td> <td>TableRules</td> <td> These values are defined within the XHTML 4.0 Table Model <br/> </td> </tr> <tr> <td>1</td> <td>TargetAwareness <a name="TargetAwareness"> </a> </td> <td>TargetAwareness</td> <td/> </tr> <tr> <td>1</td> <td>TelecommunicationAddressUse <a name="TelecommunicationAddressUse"> </a> </td> <td>TelecommunicationAddressUse</td> <td/> </tr> <tr> <td>1</td> <td>TelecommunicationCapabilities <a name="TelecommunicationCapabilities"> </a> </td> <td>TelecommunicationCapabilities</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>TimingEvent <a name="TimingEvent"> </a> </td> <td>TimingEvent</td> <td/> </tr> <tr> <td>1</td> <td>TransmissionRelationshipTypeCode <a name="TransmissionRelationshipTypeCode"> </a> </td> <td>TransmissionRelationshipTypeCode</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>TribalEntityUS <a name="TribalEntityUS"> </a> </td> <td>TribalEntityUS</td> <td> INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS <br/> </td> </tr> <tr> <td>1</td> <td>TriggerEventID <a name="TriggerEventID"> </a> </td> <td>TriggerEventID</td> <td> Description:Trigger Event ID as published in the standard. <br/> </td> </tr> <tr> <td>1</td> <td>UC <a name="UC"> </a> </td> <td>UCDS</td> <td> Uniform Clinical Data Systems. Ms. Michael McMullan, Office of Peer Review Health Care Finance Administration, The Meadows East Bldg., 6325 Security Blvd., Baltimore, MD 21207; (301) 966 6851. <br/> </td> </tr> <tr> <td>1</td> <td>UCUM <a name="UCUM"> </a> </td> <td>UCUM</td> <td> Unified Code for Units of Measure <br/> </td> </tr> <tr> <td>1</td> <td>UMD <a name="UMD"> </a> </td> <td>MDNS</td> <td> Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone: 215-825-6000, Fax: 215-834-1275. <br/> </td> </tr> <tr> <td>1</td> <td>UML <a name="UML"> </a> </td> <td>Unified Medical Language</td> <td> National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894. <br/> </td> </tr> <tr> <td>1</td> <td>UnitsOfMeasure <a name="UnitsOfMeasure"> </a> </td> <td>UnitsOfMeasureCaseInsensitive</td> <td/> </tr> <tr> <td>1</td> <td>UPC <a name="UPC"> </a> </td> <td>Universal Product Code</td> <td> The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458; (513) 435 3070 <br/> </td> </tr> <tr> <td>1</td> <td>URLScheme <a name="URLScheme"> </a> </td> <td>URLScheme</td> <td> 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. <br/> </td> </tr> <tr> <td>1</td> <td>VaccineManufacturer <a name="VaccineManufacturer"> </a> </td> <td>VaccineManufacturer</td> <td> The manufacturer of a vaccine. <br/> </td> </tr> <tr> <td>1</td> <td>VaccineType <a name="VaccineType"> </a> </td> <td>VaccineType</td> <td> The kind of vaccine. <br/> </td> </tr> <tr> <td>1</td> <td>VocabularyDomainQualifier <a name="VocabularyDomainQualifier"> </a> </td> <td>VocabularyDomainQualifier</td> <td> Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain. <br/> </td> </tr> <tr> <td>1</td> <td>W1-W2 <a name="W1-W2"> </a> </td> <td>WHO rec# drug codes</td> <td> World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2. <br/> </td> </tr> <tr> <td>1</td> <td>W4 <a name="W4"> </a> </td> <td>WHO rec# code with ASTM extension</td> <td> With ASTM extensions (see Implementation Guide), the WHO codes can be used to report serum (and other) levels, patient compliance with drug usage instructions, average daily doses and more (see Appendix X1 the Implementation Guide). <br/> </td> </tr> <tr> <td>1</td> <td>WC <a name="WC"> </a> </td> <td>WHO ATC</td> <td> WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above. <br/> </td> </tr> </table> </div> </text> <identifier value="http://hl7.org/fhir/v3/vs/CodeSystem"/> <name value="v3 Code System CodeSystem"/> <publisher value="HL7, Inc"/> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> <description value=" Code systems used in HL7 standards."/> <status value="active"/> <date value="2014-08-07T00:00:00+10:00"/> <define> <system value="http://hl7.org/fhir/v3/CodeSystem"/> <caseSensitive value="true"/> <concept> <code value="ABCcodes"/> <display value="ABCcodes"/> <definition value="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. ."/> </concept> <concept> <code value="AcknowledgementCondition"/> <display value="AcknowledgementCondition"/> </concept> <concept> <code value="AcknowledgementDetailCode"/> <display value="AcknowledgementDetailCode"/> <definition value="A site specific problem code"/> </concept> <concept> <code value="AcknowledgementDetailType"/> <display value="Acknowledgement Detail Type"/> </concept> <concept> <code value="AcknowledgementType"/> <display value="AcknowledgementType"/> <definition value="Acknowledgement code as described in HL7 message processing rules."/> </concept> <concept> <code value="ACR"/> <display value="American College of Radiology finding codes"/> <definition value="Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA."/> </concept> <concept> <code value="ActClass"/> <display value="ActClass"/> </concept> <concept> <code value="ActCode"/> <display value="ActCode"/> <definition value="The table that provides the detailed or rich codes for the Act classes."/> </concept> <concept> <code value="ActExposureLevelCode"/> <display value="ActExposureLevelCode"/> <definition value="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."/> </concept> <concept> <code value="ActInvoiceElementModifier"/> <display value="ActInvoiceElementModifier"/> <definition value="Processing consideration and clarification codes."/> </concept> <concept> <code value="ActMood"/> <display value="ActMood"/> </concept> <concept> <code value="ActPriority"/> <display value="ActPriority"/> </concept> <concept> <code value="ActReason"/> <display value="ActReason"/> </concept> <concept> <code value="ActRelationshipCheckpoint"/> <display value="ActRelationshipCheckpoint"/> </concept> <concept> <code value="ActRelationshipJoin"/> <display value="ActRelationshipJoin"/> </concept> <concept> <code value="ActRelationshipSplit"/> <display value="ActRelationshipSplit"/> </concept> <concept> <code value="ActRelationshipSubset"/> <display value="ActRelationshipSubset"/> <definition value="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."/> </concept> <concept> <code value="ActRelationshipType"/> <display value="ActRelationshipType"/> <definition value="The source is an excerpt from the target."/> </concept> <concept> <code value="ActSite"/> <display value="ActSite"/> <definition value="An anatomical location on an organism which can be the focus of an act."/> </concept> <concept> <code value="ActStatus"/> <display value="ActStatus"/> <definition value="Contains the names (codes) for each of the states in the state-machine of the RIM Act class."/> </concept> <concept> <code value="ActUncertainty"/> <display value="ActUncertainty"/> </concept> <concept> <code value="ActUSPrivacyLaw"/> <display value="Act US Privacy Law"/> <definition value="Description: A jurisdictional mandate in the US relating to privacy."/> </concept> <concept> <code value="AddressPartType"/> <display value="AddressPartType"/> <definition value="Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line""/> </concept> <concept> <code value="AddressUse"/> <display value="AddressUse"/> <definition value="Description: Uses of Addresses. Lloyd to supply more complete description."/> </concept> <concept> <code value="AdministrativeGender"/> <display value="AdministrativeGender"/> <definition value="The gender of a person used for adminstrative purposes (as opposed to clinical gender)"/> </concept> <concept> <code value="AHFS"/> <display value="AHFS Pharmacologic-Therapeutic Classification"/> <definition value="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."/> </concept> <concept> <code value="AmericanIndianAlaskaNativeLanguages"/> <display value="AmericanIndianAlaskaNativeLanguages"/> <definition value="American Indian and Alaska Native languages currently being used in the United States."/> </concept> <concept> <code value="ART"/> <display value="WHO Adverse Reaction Terms"/> <definition value="WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden."/> </concept> <concept> <code value="AS4"/> <display value="ASTM E1238/ E1467 Universal"/> <definition value="American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467)."/> </concept> <concept> <code value="AS4E"/> <display value="AS4 Neurophysiology Codes"/> <definition value="ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2."/> </concept> <concept> <code value="ATC"/> <display value="American Type Culture Collection"/> <definition value="Reference cultures (microorganisms, tissue cultures, etc.), related biological materials and associated data. American Type Culture Collection, 12301 Parklawn Dr, Rockville MD, 20852. (301) 881-2600. http://www.atcc.org"/> </concept> <concept> <code value="BindingRealm"/> <display value="BindingRealm"/> <definition value="Description: Coded concepts representing the Binding Realms used for Context Binding of terminology in HL7 models. Where concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the codes. For those realms where they do not,. codes are created for the concepts. These codes are generally carried in InfrastructureRoot.realmco de, and are used in Context Binding statements."/> </concept> <concept> <code value="BodySite"/> <display value="HL7 table 0163 - Body site"/> <definition value="Description: HL7 version 2.x Body site used in chapter(s) 4; HL7 table 0163"/> </concept> <concept> <code value="C4"/> <display value="CPT-4"/> <definition value="American Medical Association, P.O. Box 10946, Chicago IL 60610."/> </concept> <concept> <code value="C5"/> <display value="CPT-5"/> <definition value="American Medical Association, P.O. Box 10946, Chicago IL 60610."/> </concept> <concept> <code value="Calendar"/> <display value="Calendar"/> </concept> <concept> <code value="CalendarCycle"/> <display value="CalendarCycle"/> </concept> <concept> <code value="CalendarType"/> <display value="CalendarType"/> </concept> <concept> <code value="CAMNCVS"/> <display value="CAMNCVS"/> <definition value="CAM & Nursing Coding Vocabulary Set"/> </concept> <concept> <code value="CAS"/> <display value="Chemical abstract codes"/> <definition value="These include unique codes for each unique chemical, including all generic drugs. The codes do not distinguish among different dosing forms. When multiple equivalent CAS numbers exist, use the first one listed in USAN. USAN 1990 and the USP dictionary of drug names, William M. Heller, Ph.D., Executive Editor, United States Pharmacopeial Convention, Inc., 12601 Twinbrook Parkway, Rockville, MD 20852."/> </concept> <concept> <code value="CCI"/> <display value="Canadian Classification of Health Interventions"/> <definition value="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"/> </concept> <concept> <code value="CD2"/> <display value="CDT-2 Codes"/> <definition value="American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611."/> </concept> <concept> <code value="CDCA"/> <display value="CDC Analyte Codes"/> <definition value="Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/laboratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA"/> </concept> <concept> <code value="CDCM"/> <display value="CDC Methods/Instruments Codes"/> <definition value="Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/laboratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA"/> </concept> <concept> <code value="CDS"/> <display value="CDC Surveillance"/> <definition value="CDC Surveillance Codes. For data unique to specific public health surveillance requirements. Epidemiology Program Office, Centers for Disease Control and Prevention, 1600 Clifton Rd, Atlanta, GA, 30333. (404) 639-3661."/> </concept> <concept> <code value="CE"/> <display value="CEN ECG diagnostic codes"/> <definition value="CEN PT007. A quite comprehensive set of ECG diagnostic codes (abbreviations) and descriptions published as a pre-standard by CEN TC251. Available from CEN TC251 secretariat, c/o Georges DeMoor, State University Hospital Gent, De Pintelaan 185-5K3, 9000 Ge"/> </concept> <concept> <code value="Charset"/> <display value="Charset"/> <definition value="Internet Assigned Numbers Authority (IANA) Charset Types"/> </concept> <concept> <code value="CLP"/> <display value="CLIP"/> <definition value="Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports."/> </concept> <concept> <code value="CodeSystem"/> <display value="CodeSystem"/> <definition value="Code systems used in HL7 standards."/> </concept> <concept> <code value="CodeSystemType"/> <display value="HL7 Code System Type"/> </concept> <concept> <code value="CodingRationale"/> <display value="CodingRationale"/> <definition value="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."/> </concept> <concept> <code value="CommunicationFunctionType"/> <display value="CommunicationFunctionType"/> <definition value="Describes the type of communication function that the associated entity plays in the associated transmission."/> </concept> <concept> <code value="CompressionAlgorithm"/> <display value="CompressionAlgorithm"/> </concept> <concept> <code value="ConceptCodeRelationship"/> <display value="Possible Concept Code Relationships"/> </concept> <concept> <code value="ConceptGenerality"/> <display value="ConceptGenerality"/> <definition value="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."/> </concept> <concept> <code value="ConceptProperty"/> <display value="HL7 Value Set and Coded Concept Property Codes"/> </concept> <concept> <code value="ConceptStatus"/> <display value="HL7 Coded Concept Status"/> </concept> <concept> <code value="Confidentiality"/> <display value="Confidentiality"/> </concept> <concept> <code value="ContainerCap"/> <display value="ContainerCap"/> <definition value="The type of cap associated with a container"/> </concept> <concept> <code value="ContainerSeparator"/> <display value="ContainerSeparator"/> <definition value="A material in a blood collection container that facilites the separation of of blood cells from serum or plasma"/> </concept> <concept> <code value="ContentProcessingMode"/> <display value="ContentProcessingMode"/> <definition value="Description:Identifies the order in which content should be processed."/> </concept> <concept> <code value="ContextConductionStyle"/> <display value="ContextConductionStyle"/> <definition value="The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model."/> </concept> <concept> <code value="ContextControl"/> <display value="ContextControl"/> <definition value="This table contains the control codes that are used to manage the propagation and scope of a particular ActRelationship or Participation within a set of Acts."/> </concept> <concept> <code value="CSAID"/> <display value="CAN/CSA-Z795-96 (R2001)"/> <definition value="CAN/CSA-Z795-96 (R2001) - This Standard provides a framework for consistent recording and classification of information on work-related injuries and diseases in Canada (injury coding). It is constituted of Nature of injury, body part, side of body. For example: Cut or laceration of the Upper Arm, Left Injury = 03400; body part = 31100; side of body = L Code 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"/> </concept> <concept> <code value="CST"/> <display value="COSTART"/> <definition value="International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD."/> </concept> <concept> <code value="Currency"/> <display value="Currency"/> <definition value="The currency unit as defined in ISO 4217"/> </concept> <concept> <code value="CVX"/> <display value="CDC Vaccine Codes"/> <definition value="National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333"/> </concept> <concept> <code value="DataOperation"/> <display value="DataOperation"/> </concept> <concept> <code value="DataType"/> <display value="DataType"/> </concept> <concept> <code value="DCL"/> <display value="DICOM Class Label"/> <definition value="From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034"/> </concept> <concept> <code value="DCM"/> <display value="DICOM modality codes"/> <definition value="Dean Bidgood, MD; Duke University Medical Center, Durham NC. Digital Imaging and Communications in Medicine (DICOM). From NEMA Publications PS-3.1 - PS 3.12: The ACR-NEMA DICOM Standard. National Electrical Manufacturers Association (NEMA). Rosslyn, VA,"/> </concept> <concept> <code value="Dentition"/> <display value="Dentition"/> </concept> <concept> <code value="DeviceAlertLevel"/> <display value="DeviceAlertLevel"/> <definition value="Domain values for the Device.Alert_levelCode"/> </concept> <concept> <code value="DocumentCompletion"/> <display value="DocumentCompletion"/> <definition value="Identifies the current completion state of a clinical document."/> </concept> <concept> <code value="DocumentStorage"/> <display value="DocumentStorage"/> <definition value="Identifies the storage status of a document."/> </concept> <concept> <code value="DQL"/> <display value="DICOM Query Label"/> <definition value="HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI."/> </concept> <concept> <code value="E"/> <display value="EUCLIDES"/> <definition value="Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60."/> </concept> <concept> <code value="E5"/> <display value="Euclides quantity codes"/> <definition value="Available from Euclides Foundation International nv (see above)"/> </concept> <concept> <code value="E6"/> <display value="Euclides Lab method codes"/> <definition value="Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60."/> </concept> <concept> <code value="E7"/> <display value="Euclides Lab equipment codes"/> <definition value="Available from Euclides Foundation International nv (see above)"/> </concept> <concept> <code value="EditStatus"/> <display value="EditStatus"/> <definition value="The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database."/> </concept> <concept> <code value="EducationLevel"/> <display value="Education Level"/> <definition value="Years of education that a person has completed"/> </concept> <concept> <code value="EmployeeJobClass"/> <display value="EmployeeJobClass"/> </concept> <concept> <code value="EncounterAccident"/> <display value="EncounterAccident"/> </concept> <concept> <code value="EncounterAcuity"/> <display value="Encounter Acuity"/> <definition value="The level of resource intensiveness of patient care."/> </concept> <concept> <code value="EncounterAdmissionSource"/> <display value="EncounterAdmissionSource"/> </concept> <concept> <code value="EncounterReferralSource"/> <display value="EncounterReferralSource"/> <definition value="This domain is defined in UB92 and applies to US realm only"/> </concept> <concept> <code value="EncounterSpecialCourtesy"/> <display value="EncounterSpecialCourtesy"/> </concept> <concept> <code value="EntityClass"/> <display value="EntityClass"/> <definition value="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."/> </concept> <concept> <code value="EntityCode"/> <display value="EntityCode"/> </concept> <concept> <code value="EntityDeterminer"/> <display value="EntityDeterminer"/> <definition value="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."/> </concept> <concept> <code value="EntityHandling"/> <display value="EntityHandling"/> </concept> <concept> <code value="EntityNamePartQualifier"/> <display value="EntityNamePartQualifier"/> </concept> <concept> <code value="EntityNamePartQualifierR2"/> <display value="EntityNamePartQualifierR2"/> <definition value="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."/> </concept> <concept> <code value="EntityNamePartType"/> <display value="EntityNamePartType"/> </concept> <concept> <code value="EntityNamePartTypeR2"/> <display value="EntityNamePartTypeR2"/> <definition value="Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc."/> </concept> <concept> <code value="EntityNameUse"/> <display value="EntityNameUse"/> </concept> <concept> <code value="EntityNameUseR2"/> <display value="EntityNameUseR2"/> <definition value="Description:A set of codes advising a system or user which name in a set of names to select for a given purpose."/> </concept> <concept> <code value="EntityRisk"/> <display value="EntityRisk"/> <definition value="The vocabulary table for the Entity.riskCode attribute"/> </concept> <concept> <code value="EntityStatus"/> <display value="EntityStatus"/> <definition value="The status of an instance of the RIM Entity class."/> </concept> <concept> <code value="ENZC"/> <display value="Enzyme Codes"/> <definition value="Enzyme Committee of the International Union of Biochemistry and Molecular Biology. Enzyme Nomenclature: Recommendations on the Nomenclature and Classification of Enzyme-Catalysed Reactions. London: Academic Press, 1992."/> </concept> <concept> <code value="EPSG_CA"/> <display value="European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis"/> <definition value="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."/> </concept> <concept> <code value="EPSG_CRS"/> <display value="European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System"/> <definition value="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."/> </concept> <concept> <code value="EPSG-GeodeticParameterDataset"/> <display value="EPSG Geodetic Parameter Dataset"/> <definition value="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."/> </concept> <concept> <code value="EquipmentAlertLevel"/> <display value="EquipmentAlertLevel"/> </concept> <concept> <code value="Ethnicity"/> <display value="Ethnicity"/> <definition value="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."/> </concept> <concept> <code value="ExposureMode"/> <display value="ExposureMode"/> <definition value="Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure."/> </concept> <concept> <code value="FDDC"/> <display value="First DataBank Drug Codes"/> <definition value="National Drug Data File. Proprietary product of First DataBank, Inc. (800) 633-3453, or http://www.firstdatabank.com."/> </concept> <concept> <code value="FDDX"/> <display value="First DataBank Diagnostic Codes"/> <definition value="Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC."/> </concept> <concept> <code value="FDK"/> <display value="FDA K10"/> <definition value="Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes)."/> </concept> <concept> <code value="GenderStatus"/> <display value="GenderStatus"/> </concept> <concept> <code value="GTSAbbreviation"/> <display value="GTSAbbreviation"/> </concept> <concept> <code value="HB"/> <display value="HIBCC"/> <definition value="Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018."/> </concept> <concept> <code value="HC-AIC"/> <display value="Active Ingredient Code"/> <definition value="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"/> </concept> <concept> <code value="HC-AIGC"/> <display value="Active Ingredient Group Code"/> <definition value="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"/> </concept> <concept> <code value="HC-AIGN"/> <display value="Active Ingredient Group Number"/> <definition value="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"/> </concept> <concept> <code value="HC-DIN"/> <display value="Health Canada Drug Id Number"/> <definition value="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"/> </concept> <concept> <code value="HC-NPN"/> <display value="Health Canada Natural Product Number"/> <definition value="Description: 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-pro d/lnhpd-bdpsnh-eng.php"/> </concept> <concept> <code value="HealthcareProviderTaxonomyHIPAA"/> <display value="HealthcareProviderTaxonomyHIPAA"/> </concept> <concept> <code value="HealthcareServiceLocation"/> <display value="Healthcare Service Location"/> <definition value="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."/> </concept> <concept> <code value="HHC"/> <display value="Home Health Care"/> <definition value="Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC."/> </concept> <concept> <code value="HI"/> <display value="Health Outcomes"/> <definition value="Health Outcomes Institute codes for outcome variables available (with responses) from Stratis Health (formerly Foundation for Health Care Evaluation and Health Outcomes Institute), 2901 Metro Drive, Suite 400, Bloomington, MN, 55425-1525; (612) 854-3306 (voice); (612) 853-8503 (fax); dziegen@winternet.com. See examples in the Implementation Guide."/> </concept> <concept> <code value="hl7ApprovalStatus"/> <display value="HL7ApprovalStatus"/> <definition value="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."/> </concept> <concept> <code value="hl7CMETAttribution"/> <display value="HL7CMETAttribution"/> </concept> <concept> <code value="HL7CommitteeIDInRIM"/> <display value="HL7CommitteeIDInRIM"/> <definition value="Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables."/> </concept> <concept> <code value="HL7ConformanceInclusion"/> <display value="HL7ConformanceInclusion"/> <definition value="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."/> </concept> <concept> <code value="HL7DefinedRoseProperty"/> <display value="HL7DefinedRoseProperty"/> <definition value="The property Ids that HL7 has defined for customizing Rational Rose."/> </concept> <concept> <code value="hl7ITSType"/> <display value="HL7ITSType"/> <definition value="Description: Codes identifying types of HL7 Implementation Technology Specifications"/> </concept> <concept> <code value="HL7ITSVersionCode"/> <display value="HL7 ITS Version Code"/> <definition value="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."/> </concept> <concept> <code value="hl7PublishingDomain"/> <display value="HL7PublishingDomain"/> <definition value="Description: Codes for HL7 publishing 'domain's (specific content area)"/> </concept> <concept> <code value="hl7PublishingSection"/> <display value="HL7PublishingSection"/> <definition value="Description: Codes for HL7 publishing 'section's (major business categories)"/> </concept> <concept> <code value="hl7PublishingSubSection"/> <display value="HL7PublishingSubSection"/> <definition value="Description: Codes for HL7 publishing 'sub-section's (business sub-categories)"/> </concept> <concept> <code value="HL7StandardVersionCode"/> <display value="HL7StandardVersionCode"/> <definition value="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."/> </concept> <concept> <code value="HL7UpdateMode"/> <display value="HL7UpdateMode"/> <definition value="The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute."/> </concept> <concept> <code value="hl7V3Conformance"/> <display value="HL7V3Conformance"/> <definition value="Description: Identifies allowed codes for HL7aTMs v3 conformance property."/> </concept> <concept> <code value="hl7VoteResolution"/> <display value="HL7VoteResolution"/> <definition value="Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM)."/> </concept> <concept> <code value="HPC"/> <display value="HCFA Procedure Codes (HCPCS)"/> <definition value="Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) modifiers."/> </concept> <concept> <code value="HtmlLinkType"/> <display value="HtmlLinkType"/> <definition value="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"/> </concept> <concept> <code value="I10"/> <display value="ICD-10"/> <definition value="World Health Publications, Albany, NY."/> </concept> <concept> <code value="I10P"/> <display value="ICD-10 Procedure Codes"/> <definition value="Procedure Coding System (ICD-10-PCS). See http://www/hcfa.gov/stats/icd10.icd10.htm for more information."/> </concept> <concept> <code value="I9"/> <display value="ICD9"/> <definition value="World Health Publications, Albany, NY."/> </concept> <concept> <code value="I9C"/> <display value="ICD-9CM"/> <definition value="Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests)."/> </concept> <concept> <code value="IBT"/> <display value="ISBT"/> <definition value="International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169."/> </concept> <concept> <code value="IC2"/> <display value="ICHPPC-2"/> <definition value="International Classification of Health Problems in Primary Care, Classification Committee of World Organization of National Colleges, Academies and Academic Associations of General Practitioners (WONCA), 3rd edition. An adaptation of ICD9 intended for use in General Medicine, Oxford University Press."/> </concept> <concept> <code value="ICD-10-CA"/> <display value="CanadianDiagnosisCodesICD-10-CA"/> <definition value="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"/> </concept> <concept> <code value="ICDO"/> <display value="International Classification of Diseases for Oncology"/> <definition value="International Classification of Diseases for Oncology, 2nd Edition. World Health Organization: Geneva, Switzerland, 1990. Order from: College of American Pathologists, 325 Waukegan Road, Northfield, IL, 60093-2750. (847) 446-8800."/> </concept> <concept> <code value="ICS"/> <display value="ICCS"/> <definition value="Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105."/> </concept> <concept> <code value="ICSD"/> <display value="International Classification of Sleep Disorders"/> <definition value="International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902"/> </concept> <concept> <code value="IdentifierReliability"/> <display value="IdentifierReliability"/> <definition value="Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms."/> </concept> <concept> <code value="IdentifierScope"/> <display value="IdentifierScope"/> <definition value="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."/> </concept> <concept> <code value="IETF1766"/> <display value="IETF RFC 1766"/> <definition value="Language identifiers as defined by IETF RFC 1766: Tags for the Identification of Languages, or its successor on the IETF Standards Track. The biblio ref for RFC 1766 is: IETF (Internet Engineering Task Force), RFC 1766: Tag"/> </concept> <concept> <code value="IETF3066"/> <display value="Tags for the Identification of Languages"/> <definition value="from OID registry"/> </concept> <concept> <code value="IntegrityCheckAlgorithm"/> <display value="IntegrityCheckAlgorithm"/> </concept> <concept> <code value="iso21000-6-2004E-RDD"/> <display value="ISO/IEC 21000-6:2004(E) Rights Data Dictionary"/> <definition value="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."/> </concept> <concept> <code value="ISO3166-1"/> <display value="ISO 3166 2 Character Country Codes"/> <definition value="Two character country codes"/> </concept> <concept> <code value="ISO3166-2"/> <display value="ISO 3166 3 Character Country Codes"/> <definition value="Three character country codes"/> </concept> <concept> <code value="ISO3166-3"/> <display value="ISO 3166 Numeric country Codes"/> <definition value="Numeric country codes"/> </concept> <concept> <code value="ISO4217"/> <display value="ISO4217"/> <definition value="ISO 4217 currency code"/> </concept> <concept> <code value="IUPC"/> <display value="IUPAC/IFCC Component Codes"/> <definition value="Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP."/> </concept> <concept> <code value="IUPP"/> <display value="IUPAC/IFCC Property Codes"/> <definition value="International Union of Pure and Applied Chemistry/International Federation of Clinical Chemistry. The Silver Book: Compendium of terminology and nomenclature of properties in clinical laboratory sciences. Oxford: Blackwell Scientific Publishers, 1995. Henrik Olesen, M.D., D.M.Sc., Chairperson, Department of Clinical Chemistry, KK76.4.2, Rigshospitalet, University Hospital of Copenhagen, DK-2200, Copenhagen. http://inet.uni-c.dk/~qukb7642/"/> </concept> <concept> <code value="JC8"/> <display value="Japanese Chemistry"/> <definition value="Clinical examination classification code. Japan Association of Clinical Pathology. Version 8, 1990. A multiaxial code including a subject code (e.g., Rubella = 5f395, identification code (e.g., virus ab IGG), a specimen code (e.g., serum =023) and a method code (e.g., ELISA = 022)"/> </concept> <concept> <code value="LanguageAbilityMode"/> <display value="LanguageAbilityMode"/> </concept> <concept> <code value="LanguageAbilityProficiency"/> <display value="LanguageAbilityProficiency"/> </concept> <concept> <code value="LivingArrangement"/> <display value="LivingArrangement"/> <definition value="A code depicting the living arrangements of a person"/> </concept> <concept> <code value="LN"/> <display value="Logical Observation Identifier Names and Codes (LOINC)"/> <definition value="Regenstrief Institute, c/o LOINC, 1050 Wishard Blvd., 5th floor, Indianapolis, IN 46202. 317/630-7433. Available from the Regenstrief Institute server at http://www.regenstrief.org/loinc /loinc.htm. Also available via HL7 file server: FTP/Gopher (www.mcis.duke.edu/standards/ termcode/loinclab and www.mcis.duke.edu/standards/termcode/loinclin) and World Wide Web (http:// www.mcis.duke.edu/ standards/termcode/loincl.htm). January 2000 version has identifiers, synonyms and cross-reference codes for reporting over 26,000 laboratory and related observations and 1,500 clinical measures."/> </concept> <concept> <code value="LocalMarkupIgnore"/> <display value="LocalMarkupIgnore"/> <definition value="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""/> </concept> <concept> <code value="LocalRemoteControlState"/> <display value="LocalRemoteControlState"/> </concept> <concept> <code value="ManagedParticipationStatus"/> <display value="ManagedParticipationStatus"/> <definition value="The status of an instance of the RIM Participation class."/> </concept> <concept> <code value="MapRelationship"/> <display value="MapRelationship"/> <definition value="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"/> </concept> <concept> <code value="MaritalStatus"/> <display value="MaritalStatus"/> </concept> <concept> <code value="MaterialType"/> <display value="MaterialType"/> </concept> <concept> <code value="MDC"/> <display value="ISO 11073-10101 Health informatics - Point-of-care"/> <definition value="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."/> </concept> <concept> <code value="MDDX"/> <display value="Medispan Diagnostic Codes"/> <definition value="Codes Used for drug-diagnosis interaction checking. Proprietary product. Hierarchical drug codes for identifying drugs down to manufacturer and pill size. MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel: (800) 428-4495. WWW: http://www.espan.co m/medispan/pages/ medhome.html. As above for MGPI."/> </concept> <concept> <code value="MDFAttributeType"/> <display value="MDFAttributeType"/> </concept> <concept> <code value="MdfHmdMetSourceType"/> <display value="MdfHmdMetSourceType"/> <definition value="Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD."/> </concept> <concept> <code value="MdfHmdRowType"/> <display value="MdfHmdRowType"/> <definition value="The row type codes for the tabular representation of a Hierarchical Message Description."/> </concept> <concept> <code value="MdfRmimRowType"/> <display value="MdfRmimRowType"/> <definition value="The row types for the tabular representation of an R-MIM."/> </concept> <concept> <code value="MDFSubjectAreaPrefix"/> <display value="MDFSubjectAreaPrefix"/> <definition value="The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area."/> </concept> <concept> <code value="MEDC"/> <display value="Medical Economics Drug Codes"/> <definition value="Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc. (800) 223-0581."/> </concept> <concept> <code value="MEDCIN"/> <display value="MEDCIN"/> <definition value="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."/> </concept> <concept> <code value="MediaType"/> <display value="MediaType"/> <definition value="Internet Assigned Numbers Authority (IANA) Mime Media Types"/> </concept> <concept> <code value="MEDR"/> <display value="Medical Dictionary for Drug Regulatory Affairs (MEDRA)"/> <definition value="Dr. Louise Wood, Medicines Control Agency, Market Towers, 1 Nine Elms Lane, London SW85NQ, UK Tel: (44)0 171-273-0000 WWW: http://www.open.gov.uk/mca/mcahome.htm"/> </concept> <concept> <code value="MEDX"/> <display value="Medical Economics Diagnostic Codes"/> <definition value="Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc. (800) 223-0581."/> </concept> <concept> <code value="MessageCondition"/> <display value="MessageCondition"/> </concept> <concept> <code value="MessageWaitingPriority"/> <display value="Message Waiting Priority"/> <definition value="Indicates that the receiver has messages for the sender"/> </concept> <concept> <code value="MGPI"/> <display value="Medispan GPI"/> <definition value="Medispan hierarchical drug codes for identifying drugs down to manufacturer and pill size. Proprietary product of MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel: (800) 428-4495."/> </concept> <concept> <code value="MIME"/> <display value="MIME"/> <definition value="IETF MIME media types"/> </concept> <concept> <code value="ModifyIndicator"/> <display value="ModifyIndicator"/> </concept> <concept> <code value="MSH"/> <display value="MeSH"/> <definition value="Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004"/> </concept> <concept> <code value="MULTUM"/> <display value="Multum Lexicon"/> <definition value="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."/> </concept> <concept> <code value="MVX"/> <display value="CDC Vaccine Manufacturer Codes"/> <definition value="National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333"/> </concept> <concept> <code value="NAACCR"/> <display value="NAACCR"/> <definition value="NAACCR Cancer Registry"/> </concept> <concept> <code value="NAICS"/> <display value="North American Industry Classification System"/> <definition value="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."/> </concept> <concept> <code value="NDA"/> <display value="NANDA"/> <definition value="North American Nursing Diagnosis Association, Philadelphia, PA."/> </concept> <concept> <code value="NDC"/> <display value="National drug codes"/> <definition value="These provide unique codes for each distinct drug, dosing form, manufacturer, and packaging. (Available from the National Drug Code Directory, FDA, Rockville, MD, and other sources.)"/> </concept> <concept> <code value="NIC"/> <display value="Nursing Intervention Classification"/> <definition value="Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa"/> </concept> <concept> <code value="NMMDS"/> <display value="Nursing Management Minimum Data Set"/> <definition value="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."/> </concept> <concept> <code value="NOC"/> <display value="NOC"/> <definition value="NOC - Nursing Outcome Codes"/> </concept> <concept> <code value="NUBC-UB92"/> <display value="National Uniform Billing Council, UB 92"/> <definition value="The UB-92 data element specifications are developed and maintained by the NUBC. The data element specifications are for use in EDI billing and payment transactions and related business applications. There is a proprietary fee. Available from the National Uniform Billing Committee of the American Hospital Association, One North Franklin, Chicago, IL 60606. "UB-92 National Uniform Billing Data Element Specifications as developed by the National Uniform Billing Committee as of August 13, 1999". url: http://www.nubc.org"/> </concept> <concept> <code value="NUCCProviderCodes"/> <display value="NUCC Health Care Provider Taxonomy"/> <definition value="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."/> </concept> <concept> <code value="NullFlavor"/> <display value="NullFlavor"/> </concept> <concept> <code value="ObservationInterpretation"/> <display value="ObservationInterpretation"/> </concept> <concept> <code value="ObservationMethod"/> <display value="ObservationMethod"/> </concept> <concept> <code value="ObservationValue"/> <display value="ObservationValue"/> <definition value="This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type."/> </concept> <concept> <code value="OHA"/> <display value="Omaha System"/> <definition value="Omaha Visiting Nurse Association, Omaha, NB."/> </concept> <concept> <code value="OPINIONS"/> <display value="Online Product Identification Number Index of Nova Scotia"/> <definition value="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"/> </concept> <concept> <code value="OrderableDrugForm"/> <display value="OrderableDrugForm"/> </concept> <concept> <code value="OrganizationNameType"/> <display value="OrganizationNameType"/> </concept> <concept> <code value="ParameterizedDataType"/> <display value="ParameterizedDataType"/> </concept> <concept> <code value="ParticipationFunction"/> <display value="ParticipationFunction"/> <definition value="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)."/> </concept> <concept> <code value="ParticipationMode"/> <display value="ParticipationMode"/> <definition value="Identifies the primary means by which an Entity participates in an Act."/> </concept> <concept> <code value="ParticipationSignature"/> <display value="ParticipationSignature"/> </concept> <concept> <code value="ParticipationType"/> <display value="ParticipationType"/> </concept> <concept> <code value="PatientImportance"/> <display value="PatientImportance"/> <definition value="Patient VIP code"/> </concept> <concept> <code value="PaymentTerms"/> <display value="PaymentTerms"/> <definition value="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."/> </concept> <concept> <code value="PeriodicIntervalOfTimeAbbreviation"/> <display value="PeriodicIntervalOfTimeAbbreviation"/> </concept> <concept> <code value="PersonDisabilityType"/> <display value="PersonDisabilityType"/> <definition value="A code identifying a person's disability."/> </concept> <concept> <code value="PNDS"/> <display value="Perioperative Nursing Data Set"/> <definition value="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."/> </concept> <concept> <code value="POS"/> <display value="POS Codes"/> <definition value="HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm)."/> </concept> <concept> <code value="PostalAddressUse"/> <display value="PostalAddressUse"/> </concept> <concept> <code value="ProbabilityDistributionType"/> <display value="ProbabilityDistributionType"/> </concept> <concept> <code value="ProcedureMethod"/> <display value="ProcedureMethod"/> <definition value="Identifies the technique used to perform a procedure."/> </concept> <concept> <code value="ProcessingID"/> <display value="ProcessingID"/> </concept> <concept> <code value="ProcessingMode"/> <display value="ProcessingMode"/> </concept> <concept> <code value="QueryParameterValue"/> <display value="QueryParameterValue"/> <definition value="The domain of coded values used as parameters within QueryByParameter queries."/> </concept> <concept> <code value="QueryPriority"/> <display value="QueryPriority"/> </concept> <concept> <code value="QueryQuantityUnit"/> <display value="QueryQuantityUnit"/> <definition value="Values in this domain specify the units of a query quantity limited request."/> </concept> <concept> <code value="QueryRequestLimit"/> <display value="QueryRequestLimit"/> <definition value="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."/> </concept> <concept> <code value="QueryResponse"/> <display value="QueryResponse"/> <definition value="Values in this domain allow a query response system to return a precise response status."/> </concept> <concept> <code value="QueryStatusCode"/> <display value="QueryStatusCode"/> <definition value="State attributes for Query event"/> </concept> <concept> <code value="Race"/> <display value="Race"/> <definition value="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."/> </concept> <concept> <code value="RC"/> <display value="Read Classification"/> <definition value="The Read Clinical Classification of Medicine, Park View Surgery, 26 Leicester Rd., Loughborough LE11 2AG (includes drug procedure and other codes, as well as diagnostic codes)."/> </concept> <concept> <code value="RCFB"/> <display value="The Read Codes Four Byte Set:"/> <definition value="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"/> </concept> <concept> <code value="RCV2"/> <display value="The Read Codes Version 2"/> <definition value="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"/> </concept> <concept> <code value="RelationalOperator"/> <display value="RelationalOperator"/> </concept> <concept> <code value="RelationshipConjunction"/> <display value="RelationshipConjunction"/> </concept> <concept> <code value="ReligiousAffiliation"/> <display value="Religious Affiliation"/> <definition value="Assigment of spiritual faith affiliation"/> </concept> <concept> <code value="ResponseLevel"/> <display value="ResponseLevel"/> <definition value="Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include"/> </concept> <concept> <code value="ResponseModality"/> <display value="ResponseModality"/> </concept> <concept> <code value="ResponseMode"/> <display value="ResponseMode"/> <definition value="Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities."/> </concept> <concept> <code value="RoleClass"/> <display value="RoleClass"/> </concept> <concept> <code value="RoleCode"/> <display value="RoleCode"/> <definition value="Specific classification codes for further qualifying RoleClass codes."/> </concept> <concept> <code value="RoleLinkStatus"/> <display value="RoleLink Status"/> <definition value="Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine."/> </concept> <concept> <code value="RoleLinkType"/> <display value="RoleLinkType"/> </concept> <concept> <code value="RoleStatus"/> <display value="RoleStatus"/> <definition value="The status of an instance of the RIM Role class."/> </concept> <concept> <code value="RouteOfAdministration"/> <display value="RouteOfAdministration"/> </concept> <concept> <code value="SCDHEC-GISSpatialAccuracyTiers"/> <display value="SCDHEC GIS Spatial Accuracy Tiers"/> <definition value="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."/> </concept> <concept> <code value="SDM"/> <display value="SNOMED- DICOM Microglossary"/> <definition value="College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM)."/> </concept> <concept> <code value="Sequencing"/> <display value="Sequencing"/> </concept> <concept> <code value="SetOperator"/> <display value="SetOperator"/> </concept> <concept> <code value="SNM"/> <display value="Systemized Nomenclature of Medicine (SNOMED)"/> <definition value="Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL."/> </concept> <concept> <code value="SNM3"/> <display value="SNOMED International"/> <definition value="SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034.."/> </concept> <concept> <code value="SNT"/> <display value="SNOMED topology codes (anatomic sites)"/> <definition value="College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034."/> </concept> <concept> <code value="SpecialArrangement"/> <display value="SpecialArrangement"/> <definition value="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."/> </concept> <concept> <code value="SpecimenType"/> <display value="SpecimenType"/> </concept> <concept> <code value="StyleType"/> <display value="StyleType"/> <definition value="The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style"/> </concept> <concept> <code value="SubstanceAdminSubstitution"/> <display value="SubstanceAdminSubstitution"/> <definition value="Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided."/> </concept> <concept> <code value="SubstitutionCondition"/> <display value="SubstitutionCondition"/> <definition value="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."/> </concept> <concept> <code value="TableCellHorizontalAlign"/> <display value="TableCellHorizontalAlign"/> <definition value="These values are defined within the XHTML 4.0 Table Model"/> </concept> <concept> <code value="TableCellScope"/> <display value="TableCellScope"/> <definition value="These values are defined within the XHTML 4.0 Table Model"/> </concept> <concept> <code value="TableCellVerticalAlign"/> <display value="TableCellVerticalAlign"/> <definition value="These values are defined within the XHTML 4.0 Table Model"/> </concept> <concept> <code value="TableFrame"/> <display value="TableFrame"/> <definition value="These values are defined within the XHTML 4.0 Table Model"/> </concept> <concept> <code value="TableRules"/> <display value="TableRules"/> <definition value="These values are defined within the XHTML 4.0 Table Model"/> </concept> <concept> <code value="TargetAwareness"/> <display value="TargetAwareness"/> </concept> <concept> <code value="TelecommunicationAddressUse"/> <display value="TelecommunicationAddressUse"/> </concept> <concept> <code value="TelecommunicationCapabilities"/> <display value="TelecommunicationCapabilities"/> <definition value="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."/> </concept> <concept> <code value="TimingEvent"/> <display value="TimingEvent"/> </concept> <concept> <code value="TransmissionRelationshipTypeCode"/> <display value="TransmissionRelationshipTypeCode"/> <definition value="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."/> </concept> <concept> <code value="TribalEntityUS"/> <display value="TribalEntityUS"/> <definition value="INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS"/> </concept> <concept> <code value="TriggerEventID"/> <display value="TriggerEventID"/> <definition value="Description:Trigger Event ID as published in the standard."/> </concept> <concept> <code value="UC"/> <display value="UCDS"/> <definition value="Uniform Clinical Data Systems. Ms. Michael McMullan, Office of Peer Review Health Care Finance Administration, The Meadows East Bldg., 6325 Security Blvd., Baltimore, MD 21207; (301) 966 6851."/> </concept> <concept> <code value="UCUM"/> <display value="UCUM"/> <definition value="Unified Code for Units of Measure"/> </concept> <concept> <code value="UMD"/> <display value="MDNS"/> <definition value="Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone: 215-825-6000, Fax: 215-834-1275."/> </concept> <concept> <code value="UML"/> <display value="Unified Medical Language"/> <definition value="National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894."/> </concept> <concept> <code value="UnitsOfMeasure"/> <display value="UnitsOfMeasureCaseInsensitive"/> </concept> <concept> <code value="UPC"/> <display value="Universal Product Code"/> <definition value="The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458; (513) 435 3070"/> </concept> <concept> <code value="URLScheme"/> <display value="URLScheme"/> <definition value="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."/> </concept> <concept> <code value="VaccineManufacturer"/> <display value="VaccineManufacturer"/> <definition value="The manufacturer of a vaccine."/> </concept> <concept> <code value="VaccineType"/> <display value="VaccineType"/> <definition value="The kind of vaccine."/> </concept> <concept> <code value="VocabularyDomainQualifier"/> <display value="VocabularyDomainQualifier"/> <definition value="Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain."/> </concept> <concept> <code value="W1-W2"/> <display value="WHO rec# drug codes"/> <definition value="World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2."/> </concept> <concept> <code value="W4"/> <display value="WHO rec# code with ASTM extension"/> <definition value="With ASTM extensions (see Implementation Guide), the WHO codes can be used to report serum (and other) levels, patient compliance with drug usage instructions, average daily doses and more (see Appendix X1 the Implementation Guide)."/> </concept> <concept> <code value="WC"/> <display value="WHO ATC"/> <definition value="WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above."/> </concept> </define> </ValueSet>
© HL7.org 2011+. FHIR DSTU (v0.0.82.2943) generated on Tue, Sep 30, 2014 18:10+1000.
Links:
What's a DSTU? |
Version History |
|
Propose a change