2.16.840.1.113883.5.22/static-2012-07-24: Unterschied zwischen den Versionen

Aus Hl7wiki
Wechseln zu: Navigation, Suche
(Automated TermBot page content)
(Automated TermBot page content)
Zeile 20: Zeile 20:
 
|0-L
 
|0-L
 
|'''AS4'''
 
|'''AS4'''
|<font color="grey">(en-US)</font> ASTM E1238/ E1467 Universal
+
|[[Datei:EN-US.png]]ASTM E1238/ E1467 Universal
 
| colspan="2" |<p>American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467).</p>
 
| colspan="2" |<p>American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ACR'''
 
|'''ACR'''
|<font color="grey">(en-US)</font> American College of Radiology finding codes
+
|[[Datei:EN-US.png]]American College of Radiology finding codes
 
| colspan="2" |<p>Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA.</p>
 
| colspan="2" |<p>Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ATC'''
 
|'''ATC'''
|<font color="grey">(en-US)</font> American Type Culture Collection
+
|[[Datei:EN-US.png]]American Type Culture Collection
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AS4E'''
 
|'''AS4E'''
|<font color="grey">(en-US)</font> AS4 Neurophysiology Codes
+
|[[Datei:EN-US.png]]AS4 Neurophysiology Codes
 
| colspan="2" |<p>ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2.</p>
 
| colspan="2" |<p>ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CDS'''
 
|'''CDS'''
|<font color="grey">(en-US)</font> CDC Surveillance
+
|[[Datei:EN-US.png]]CDC Surveillance
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CD2'''
 
|'''CD2'''
|<font color="grey">(en-US)</font> CDT-2 Codes
+
|[[Datei:EN-US.png]]CDT-2 Codes
 
| colspan="2" |<p>American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611.</p>
 
| colspan="2" |<p>American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CE'''
 
|'''CE'''
|<font color="grey">(en-US)</font> CEN ECG diagnostic codes
+
|[[Datei:EN-US.png]]CEN ECG diagnostic codes
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CLP'''
 
|'''CLP'''
|<font color="grey">(en-US)</font> CLIP
+
|[[Datei:EN-US.png]]CLIP
 
| colspan="2" |<p>Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports.</p>
 
| colspan="2" |<p>Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''C4'''
 
|'''C4'''
|<font color="grey">(en-US)</font> CPT-4
+
|[[Datei:EN-US.png]]CPT-4
 
| colspan="2" |<p>American Medical Association, P.O. Box 10946, Chicago IL 60610.</p>
 
| colspan="2" |<p>American Medical Association, P.O. Box 10946, Chicago IL 60610.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''C5'''
 
|'''C5'''
|<font color="grey">(en-US)</font> CPT-5
+
|[[Datei:EN-US.png]]CPT-5
 
| colspan="2" |<p>American Medical Association, P.O. Box 10946, Chicago IL 60610.</p>
 
| colspan="2" |<p>American Medical Association, P.O. Box 10946, Chicago IL 60610.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DCL'''
 
|'''DCL'''
|<font color="grey">(en-US)</font> DICOM Class Label
+
|[[Datei:EN-US.png]]DICOM Class Label
 
| colspan="2" |<p>From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034</p>
 
| colspan="2" |<p>From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DCM'''
 
|'''DCM'''
|<font color="grey">(en-US)</font> DICOM modality codes
+
|[[Datei:EN-US.png]]DICOM modality codes
 
| colspan="2" |<p>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,</p>
 
| colspan="2" |<p>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,</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DQL'''
 
|'''DQL'''
|<font color="grey">(en-US)</font> DICOM Query Label
+
|[[Datei:EN-US.png]]DICOM Query Label
 
| colspan="2" |<p>HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI.</p>
 
| colspan="2" |<p>HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ENZC'''
 
|'''ENZC'''
|<font color="grey">(en-US)</font> Enzyme Codes
+
|[[Datei:EN-US.png]]Enzyme Codes
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''E'''
 
|'''E'''
|<font color="grey">(en-US)</font> EUCLIDES
+
|[[Datei:EN-US.png]]EUCLIDES
 
| colspan="2" |<p>Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.</p>
 
| colspan="2" |<p>Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''E5'''
 
|'''E5'''
|<font color="grey">(en-US)</font> Euclides quantity codes
+
|[[Datei:EN-US.png]]Euclides quantity codes
 
| colspan="2" |<p>Available from Euclides Foundation International nv (see above)</p>
 
| colspan="2" |<p>Available from Euclides Foundation International nv (see above)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''E6'''
 
|'''E6'''
|<font color="grey">(en-US)</font> Euclides Lab method codes
+
|[[Datei:EN-US.png]]Euclides Lab method codes
 
| colspan="2" |<p>Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.</p>
 
| colspan="2" |<p>Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''E7'''
 
|'''E7'''
|<font color="grey">(en-US)</font> Euclides Lab equipment codes
+
|[[Datei:EN-US.png]]Euclides Lab equipment codes
 
| colspan="2" |<p>Available from Euclides Foundation International nv (see above)</p>
 
| colspan="2" |<p>Available from Euclides Foundation International nv (see above)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''FDK'''
 
|'''FDK'''
|<font color="grey">(en-US)</font> FDA K10
+
|[[Datei:EN-US.png]]FDA K10
 
| colspan="2" |<p>Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes).</p>
 
| colspan="2" |<p>Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HPC'''
 
|'''HPC'''
|<font color="grey">(en-US)</font> HCFA Procedure Codes (HCPCS)
+
|[[Datei:EN-US.png]]HCFA Procedure Codes (HCPCS)
 
| colspan="2" |<p>Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) modifiers.</p>
 
| colspan="2" |<p>Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) modifiers.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HI'''
 
|'''HI'''
|<font color="grey">(en-US)</font> Health Outcomes
+
|[[Datei:EN-US.png]]Health Outcomes
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HB'''
 
|'''HB'''
|<font color="grey">(en-US)</font> HIBCC
+
|[[Datei:EN-US.png]]HIBCC
 
| colspan="2" |<p>Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018.</p>
 
| colspan="2" |<p>Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HHC'''
 
|'''HHC'''
|<font color="grey">(en-US)</font> Home Health Care
+
|[[Datei:EN-US.png]]Home Health Care
 
| colspan="2" |<p>Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC.</p>
 
| colspan="2" |<p>Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ICS'''
 
|'''ICS'''
|<font color="grey">(en-US)</font> ICCS
+
|[[Datei:EN-US.png]]ICCS
 
| colspan="2" |<p>Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105.</p>
 
| colspan="2" |<p>Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''I9C'''
 
|'''I9C'''
|<font color="grey">(en-US)</font> ICD-9CM
+
|[[Datei:EN-US.png]]ICD-9CM
 
| colspan="2" |<p>Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests).</p>
 
| colspan="2" |<p>Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''I9'''
 
|'''I9'''
|<font color="grey">(en-US)</font> ICD9
+
|[[Datei:EN-US.png]]ICD9
 
| colspan="2" |<p>World Health Publications, Albany, NY.</p>
 
| colspan="2" |<p>World Health Publications, Albany, NY.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''I10P'''
 
|'''I10P'''
|<font color="grey">(en-US)</font> ICD-10 Procedure Codes
+
|[[Datei:EN-US.png]]ICD-10 Procedure Codes
 
| colspan="2" |<p>Procedure Coding System (ICD-10-PCS). See http://www/hcfa.gov/stats/icd10.icd10.htm for more information.</p>
 
| colspan="2" |<p>Procedure Coding System (ICD-10-PCS). See http://www/hcfa.gov/stats/icd10.icd10.htm for more information.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''I10'''
 
|'''I10'''
|<font color="grey">(en-US)</font> ICD-10
+
|[[Datei:EN-US.png]]ICD-10
 
| colspan="2" |<p>World Health Publications, Albany, NY.</p>
 
| colspan="2" |<p>World Health Publications, Albany, NY.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ICDO'''
 
|'''ICDO'''
|<font color="grey">(en-US)</font> International Classification of Diseases for Oncology
+
|[[Datei:EN-US.png]]International Classification of Diseases for Oncology
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IC2'''
 
|'''IC2'''
|<font color="grey">(en-US)</font> ICHPPC-2
+
|[[Datei:EN-US.png]]ICHPPC-2
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ICSD'''
 
|'''ICSD'''
|<font color="grey">(en-US)</font> International Classification of Sleep Disorders
+
|[[Datei:EN-US.png]]International Classification of Sleep Disorders
 
| colspan="2" |<p>International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902</p>
 
| colspan="2" |<p>International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IBT'''
 
|'''IBT'''
|<font color="grey">(en-US)</font> ISBT
+
|[[Datei:EN-US.png]]ISBT
 
| colspan="2" |<p>International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169.</p>
 
| colspan="2" |<p>International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IUPP'''
 
|'''IUPP'''
|<font color="grey">(en-US)</font> IUPAC/IFCC Property Codes
+
|[[Datei:EN-US.png]]IUPAC/IFCC Property Codes
 
| colspan="2" |<p>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/</p>
 
| colspan="2" |<p>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/</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IUPC'''
 
|'''IUPC'''
|<font color="grey">(en-US)</font> IUPAC/IFCC Component Codes
+
|[[Datei:EN-US.png]]IUPAC/IFCC Component Codes
 
| colspan="2" |<p>Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP.</p>
 
| colspan="2" |<p>Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''JC8'''
 
|'''JC8'''
|<font color="grey">(en-US)</font> Japanese Chemistry
+
|[[Datei:EN-US.png]]Japanese Chemistry
 
| colspan="2" |<p>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)</p>
 
| colspan="2" |<p>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)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LN'''
 
|'''LN'''
|<font color="grey">(en-US)</font> Logical Observation Identifier Names and Codes (LOINC)
+
|[[Datei:EN-US.png]]Logical Observation Identifier Names and Codes (LOINC)
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NIC'''
 
|'''NIC'''
|<font color="grey">(en-US)</font> Nursing Intervention Classification
+
|[[Datei:EN-US.png]]Nursing Intervention Classification
 
| colspan="2" |<p>Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa</p>
 
| colspan="2" |<p>Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''OHA'''
 
|'''OHA'''
|<font color="grey">(en-US)</font> Omaha System
+
|[[Datei:EN-US.png]]Omaha System
 
| colspan="2" |<p>Omaha Visiting Nurse Association, Omaha, NB.</p>
 
| colspan="2" |<p>Omaha Visiting Nurse Association, Omaha, NB.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NDA'''
 
|'''NDA'''
|<font color="grey">(en-US)</font> NANDA
+
|[[Datei:EN-US.png]]NANDA
 
| colspan="2" |<p>North American Nursing Diagnosis Association, Philadelphia, PA.</p>
 
| colspan="2" |<p>North American Nursing Diagnosis Association, Philadelphia, PA.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''POS'''
 
|'''POS'''
|<font color="grey">(en-US)</font> POS Codes
+
|[[Datei:EN-US.png]]POS Codes
 
| colspan="2" |<p>HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm).</p>
 
| colspan="2" |<p>HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RC'''
 
|'''RC'''
|<font color="grey">(en-US)</font> Read Classification
+
|[[Datei:EN-US.png]]Read Classification
 
| colspan="2" |<p>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).</p>
 
| colspan="2" |<p>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).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SNM'''
 
|'''SNM'''
|<font color="grey">(en-US)</font> Systemized Nomenclature of Medicine (SNOMED)
+
|[[Datei:EN-US.png]]Systemized Nomenclature of Medicine (SNOMED)
 
| colspan="2" |<p>Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL.</p>
 
| colspan="2" |<p>Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SNM3'''
 
|'''SNM3'''
|<font color="grey">(en-US)</font> SNOMED International
+
|[[Datei:EN-US.png]]SNOMED International
 
| colspan="2" |<p>SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034..</p>
 
| colspan="2" |<p>SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034..</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SNT'''
 
|'''SNT'''
|<font color="grey">(en-US)</font> SNOMED topology codes (anatomic sites)
+
|[[Datei:EN-US.png]]SNOMED topology codes (anatomic sites)
 
| colspan="2" |<p>College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034.</p>
 
| colspan="2" |<p>College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SDM'''
 
|'''SDM'''
|<font color="grey">(en-US)</font> SNOMED- DICOM Microglossary
+
|[[Datei:EN-US.png]]SNOMED- DICOM Microglossary
 
| colspan="2" |<p>College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM).</p>
 
| colspan="2" |<p>College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UC'''
 
|'''UC'''
|<font color="grey">(en-US)</font> UCDS
+
|[[Datei:EN-US.png]]UCDS
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UPC'''
 
|'''UPC'''
|<font color="grey">(en-US)</font> Universal Product Code
+
|[[Datei:EN-US.png]]Universal Product Code
 
| colspan="2" |<p>The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458; (513) 435 3070</p>
 
| colspan="2" |<p>The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458; (513) 435 3070</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UML'''
 
|'''UML'''
|<font color="grey">(en-US)</font> Unified Medical Language
+
|[[Datei:EN-US.png]]Unified Medical Language
 
| colspan="2" |<p>National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894.</p>
 
| colspan="2" |<p>National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CDCA'''
 
|'''CDCA'''
|<font color="grey">(en-US)</font> CDC Analyte Codes
+
|[[Datei:EN-US.png]]CDC Analyte Codes
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CDCM'''
 
|'''CDCM'''
|<font color="grey">(en-US)</font> CDC Methods/Instruments Codes
+
|[[Datei:EN-US.png]]CDC Methods/Instruments Codes
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CVX'''
 
|'''CVX'''
|<font color="grey">(en-US)</font> CDC Vaccine Codes
+
|[[Datei:EN-US.png]]CDC Vaccine Codes
 
| colspan="2" |<p>National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333</p>
 
| colspan="2" |<p>National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MVX'''
 
|'''MVX'''
|<font color="grey">(en-US)</font> CDC Vaccine Manufacturer Codes
+
|[[Datei:EN-US.png]]CDC Vaccine Manufacturer Codes
 
| colspan="2" |<p>National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333</p>
 
| colspan="2" |<p>National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CAS'''
 
|'''CAS'''
|<font color="grey">(en-US)</font> Chemical abstract codes
+
|[[Datei:EN-US.png]]Chemical abstract codes
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CST'''
 
|'''CST'''
|<font color="grey">(en-US)</font> COSTART
+
|[[Datei:EN-US.png]]COSTART
 
| colspan="2" |<p>International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD.</p>
 
| colspan="2" |<p>International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''FDDX'''
 
|'''FDDX'''
|<font color="grey">(en-US)</font> First DataBank Diagnostic Codes
+
|[[Datei:EN-US.png]]First DataBank Diagnostic Codes
 
| colspan="2" |<p>Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC.</p>
 
| colspan="2" |<p>Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''FDDC'''
 
|'''FDDC'''
|<font color="grey">(en-US)</font> First DataBank Drug Codes
+
|[[Datei:EN-US.png]]First DataBank Drug Codes
 
| colspan="2" |<p>National Drug Data File. Proprietary product of First DataBank, Inc. (800) 633-3453, or http://www.firstdatabank.com.</p>
 
| colspan="2" |<p>National Drug Data File. Proprietary product of First DataBank, Inc. (800) 633-3453, or http://www.firstdatabank.com.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MDDX'''
 
|'''MDDX'''
|<font color="grey">(en-US)</font> Medispan Diagnostic Codes
+
|[[Datei:EN-US.png]]Medispan Diagnostic Codes
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MEDX'''
 
|'''MEDX'''
|<font color="grey">(en-US)</font> Medical Economics Diagnostic Codes
+
|[[Datei:EN-US.png]]Medical Economics Diagnostic Codes
 
| colspan="2" |<p>Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.</p>
 
| colspan="2" |<p>Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MEDC'''
 
|'''MEDC'''
|<font color="grey">(en-US)</font> Medical Economics Drug Codes
+
|[[Datei:EN-US.png]]Medical Economics Drug Codes
 
| colspan="2" |<p>Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.</p>
 
| colspan="2" |<p>Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MGPI'''
 
|'''MGPI'''
|<font color="grey">(en-US)</font> Medispan GPI
+
|[[Datei:EN-US.png]]Medispan GPI
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NDC'''
 
|'''NDC'''
|<font color="grey">(en-US)</font> National drug codes
+
|[[Datei:EN-US.png]]National drug codes
 
| colspan="2" |<p>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.)</p>
 
| colspan="2" |<p>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.)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MEDR'''
 
|'''MEDR'''
|<font color="grey">(en-US)</font> Medical Dictionary for Drug Regulatory Affairs (MEDRA)
+
|[[Datei:EN-US.png]]Medical Dictionary for Drug Regulatory Affairs (MEDRA)
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''W1-W2'''
 
|'''W1-W2'''
|<font color="grey">(en-US)</font> WHO rec# drug codes
+
|[[Datei:EN-US.png]]WHO rec# drug codes
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''W4'''
 
|'''W4'''
|<font color="grey">(en-US)</font> WHO rec# code with ASTM extension
+
|[[Datei:EN-US.png]]WHO rec# code with ASTM extension
 
| colspan="2" |<p>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).</p>
 
| colspan="2" |<p>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).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''WC'''
 
|'''WC'''
|<font color="grey">(en-US)</font> WHO ATC
+
|[[Datei:EN-US.png]]WHO ATC
 
| colspan="2" |<p>WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above.</p>
 
| colspan="2" |<p>WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ART'''
 
|'''ART'''
|<font color="grey">(en-US)</font> WHO Adverse Reaction Terms
+
|[[Datei:EN-US.png]]WHO Adverse Reaction Terms
 
| colspan="2" |<p>WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden.</p>
 
| colspan="2" |<p>WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UMD'''
 
|'''UMD'''
|<font color="grey">(en-US)</font> MDNS
+
|[[Datei:EN-US.png]]MDNS
 
| colspan="2" |<p>Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone: 215-825-6000, Fax: 215-834-1275.</p>
 
| colspan="2" |<p>Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone: 215-825-6000, Fax: 215-834-1275.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NUBC-UB92'''
 
|'''NUBC-UB92'''
|<font color="grey">(en-US)</font> National Uniform Billing Council, UB 92
+
|[[Datei:EN-US.png]]National Uniform Billing Council, UB 92
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Dentition'''
 
|'''Dentition'''
|<font color="grey">(en-US)</font> Dentition
+
|[[Datei:EN-US.png]]Dentition
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CSAID'''
 
|'''CSAID'''
|<font color="grey">(en-US)</font> CAN/CSA-Z795-96 (R2001)
+
|[[Datei:EN-US.png]]CAN/CSA-Z795-96 (R2001)
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CCI'''
 
|'''CCI'''
|<font color="grey">(en-US)</font> Canadian Classification of Health Interventions
+
|[[Datei:EN-US.png]]Canadian Classification of Health Interventions
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AcknowledgementDetailType'''
 
|'''AcknowledgementDetailType'''
|<font color="grey">(en-US)</font> Acknowledgement Detail Type
+
|[[Datei:EN-US.png]]Acknowledgement Detail Type
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MessageWaitingPriority'''
 
|'''MessageWaitingPriority'''
|<font color="grey">(en-US)</font> Message Waiting Priority
+
|[[Datei:EN-US.png]]Message Waiting Priority
 
| colspan="2" |<p>Indicates that the receiver has messages for the sender</p>
 
| colspan="2" |<p>Indicates that the receiver has messages for the sender</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EncounterAcuity'''
 
|'''EncounterAcuity'''
|<font color="grey">(en-US)</font> Encounter Acuity
+
|[[Datei:EN-US.png]]Encounter Acuity
 
| colspan="2" |<p>The level of resource intensiveness of patient care.</p>
 
| colspan="2" |<p>The level of resource intensiveness of patient care.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ISO3166-1'''
 
|'''ISO3166-1'''
|<font color="grey">(en-US)</font> ISO 3166 2 Character Country Codes
+
|[[Datei:EN-US.png]]ISO 3166 2 Character Country Codes
 
| colspan="2" |<p>Two character country codes</p>
 
| colspan="2" |<p>Two character country codes</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ISO3166-2'''
 
|'''ISO3166-2'''
|<font color="grey">(en-US)</font> ISO 3166 3 Character Country Codes
+
|[[Datei:EN-US.png]]ISO 3166 3 Character Country Codes
 
| colspan="2" |<p>Three character country codes</p>
 
| colspan="2" |<p>Three character country codes</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ISO3166-3'''
 
|'''ISO3166-3'''
|<font color="grey">(en-US)</font> ISO 3166 Numeric country Codes
+
|[[Datei:EN-US.png]]ISO 3166 Numeric country Codes
 
| colspan="2" |<p>Numeric country codes</p>
 
| colspan="2" |<p>Numeric country codes</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AdministrativeGender'''
 
|'''AdministrativeGender'''
|<font color="grey">(en-US)</font> AdministrativeGender
+
|[[Datei:EN-US.png]]AdministrativeGender
 
| colspan="2" |<p>The gender of a person used for adminstrative purposes (as opposed to clinical gender)</p>
 
| colspan="2" |<p>The gender of a person used for adminstrative purposes (as opposed to clinical gender)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActRelationshipCheckpoint'''
 
|'''ActRelationshipCheckpoint'''
|<font color="grey">(en-US)</font> ActRelationshipCheckpoint
+
|[[Datei:EN-US.png]]ActRelationshipCheckpoint
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ProcessingID'''
 
|'''ProcessingID'''
|<font color="grey">(en-US)</font> ProcessingID
+
|[[Datei:EN-US.png]]ProcessingID
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActMood'''
 
|'''ActMood'''
|<font color="grey">(en-US)</font> ActMood
+
|[[Datei:EN-US.png]]ActMood
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActRelationshipType'''
 
|'''ActRelationshipType'''
|<font color="grey">(en-US)</font> ActRelationshipType
+
|[[Datei:EN-US.png]]ActRelationshipType
 
| colspan="2" |<p>The source is an excerpt from the target.</p>
 
| colspan="2" |<p>The source is an excerpt from the target.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DataType'''
 
|'''DataType'''
|<font color="grey">(en-US)</font> DataType
+
|[[Datei:EN-US.png]]DataType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NullFlavor'''
 
|'''NullFlavor'''
|<font color="grey">(en-US)</font> NullFlavor
+
|[[Datei:EN-US.png]]NullFlavor
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CompressionAlgorithm'''
 
|'''CompressionAlgorithm'''
|<font color="grey">(en-US)</font> CompressionAlgorithm
+
|[[Datei:EN-US.png]]CompressionAlgorithm
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ProcessingMode'''
 
|'''ProcessingMode'''
|<font color="grey">(en-US)</font> ProcessingMode
+
|[[Datei:EN-US.png]]ProcessingMode
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IntegrityCheckAlgorithm'''
 
|'''IntegrityCheckAlgorithm'''
|<font color="grey">(en-US)</font> IntegrityCheckAlgorithm
+
|[[Datei:EN-US.png]]IntegrityCheckAlgorithm
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TelecommunicationAddressUse'''
 
|'''TelecommunicationAddressUse'''
|<font color="grey">(en-US)</font> TelecommunicationAddressUse
+
|[[Datei:EN-US.png]]TelecommunicationAddressUse
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PostalAddressUse'''
 
|'''PostalAddressUse'''
|<font color="grey">(en-US)</font> PostalAddressUse
+
|[[Datei:EN-US.png]]PostalAddressUse
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''OrganizationNameType'''
 
|'''OrganizationNameType'''
|<font color="grey">(en-US)</font> OrganizationNameType
+
|[[Datei:EN-US.png]]OrganizationNameType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CalendarType'''
 
|'''CalendarType'''
|<font color="grey">(en-US)</font> CalendarType
+
|[[Datei:EN-US.png]]CalendarType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryPriority'''
 
|'''QueryPriority'''
|<font color="grey">(en-US)</font> QueryPriority
+
|[[Datei:EN-US.png]]QueryPriority
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ProbabilityDistributionType'''
 
|'''ProbabilityDistributionType'''
|<font color="grey">(en-US)</font> ProbabilityDistributionType
+
|[[Datei:EN-US.png]]ProbabilityDistributionType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PeriodicIntervalOfTimeAbbreviation'''
 
|'''PeriodicIntervalOfTimeAbbreviation'''
|<font color="grey">(en-US)</font> PeriodicIntervalOfTimeAbbreviation
+
|[[Datei:EN-US.png]]PeriodicIntervalOfTimeAbbreviation
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''GTSAbbreviation'''
 
|'''GTSAbbreviation'''
|<font color="grey">(en-US)</font> GTSAbbreviation
+
|[[Datei:EN-US.png]]GTSAbbreviation
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryStatusCode'''
 
|'''QueryStatusCode'''
|<font color="grey">(en-US)</font> QueryStatusCode
+
|[[Datei:EN-US.png]]QueryStatusCode
 
| colspan="2" |<p>State attributes for Query event</p>
 
| colspan="2" |<p>State attributes for Query event</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Race'''
 
|'''Race'''
|<font color="grey">(en-US)</font> Race
+
|[[Datei:EN-US.png]]Race
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RelationalOperator'''
 
|'''RelationalOperator'''
|<font color="grey">(en-US)</font> RelationalOperator
+
|[[Datei:EN-US.png]]RelationalOperator
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AcknowledgementCondition'''
 
|'''AcknowledgementCondition'''
|<font color="grey">(en-US)</font> AcknowledgementCondition
+
|[[Datei:EN-US.png]]AcknowledgementCondition
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActInvoiceElementModifier'''
 
|'''ActInvoiceElementModifier'''
|<font color="grey">(en-US)</font> ActInvoiceElementModifier
+
|[[Datei:EN-US.png]]ActInvoiceElementModifier
 
| colspan="2" |<p>Processing consideration and clarification codes.</p>
 
| colspan="2" |<p>Processing consideration and clarification codes.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActSite'''
 
|'''ActSite'''
|<font color="grey">(en-US)</font> ActSite
+
|[[Datei:EN-US.png]]ActSite
 
| colspan="2" |<p>An anatomical location on an organism which can be the focus of an act.</p>
 
| colspan="2" |<p>An anatomical location on an organism which can be the focus of an act.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActUncertainty'''
 
|'''ActUncertainty'''
|<font color="grey">(en-US)</font> ActUncertainty
+
|[[Datei:EN-US.png]]ActUncertainty
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AmericanIndianAlaskaNativeLanguages'''
 
|'''AmericanIndianAlaskaNativeLanguages'''
|<font color="grey">(en-US)</font> AmericanIndianAlaskaNativeLanguages
+
|[[Datei:EN-US.png]]AmericanIndianAlaskaNativeLanguages
 
| colspan="2" |<p>American Indian and Alaska Native languages currently being used in the United States.</p>
 
| colspan="2" |<p>American Indian and Alaska Native languages currently being used in the United States.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Calendar'''
 
|'''Calendar'''
|<font color="grey">(en-US)</font> Calendar
+
|[[Datei:EN-US.png]]Calendar
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CommunicationFunctionType'''
 
|'''CommunicationFunctionType'''
|<font color="grey">(en-US)</font> CommunicationFunctionType
+
|[[Datei:EN-US.png]]CommunicationFunctionType
 
| colspan="2" |<p>Describes the type of communication function that the associated entity plays in the associated transmission.</p>
 
| colspan="2" |<p>Describes the type of communication function that the associated entity plays in the associated transmission.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ContextControl'''
 
|'''ContextControl'''
|<font color="grey">(en-US)</font> ContextControl
+
|[[Datei:EN-US.png]]ContextControl
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Currency'''
 
|'''Currency'''
|<font color="grey">(en-US)</font> Currency
+
|[[Datei:EN-US.png]]Currency
 
| colspan="2" |<p>The currency unit as defined in ISO 4217</p>
 
| colspan="2" |<p>The currency unit as defined in ISO 4217</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EmployeeJobClass'''
 
|'''EmployeeJobClass'''
|<font color="grey">(en-US)</font> EmployeeJobClass
+
|[[Datei:EN-US.png]]EmployeeJobClass
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RelationshipConjunction'''
 
|'''RelationshipConjunction'''
|<font color="grey">(en-US)</font> RelationshipConjunction
+
|[[Datei:EN-US.png]]RelationshipConjunction
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityCode'''
 
|'''EntityCode'''
|<font color="grey">(en-US)</font> EntityCode
+
|[[Datei:EN-US.png]]EntityCode
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityStatus'''
 
|'''EntityStatus'''
|<font color="grey">(en-US)</font> EntityStatus
+
|[[Datei:EN-US.png]]EntityStatus
 
| colspan="2" |<p>The status of an instance of the RIM Entity class.</p>
 
| colspan="2" |<p>The status of an instance of the RIM Entity class.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ManagedParticipationStatus'''
 
|'''ManagedParticipationStatus'''
|<font color="grey">(en-US)</font> ManagedParticipationStatus
+
|[[Datei:EN-US.png]]ManagedParticipationStatus
 
| colspan="2" |<p>The status of an instance of the RIM Participation class.</p>
 
| colspan="2" |<p>The status of an instance of the RIM Participation class.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ObservationValue'''
 
|'''ObservationValue'''
|<font color="grey">(en-US)</font> ObservationValue
+
|[[Datei:EN-US.png]]ObservationValue
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ParticipationMode'''
 
|'''ParticipationMode'''
|<font color="grey">(en-US)</font> ParticipationMode
+
|[[Datei:EN-US.png]]ParticipationMode
 
| colspan="2" |<p>Identifies the primary means by which an Entity participates in an Act.</p>
 
| colspan="2" |<p>Identifies the primary means by which an Entity participates in an Act.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ProcedureMethod'''
 
|'''ProcedureMethod'''
|<font color="grey">(en-US)</font> ProcedureMethod
+
|[[Datei:EN-US.png]]ProcedureMethod
 
| colspan="2" |<p>Identifies the technique used to perform a procedure.</p>
 
| colspan="2" |<p>Identifies the technique used to perform a procedure.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryQuantityUnit'''
 
|'''QueryQuantityUnit'''
|<font color="grey">(en-US)</font> QueryQuantityUnit
+
|[[Datei:EN-US.png]]QueryQuantityUnit
 
| colspan="2" |<p>Values in this domain specify the units of a query quantity limited request.</p>
 
| colspan="2" |<p>Values in this domain specify the units of a query quantity limited request.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryResponse'''
 
|'''QueryResponse'''
|<font color="grey">(en-US)</font> QueryResponse
+
|[[Datei:EN-US.png]]QueryResponse
 
| colspan="2" |<p>Values in this domain allow a query response system to return a precise response status.</p>
 
| colspan="2" |<p>Values in this domain allow a query response system to return a precise response status.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RoleStatus'''
 
|'''RoleStatus'''
|<font color="grey">(en-US)</font> RoleStatus
+
|[[Datei:EN-US.png]]RoleStatus
 
| colspan="2" |<p>The status of an instance of the RIM Role class.</p>
 
| colspan="2" |<p>The status of an instance of the RIM Role class.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SetOperator'''
 
|'''SetOperator'''
|<font color="grey">(en-US)</font> SetOperator
+
|[[Datei:EN-US.png]]SetOperator
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RoleLinkType'''
 
|'''RoleLinkType'''
|<font color="grey">(en-US)</font> RoleLinkType
+
|[[Datei:EN-US.png]]RoleLinkType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SubstanceAdminSubstitution'''
 
|'''SubstanceAdminSubstitution'''
|<font color="grey">(en-US)</font> SubstanceAdminSubstitution
+
|[[Datei:EN-US.png]]SubstanceAdminSubstitution
 
| colspan="2" |<p>Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.</p>
 
| colspan="2" |<p>Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SubstitutionCondition'''
 
|'''SubstitutionCondition'''
|<font color="grey">(en-US)</font> SubstitutionCondition
+
|[[Datei:EN-US.png]]SubstitutionCondition
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CodingRationale'''
 
|'''CodingRationale'''
|<font color="grey">(en-US)</font> CodingRationale
+
|[[Datei:EN-US.png]]CodingRationale
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PatientImportance'''
 
|'''PatientImportance'''
|<font color="grey">(en-US)</font> PatientImportance
+
|[[Datei:EN-US.png]]PatientImportance
 
| colspan="2" |<p>Patient VIP code</p>
 
| colspan="2" |<p>Patient VIP code</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ReligiousAffiliation'''
 
|'''ReligiousAffiliation'''
|<font color="grey">(en-US)</font> Religious Affiliation
+
|[[Datei:EN-US.png]]Religious Affiliation
 
| colspan="2" |<p>Assigment of spiritual faith affiliation</p>
 
| colspan="2" |<p>Assigment of spiritual faith affiliation</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EducationLevel'''
 
|'''EducationLevel'''
|<font color="grey">(en-US)</font> Education Level
+
|[[Datei:EN-US.png]]Education Level
 
| colspan="2" |<p>Years of education that a person has completed</p>
 
| colspan="2" |<p>Years of education that a person has completed</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ResponseLevel'''
 
|'''ResponseLevel'''
|<font color="grey">(en-US)</font> ResponseLevel
+
|[[Datei:EN-US.png]]ResponseLevel
 
| colspan="2" |<p>Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include</p>
 
| colspan="2" |<p>Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ResponseModality'''
 
|'''ResponseModality'''
|<font color="grey">(en-US)</font> ResponseModality
+
|[[Datei:EN-US.png]]ResponseModality
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RoleClass'''
 
|'''RoleClass'''
|<font color="grey">(en-US)</font> RoleClass
+
|[[Datei:EN-US.png]]RoleClass
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RoleCode'''
 
|'''RoleCode'''
|<font color="grey">(en-US)</font> RoleCode
+
|[[Datei:EN-US.png]]RoleCode
 
| colspan="2" |<p>Specific classification codes for further qualifying RoleClass codes.</p>
 
| colspan="2" |<p>Specific classification codes for further qualifying RoleClass codes.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RouteOfAdministration'''
 
|'''RouteOfAdministration'''
|<font color="grey">(en-US)</font> RouteOfAdministration
+
|[[Datei:EN-US.png]]RouteOfAdministration
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Sequencing'''
 
|'''Sequencing'''
|<font color="grey">(en-US)</font> Sequencing
+
|[[Datei:EN-US.png]]Sequencing
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActRelationshipJoin'''
 
|'''ActRelationshipJoin'''
|<font color="grey">(en-US)</font> ActRelationshipJoin
+
|[[Datei:EN-US.png]]ActRelationshipJoin
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SpecimenType'''
 
|'''SpecimenType'''
|<font color="grey">(en-US)</font> SpecimenType
+
|[[Datei:EN-US.png]]SpecimenType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActRelationshipSplit'''
 
|'''ActRelationshipSplit'''
|<font color="grey">(en-US)</font> ActRelationshipSplit
+
|[[Datei:EN-US.png]]ActRelationshipSplit
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TableCellHorizontalAlign'''
 
|'''TableCellHorizontalAlign'''
|<font color="grey">(en-US)</font> TableCellHorizontalAlign
+
|[[Datei:EN-US.png]]TableCellHorizontalAlign
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TableCellScope'''
 
|'''TableCellScope'''
|<font color="grey">(en-US)</font> TableCellScope
+
|[[Datei:EN-US.png]]TableCellScope
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TableCellVerticalAlign'''
 
|'''TableCellVerticalAlign'''
|<font color="grey">(en-US)</font> TableCellVerticalAlign
+
|[[Datei:EN-US.png]]TableCellVerticalAlign
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TableFrame'''
 
|'''TableFrame'''
|<font color="grey">(en-US)</font> TableFrame
+
|[[Datei:EN-US.png]]TableFrame
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TableRules'''
 
|'''TableRules'''
|<font color="grey">(en-US)</font> TableRules
+
|[[Datei:EN-US.png]]TableRules
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
| colspan="2" |<p>These values are defined within the XHTML 4.0 Table Model</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TargetAwareness'''
 
|'''TargetAwareness'''
|<font color="grey">(en-US)</font> TargetAwareness
+
|[[Datei:EN-US.png]]TargetAwareness
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TimingEvent'''
 
|'''TimingEvent'''
|<font color="grey">(en-US)</font> TimingEvent
+
|[[Datei:EN-US.png]]TimingEvent
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActStatus'''
 
|'''ActStatus'''
|<font color="grey">(en-US)</font> ActStatus
+
|[[Datei:EN-US.png]]ActStatus
 
| colspan="2" |<p>Contains the names (codes) for each of the states in the state-machine of the RIM Act class.</p>
 
| colspan="2" |<p>Contains the names (codes) for each of the states in the state-machine of the RIM Act class.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TribalEntityUS'''
 
|'''TribalEntityUS'''
|<font color="grey">(en-US)</font> TribalEntityUS
+
|[[Datei:EN-US.png]]TribalEntityUS
 
| colspan="2" |<p>INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS</p>
 
| colspan="2" |<p>INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UnitsOfMeasure'''
 
|'''UnitsOfMeasure'''
|<font color="grey">(en-US)</font> UnitsOfMeasureCaseInsensitive
+
|[[Datei:EN-US.png]]UnitsOfMeasureCaseInsensitive
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''URLScheme'''
 
|'''URLScheme'''
|<font color="grey">(en-US)</font> URLScheme
+
|[[Datei:EN-US.png]]URLScheme
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''VaccineManufacturer'''
 
|'''VaccineManufacturer'''
|<font color="grey">(en-US)</font> VaccineManufacturer
+
|[[Datei:EN-US.png]]VaccineManufacturer
 
| colspan="2" |<p>The manufacturer of a vaccine.</p>
 
| colspan="2" |<p>The manufacturer of a vaccine.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''VaccineType'''
 
|'''VaccineType'''
|<font color="grey">(en-US)</font> VaccineType
+
|[[Datei:EN-US.png]]VaccineType
 
| colspan="2" |<p>The kind of vaccine.</p>
 
| colspan="2" |<p>The kind of vaccine.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''VocabularyDomainQualifier'''
 
|'''VocabularyDomainQualifier'''
|<font color="grey">(en-US)</font> VocabularyDomainQualifier
+
|[[Datei:EN-US.png]]VocabularyDomainQualifier
 
| colspan="2" |<p>Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain.</p>
 
| colspan="2" |<p>Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AddressPartType'''
 
|'''AddressPartType'''
|<font color="grey">(en-US)</font> AddressPartType
+
|[[Datei:EN-US.png]]AddressPartType
 
| colspan="2" |<p>Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"</p>
 
| colspan="2" |<p>Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AcknowledgementType'''
 
|'''AcknowledgementType'''
|<font color="grey">(en-US)</font> AcknowledgementType
+
|[[Datei:EN-US.png]]AcknowledgementType
 
| colspan="2" |<p>Acknowledgement code as described in HL7 message processing rules.</p>
 
| colspan="2" |<p>Acknowledgement code as described in HL7 message processing rules.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MaritalStatus'''
 
|'''MaritalStatus'''
|<font color="grey">(en-US)</font> MaritalStatus
+
|[[Datei:EN-US.png]]MaritalStatus
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Charset'''
 
|'''Charset'''
|<font color="grey">(en-US)</font> Charset
+
|[[Datei:EN-US.png]]Charset
 
| colspan="2" |<p>Internet Assigned Numbers Authority (IANA) Charset Types</p>
 
| colspan="2" |<p>Internet Assigned Numbers Authority (IANA) Charset Types</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CodeSystem'''
 
|'''CodeSystem'''
|<font color="grey">(en-US)</font> CodeSystem
+
|[[Datei:EN-US.png]]CodeSystem
 
| colspan="2" |<p>Code systems used in HL7 standards.</p>
 
| colspan="2" |<p>Code systems used in HL7 standards.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ConceptGenerality'''
 
|'''ConceptGenerality'''
|<font color="grey">(en-US)</font> ConceptGenerality
+
|[[Datei:EN-US.png]]ConceptGenerality
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Confidentiality'''
 
|'''Confidentiality'''
|<font color="grey">(en-US)</font> Confidentiality
+
|[[Datei:EN-US.png]]Confidentiality
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ContainerCap'''
 
|'''ContainerCap'''
|<font color="grey">(en-US)</font> ContainerCap
+
|[[Datei:EN-US.png]]ContainerCap
 
| colspan="2" |<p>The type of cap associated with a container</p>
 
| colspan="2" |<p>The type of cap associated with a container</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ContainerSeparator'''
 
|'''ContainerSeparator'''
|<font color="grey">(en-US)</font> ContainerSeparator
+
|[[Datei:EN-US.png]]ContainerSeparator
 
| colspan="2" |<p>A material in a blood collection container that facilites the separation of of blood cells from serum or plasma</p>
 
| colspan="2" |<p>A material in a blood collection container that facilites the separation of of blood cells from serum or plasma</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityDeterminer'''
 
|'''EntityDeterminer'''
|<font color="grey">(en-US)</font> EntityDeterminer
+
|[[Datei:EN-US.png]]EntityDeterminer
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DeviceAlertLevel'''
 
|'''DeviceAlertLevel'''
|<font color="grey">(en-US)</font> DeviceAlertLevel
+
|[[Datei:EN-US.png]]DeviceAlertLevel
 
| colspan="2" |<p>Domain values for the Device.Alert_levelCode</p>
 
| colspan="2" |<p>Domain values for the Device.Alert_levelCode</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DocumentCompletion'''
 
|'''DocumentCompletion'''
|<font color="grey">(en-US)</font> DocumentCompletion
+
|[[Datei:EN-US.png]]DocumentCompletion
 
| colspan="2" |<p>Identifies the current completion state of a clinical document.</p>
 
| colspan="2" |<p>Identifies the current completion state of a clinical document.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DocumentStorage'''
 
|'''DocumentStorage'''
|<font color="grey">(en-US)</font> DocumentStorage
+
|[[Datei:EN-US.png]]DocumentStorage
 
| colspan="2" |<p>Identifies the storage status of a document.</p>
 
| colspan="2" |<p>Identifies the storage status of a document.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EditStatus'''
 
|'''EditStatus'''
|<font color="grey">(en-US)</font> EditStatus
+
|[[Datei:EN-US.png]]EditStatus
 
| colspan="2" |<p>The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database.</p>
 
| colspan="2" |<p>The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EncounterAccident'''
 
|'''EncounterAccident'''
|<font color="grey">(en-US)</font> EncounterAccident
+
|[[Datei:EN-US.png]]EncounterAccident
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EncounterAdmissionSource'''
 
|'''EncounterAdmissionSource'''
|<font color="grey">(en-US)</font> EncounterAdmissionSource
+
|[[Datei:EN-US.png]]EncounterAdmissionSource
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EncounterReferralSource'''
 
|'''EncounterReferralSource'''
|<font color="grey">(en-US)</font> EncounterReferralSource
+
|[[Datei:EN-US.png]]EncounterReferralSource
 
| colspan="2" |<p>This domain is defined in UB92 and applies to US realm only</p>
 
| colspan="2" |<p>This domain is defined in UB92 and applies to US realm only</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActCode'''
 
|'''ActCode'''
|<font color="grey">(en-US)</font> ActCode
+
|[[Datei:EN-US.png]]ActCode
 
| colspan="2" |<p>The table that provides the detailed or rich codes for the Act classes.</p>
 
| colspan="2" |<p>The table that provides the detailed or rich codes for the Act classes.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EncounterSpecialCourtesy'''
 
|'''EncounterSpecialCourtesy'''
|<font color="grey">(en-US)</font> EncounterSpecialCourtesy
+
|[[Datei:EN-US.png]]EncounterSpecialCourtesy
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityClass'''
 
|'''EntityClass'''
|<font color="grey">(en-US)</font> EntityClass
+
|[[Datei:EN-US.png]]EntityClass
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityHandling'''
 
|'''EntityHandling'''
|<font color="grey">(en-US)</font> EntityHandling
+
|[[Datei:EN-US.png]]EntityHandling
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNamePartQualifier'''
 
|'''EntityNamePartQualifier'''
|<font color="grey">(en-US)</font> EntityNamePartQualifier
+
|[[Datei:EN-US.png]]EntityNamePartQualifier
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNamePartType'''
 
|'''EntityNamePartType'''
|<font color="grey">(en-US)</font> EntityNamePartType
+
|[[Datei:EN-US.png]]EntityNamePartType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNameUse'''
 
|'''EntityNameUse'''
|<font color="grey">(en-US)</font> EntityNameUse
+
|[[Datei:EN-US.png]]EntityNameUse
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityRisk'''
 
|'''EntityRisk'''
|<font color="grey">(en-US)</font> EntityRisk
+
|[[Datei:EN-US.png]]EntityRisk
 
| colspan="2" |<p>The vocabulary table for the Entity.riskCode attribute</p>
 
| colspan="2" |<p>The vocabulary table for the Entity.riskCode attribute</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EquipmentAlertLevel'''
 
|'''EquipmentAlertLevel'''
|<font color="grey">(en-US)</font> EquipmentAlertLevel
+
|[[Datei:EN-US.png]]EquipmentAlertLevel
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''Ethnicity'''
 
|'''Ethnicity'''
|<font color="grey">(en-US)</font> Ethnicity
+
|[[Datei:EN-US.png]]Ethnicity
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''GenderStatus'''
 
|'''GenderStatus'''
|<font color="grey">(en-US)</font> GenderStatus
+
|[[Datei:EN-US.png]]GenderStatus
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HealthcareProviderTaxonomyHIPAA'''
 
|'''HealthcareProviderTaxonomyHIPAA'''
|<font color="grey">(en-US)</font> HealthcareProviderTaxonomyHIPAA
+
|[[Datei:EN-US.png]]HealthcareProviderTaxonomyHIPAA
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7CommitteeIDInRIM'''
 
|'''HL7CommitteeIDInRIM'''
|<font color="grey">(en-US)</font> HL7CommitteeIDInRIM
+
|[[Datei:EN-US.png]]HL7CommitteeIDInRIM
 
| colspan="2" |<p>Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables.</p>
 
| colspan="2" |<p>Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7ConformanceInclusion'''
 
|'''HL7ConformanceInclusion'''
|<font color="grey">(en-US)</font> HL7ConformanceInclusion
+
|[[Datei:EN-US.png]]HL7ConformanceInclusion
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7DefinedRoseProperty'''
 
|'''HL7DefinedRoseProperty'''
|<font color="grey">(en-US)</font> HL7DefinedRoseProperty
+
|[[Datei:EN-US.png]]HL7DefinedRoseProperty
 
| colspan="2" |<p>The property Ids that HL7 has defined for customizing Rational Rose.</p>
 
| colspan="2" |<p>The property Ids that HL7 has defined for customizing Rational Rose.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7UpdateMode'''
 
|'''HL7UpdateMode'''
|<font color="grey">(en-US)</font> HL7UpdateMode
+
|[[Datei:EN-US.png]]HL7UpdateMode
 
| colspan="2" |<p>The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.</p>
 
| colspan="2" |<p>The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HtmlLinkType'''
 
|'''HtmlLinkType'''
|<font color="grey">(en-US)</font> HtmlLinkType
+
|[[Datei:EN-US.png]]HtmlLinkType
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActClass'''
 
|'''ActClass'''
|<font color="grey">(en-US)</font> ActClass
+
|[[Datei:EN-US.png]]ActClass
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LanguageAbilityMode'''
 
|'''LanguageAbilityMode'''
|<font color="grey">(en-US)</font> LanguageAbilityMode
+
|[[Datei:EN-US.png]]LanguageAbilityMode
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LanguageAbilityProficiency'''
 
|'''LanguageAbilityProficiency'''
|<font color="grey">(en-US)</font> LanguageAbilityProficiency
+
|[[Datei:EN-US.png]]LanguageAbilityProficiency
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LivingArrangement'''
 
|'''LivingArrangement'''
|<font color="grey">(en-US)</font> LivingArrangement
+
|[[Datei:EN-US.png]]LivingArrangement
 
| colspan="2" |<p>A code depicting the living arrangements of a person</p>
 
| colspan="2" |<p>A code depicting the living arrangements of a person</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LocalMarkupIgnore'''
 
|'''LocalMarkupIgnore'''
|<font color="grey">(en-US)</font> LocalMarkupIgnore
+
|[[Datei:EN-US.png]]LocalMarkupIgnore
 
| colspan="2" |<p>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"</p>
 
| colspan="2" |<p>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"</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''LocalRemoteControlState'''
 
|'''LocalRemoteControlState'''
|<font color="grey">(en-US)</font> LocalRemoteControlState
+
|[[Datei:EN-US.png]]LocalRemoteControlState
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MapRelationship'''
 
|'''MapRelationship'''
|<font color="grey">(en-US)</font> MapRelationship
+
|[[Datei:EN-US.png]]MapRelationship
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActPriority'''
 
|'''ActPriority'''
|<font color="grey">(en-US)</font> ActPriority
+
|[[Datei:EN-US.png]]ActPriority
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MaterialType'''
 
|'''MaterialType'''
|<font color="grey">(en-US)</font> MaterialType
+
|[[Datei:EN-US.png]]MaterialType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MDFAttributeType'''
 
|'''MDFAttributeType'''
|<font color="grey">(en-US)</font> MDFAttributeType
+
|[[Datei:EN-US.png]]MDFAttributeType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MdfHmdMetSourceType'''
 
|'''MdfHmdMetSourceType'''
|<font color="grey">(en-US)</font> MdfHmdMetSourceType
+
|[[Datei:EN-US.png]]MdfHmdMetSourceType
 
| colspan="2" |<p>Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD.</p>
 
| colspan="2" |<p>Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MdfHmdRowType'''
 
|'''MdfHmdRowType'''
|<font color="grey">(en-US)</font> MdfHmdRowType
+
|[[Datei:EN-US.png]]MdfHmdRowType
 
| colspan="2" |<p>The row type codes for the tabular representation of a Hierarchical Message Description.</p>
 
| colspan="2" |<p>The row type codes for the tabular representation of a Hierarchical Message Description.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MdfRmimRowType'''
 
|'''MdfRmimRowType'''
|<font color="grey">(en-US)</font> MdfRmimRowType
+
|[[Datei:EN-US.png]]MdfRmimRowType
 
| colspan="2" |<p>The row types for the tabular representation of an R-MIM.</p>
 
| colspan="2" |<p>The row types for the tabular representation of an R-MIM.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MDFSubjectAreaPrefix'''
 
|'''MDFSubjectAreaPrefix'''
|<font color="grey">(en-US)</font> MDFSubjectAreaPrefix
+
|[[Datei:EN-US.png]]MDFSubjectAreaPrefix
 
| colspan="2" |<p>The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area.</p>
 
| colspan="2" |<p>The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MediaType'''
 
|'''MediaType'''
|<font color="grey">(en-US)</font> MediaType
+
|[[Datei:EN-US.png]]MediaType
 
| colspan="2" |<p>Internet Assigned Numbers Authority (IANA) Mime Media Types</p>
 
| colspan="2" |<p>Internet Assigned Numbers Authority (IANA) Mime Media Types</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActReason'''
 
|'''ActReason'''
|<font color="grey">(en-US)</font> ActReason
+
|[[Datei:EN-US.png]]ActReason
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MessageCondition'''
 
|'''MessageCondition'''
|<font color="grey">(en-US)</font> MessageCondition
+
|[[Datei:EN-US.png]]MessageCondition
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ModifyIndicator'''
 
|'''ModifyIndicator'''
|<font color="grey">(en-US)</font> ModifyIndicator
+
|[[Datei:EN-US.png]]ModifyIndicator
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ObservationInterpretation'''
 
|'''ObservationInterpretation'''
|<font color="grey">(en-US)</font> ObservationInterpretation
+
|[[Datei:EN-US.png]]ObservationInterpretation
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ObservationMethod'''
 
|'''ObservationMethod'''
|<font color="grey">(en-US)</font> ObservationMethod
+
|[[Datei:EN-US.png]]ObservationMethod
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''OrderableDrugForm'''
 
|'''OrderableDrugForm'''
|<font color="grey">(en-US)</font> OrderableDrugForm
+
|[[Datei:EN-US.png]]OrderableDrugForm
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ParameterizedDataType'''
 
|'''ParameterizedDataType'''
|<font color="grey">(en-US)</font> ParameterizedDataType
+
|[[Datei:EN-US.png]]ParameterizedDataType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ParticipationFunction'''
 
|'''ParticipationFunction'''
|<font color="grey">(en-US)</font> ParticipationFunction
+
|[[Datei:EN-US.png]]ParticipationFunction
 
| colspan="2" |<p>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).</p>
 
| colspan="2" |<p>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).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ParticipationSignature'''
 
|'''ParticipationSignature'''
|<font color="grey">(en-US)</font> ParticipationSignature
+
|[[Datei:EN-US.png]]ParticipationSignature
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CalendarCycle'''
 
|'''CalendarCycle'''
|<font color="grey">(en-US)</font> CalendarCycle
+
|[[Datei:EN-US.png]]CalendarCycle
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ParticipationType'''
 
|'''ParticipationType'''
|<font color="grey">(en-US)</font> ParticipationType
+
|[[Datei:EN-US.png]]ParticipationType
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PaymentTerms'''
 
|'''PaymentTerms'''
|<font color="grey">(en-US)</font> PaymentTerms
+
|[[Datei:EN-US.png]]PaymentTerms
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PersonDisabilityType'''
 
|'''PersonDisabilityType'''
|<font color="grey">(en-US)</font> PersonDisabilityType
+
|[[Datei:EN-US.png]]PersonDisabilityType
 
| colspan="2" |<p>A code identifying a person's disability.</p>
 
| colspan="2" |<p>A code identifying a person's disability.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MIME'''
 
|'''MIME'''
|<font color="grey">(en-US)</font> MIME
+
|[[Datei:EN-US.png]]MIME
 
| colspan="2" |<p>IETF MIME media types</p>
 
| colspan="2" |<p>IETF MIME media types</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NOC'''
 
|'''NOC'''
|<font color="grey">(en-US)</font> NOC
+
|[[Datei:EN-US.png]]NOC
 
| colspan="2" |<p>NOC - Nursing Outcome Codes</p>
 
| colspan="2" |<p>NOC - Nursing Outcome Codes</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CAMNCVS'''
 
|'''CAMNCVS'''
|<font color="grey">(en-US)</font> CAMNCVS
+
|[[Datei:EN-US.png]]CAMNCVS
 
| colspan="2" |<p>CAM & Nursing Coding Vocabulary Set</p>
 
| colspan="2" |<p>CAM & Nursing Coding Vocabulary Set</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''PNDS'''
 
|'''PNDS'''
|<font color="grey">(en-US)</font> Perioperative Nursing Data Set
+
|[[Datei:EN-US.png]]Perioperative Nursing Data Set
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NMMDS'''
 
|'''NMMDS'''
|<font color="grey">(en-US)</font> Nursing Management Minimum Data Set
+
|[[Datei:EN-US.png]]Nursing Management Minimum Data Set
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MDC'''
 
|'''MDC'''
|<font color="grey">(en-US)</font> ISO 11073-10101 Health informatics - Point-of-care
+
|[[Datei:EN-US.png]]ISO 11073-10101 Health informatics - Point-of-care
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ABCcodes'''
 
|'''ABCcodes'''
|<font color="grey">(en-US)</font> ABCcodes
+
|[[Datei:EN-US.png]]ABCcodes
 
| colspan="2" |<p>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. .</p>
 
| colspan="2" |<p>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. .</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MEDCIN'''
 
|'''MEDCIN'''
|<font color="grey">(en-US)</font> MEDCIN
+
|[[Datei:EN-US.png]]MEDCIN
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MULTUM'''
 
|'''MULTUM'''
|<font color="grey">(en-US)</font> Multum Lexicon
+
|[[Datei:EN-US.png]]Multum Lexicon
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RCFB'''
 
|'''RCFB'''
|<font color="grey">(en-US)</font> The Read Codes Four Byte Set:
+
|[[Datei:EN-US.png]]The Read Codes Four Byte Set:
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RCV2'''
 
|'''RCV2'''
|<font color="grey">(en-US)</font> The Read Codes Version 2
+
|[[Datei:EN-US.png]]The Read Codes Version 2
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NAACCR'''
 
|'''NAACCR'''
|<font color="grey">(en-US)</font> NAACCR
+
|[[Datei:EN-US.png]]NAACCR
 
| colspan="2" |<p>NAACCR Cancer Registry</p>
 
| colspan="2" |<p>NAACCR Cancer Registry</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''UCUM'''
 
|'''UCUM'''
|<font color="grey">(en-US)</font> UCUM
+
|[[Datei:EN-US.png]]UCUM
 
| colspan="2" |<p>Unified Code for Units of Measure</p>
 
| colspan="2" |<p>Unified Code for Units of Measure</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IETF1766'''
 
|'''IETF1766'''
|<font color="grey">(en-US)</font> IETF RFC 1766
+
|[[Datei:EN-US.png]]IETF RFC 1766
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NAICS'''
 
|'''NAICS'''
|<font color="grey">(en-US)</font> North American Industry Classification System
+
|[[Datei:EN-US.png]]North American Industry Classification System
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ISO4217'''
 
|'''ISO4217'''
|<font color="grey">(en-US)</font> ISO4217
+
|[[Datei:EN-US.png]]ISO4217
 
| colspan="2" |<p>ISO 4217 currency code</p>
 
| colspan="2" |<p>ISO 4217 currency code</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''CodeSystemType'''
 
|'''CodeSystemType'''
|<font color="grey">(en-US)</font> HL7 Code System Type
+
|[[Datei:EN-US.png]]HL7 Code System Type
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ConceptStatus'''
 
|'''ConceptStatus'''
|<font color="grey">(en-US)</font> HL7 Coded Concept Status
+
|[[Datei:EN-US.png]]HL7 Coded Concept Status
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ConceptProperty'''
 
|'''ConceptProperty'''
|<font color="grey">(en-US)</font> HL7 Value Set and Coded Concept Property Codes
+
|[[Datei:EN-US.png]]HL7 Value Set and Coded Concept Property Codes
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ConceptCodeRelationship'''
 
|'''ConceptCodeRelationship'''
|<font color="grey">(en-US)</font> Possible Concept Code Relationships
+
|[[Datei:EN-US.png]]Possible Concept Code Relationships
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7StandardVersionCode'''
 
|'''HL7StandardVersionCode'''
|<font color="grey">(en-US)</font> HL7StandardVersionCode
+
|[[Datei:EN-US.png]]HL7StandardVersionCode
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ICD-10-CA'''
 
|'''ICD-10-CA'''
|<font color="grey">(en-US)</font> CanadianDiagnosisCodesICD-10-CA
+
|[[Datei:EN-US.png]]CanadianDiagnosisCodesICD-10-CA
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HL7ITSVersionCode'''
 
|'''HL7ITSVersionCode'''
|<font color="grey">(en-US)</font> HL7 ITS Version Code
+
|[[Datei:EN-US.png]]HL7 ITS Version Code
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''NUCCProviderCodes'''
 
|'''NUCCProviderCodes'''
|<font color="grey">(en-US)</font> NUCC Health Care Provider Taxonomy
+
|[[Datei:EN-US.png]]NUCC Health Care Provider Taxonomy
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''StyleType'''
 
|'''StyleType'''
|<font color="grey">(en-US)</font> StyleType
+
|[[Datei:EN-US.png]]StyleType
 
| colspan="2" |<p>The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style</p>
 
| colspan="2" |<p>The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActRelationshipSubset'''
 
|'''ActRelationshipSubset'''
|<font color="grey">(en-US)</font> ActRelationshipSubset
+
|[[Datei:EN-US.png]]ActRelationshipSubset
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AcknowledgementDetailCode'''
 
|'''AcknowledgementDetailCode'''
|<font color="grey">(en-US)</font> AcknowledgementDetailCode
+
|[[Datei:EN-US.png]]AcknowledgementDetailCode
 
| colspan="2" |<p>A site specific problem code</p>
 
| colspan="2" |<p>A site specific problem code</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IETF3066'''
 
|'''IETF3066'''
|<font color="grey">(en-US)</font> Tags for the Identification of Languages
+
|[[Datei:EN-US.png]]Tags for the Identification of Languages
 
| colspan="2" |<p>from OID registry</p>
 
| colspan="2" |<p>from OID registry</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ResponseMode'''
 
|'''ResponseMode'''
|<font color="grey">(en-US)</font> ResponseMode
+
|[[Datei:EN-US.png]]ResponseMode
 
| colspan="2" |<p>Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.</p>
 
| colspan="2" |<p>Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryParameterValue'''
 
|'''QueryParameterValue'''
|<font color="grey">(en-US)</font> QueryParameterValue
+
|[[Datei:EN-US.png]]QueryParameterValue
 
| colspan="2" |<p>The domain of coded values used as parameters within QueryByParameter queries.</p>
 
| colspan="2" |<p>The domain of coded values used as parameters within QueryByParameter queries.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SpecialArrangement'''
 
|'''SpecialArrangement'''
|<font color="grey">(en-US)</font> SpecialArrangement
+
|[[Datei:EN-US.png]]SpecialArrangement
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EPSG-GeodeticParameterDataset'''
 
|'''EPSG-GeodeticParameterDataset'''
|<font color="grey">(en-US)</font> EPSG Geodetic Parameter Dataset
+
|[[Datei:EN-US.png]]EPSG Geodetic Parameter Dataset
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''SCDHEC-GISSpatialAccuracyTiers'''
 
|'''SCDHEC-GISSpatialAccuracyTiers'''
|<font color="grey">(en-US)</font> SCDHEC GIS Spatial Accuracy Tiers
+
|[[Datei:EN-US.png]]SCDHEC GIS Spatial Accuracy Tiers
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ContentProcessingMode'''
 
|'''ContentProcessingMode'''
|<font color="grey">(en-US)</font> ContentProcessingMode
+
|[[Datei:EN-US.png]]ContentProcessingMode
 
| colspan="2" |<p>Description:Identifies the order in which content should be processed.</p>
 
| colspan="2" |<p>Description:Identifies the order in which content should be processed.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TransmissionRelationshipTypeCode'''
 
|'''TransmissionRelationshipTypeCode'''
|<font color="grey">(en-US)</font> TransmissionRelationshipTypeCode
+
|[[Datei:EN-US.png]]TransmissionRelationshipTypeCode
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''QueryRequestLimit'''
 
|'''QueryRequestLimit'''
|<font color="grey">(en-US)</font> QueryRequestLimit
+
|[[Datei:EN-US.png]]QueryRequestLimit
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActExposureLevelCode'''
 
|'''ActExposureLevelCode'''
|<font color="grey">(en-US)</font> ActExposureLevelCode
+
|[[Datei:EN-US.png]]ActExposureLevelCode
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ExposureMode'''
 
|'''ExposureMode'''
|<font color="grey">(en-US)</font> ExposureMode
+
|[[Datei:EN-US.png]]ExposureMode
 
| colspan="2" |<p>Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.</p>
 
| colspan="2" |<p>Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HealthcareServiceLocation'''
 
|'''HealthcareServiceLocation'''
|<font color="grey">(en-US)</font> Healthcare Service Location
+
|[[Datei:EN-US.png]]Healthcare Service Location
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IdentifierScope'''
 
|'''IdentifierScope'''
|<font color="grey">(en-US)</font> IdentifierScope
+
|[[Datei:EN-US.png]]IdentifierScope
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''IdentifierReliability'''
 
|'''IdentifierReliability'''
|<font color="grey">(en-US)</font> IdentifierReliability
+
|[[Datei:EN-US.png]]IdentifierReliability
 
| colspan="2" |<p>Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.</p>
 
| colspan="2" |<p>Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TriggerEventID'''
 
|'''TriggerEventID'''
|<font color="grey">(en-US)</font> TriggerEventID
+
|[[Datei:EN-US.png]]TriggerEventID
 
| colspan="2" |<p>Description:Trigger Event ID as published in the standard.</p>
 
| colspan="2" |<p>Description:Trigger Event ID as published in the standard.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''TelecommunicationCapabilities'''
 
|'''TelecommunicationCapabilities'''
|<font color="grey">(en-US)</font> TelecommunicationCapabilities
+
|[[Datei:EN-US.png]]TelecommunicationCapabilities
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AddressUse'''
 
|'''AddressUse'''
|<font color="grey">(en-US)</font> AddressUse
+
|[[Datei:EN-US.png]]AddressUse
 
| colspan="2" |<p>Description: Uses of Addresses. Lloyd to supply more complete description.</p>
 
| colspan="2" |<p>Description: Uses of Addresses. Lloyd to supply more complete description.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''OPINIONS'''
 
|'''OPINIONS'''
|<font color="grey">(en-US)</font> Online Product Identification Number Index of Nova Scotia
+
|[[Datei:EN-US.png]]Online Product Identification Number Index of Nova Scotia
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HC-AIC'''
 
|'''HC-AIC'''
|<font color="grey">(en-US)</font> Active Ingredient Code
+
|[[Datei:EN-US.png]]Active Ingredient Code
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HC-AIGC'''
 
|'''HC-AIGC'''
|<font color="grey">(en-US)</font> Active Ingredient Group Code
+
|[[Datei:EN-US.png]]Active Ingredient Group Code
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HC-DIN'''
 
|'''HC-DIN'''
|<font color="grey">(en-US)</font> Health Canada Drug Id Number
+
|[[Datei:EN-US.png]]Health Canada Drug Id Number
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HC-AIGN'''
 
|'''HC-AIGN'''
|<font color="grey">(en-US)</font> Active Ingredient Group Number
+
|[[Datei:EN-US.png]]Active Ingredient Group Number
 
| colspan="2" |<p>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</p>
 
| colspan="2" |<p>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</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''HC-NPN'''
 
|'''HC-NPN'''
|<font color="grey">(en-US)</font> Health Canada Natural Product Number
+
|[[Datei:EN-US.png]]Health Canada Natural Product Number
 
| colspan="2" |<p>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-prod/lnhpd-bdpsnh-eng.php</p>
 
| colspan="2" |<p>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-prod/lnhpd-bdpsnh-eng.php</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''AHFS'''
 
|'''AHFS'''
|<font color="grey">(en-US)</font> AHFS Pharmacologic-Therapeutic Classification
+
|[[Datei:EN-US.png]]AHFS Pharmacologic-Therapeutic Classification
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''BodySite'''
 
|'''BodySite'''
|<font color="grey">(en-US)</font> HL7 table 0163 - Body site
+
|[[Datei:EN-US.png]]HL7 table 0163 - Body site
 
| colspan="2" |<p>Description: HL7 version 2.x Body site used in chapter(s) 4; HL7 table 0163</p>
 
| colspan="2" |<p>Description: HL7 version 2.x Body site used in chapter(s) 4; HL7 table 0163</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNameUseR2'''
 
|'''EntityNameUseR2'''
|<font color="grey">(en-US)</font> EntityNameUseR2
+
|[[Datei:EN-US.png]]EntityNameUseR2
 
| colspan="2" |<p>Description:A set of codes advising a system or user which name in a set of names to select for a given purpose.</p>
 
| colspan="2" |<p>Description:A set of codes advising a system or user which name in a set of names to select for a given purpose.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNamePartTypeR2'''
 
|'''EntityNamePartTypeR2'''
|<font color="grey">(en-US)</font> EntityNamePartTypeR2
+
|[[Datei:EN-US.png]]EntityNamePartTypeR2
 
| colspan="2" |<p>Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc.</p>
 
| colspan="2" |<p>Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EntityNamePartQualifierR2'''
 
|'''EntityNamePartQualifierR2'''
|<font color="grey">(en-US)</font> EntityNamePartQualifierR2
+
|[[Datei:EN-US.png]]EntityNamePartQualifierR2
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EPSG_CRS'''
 
|'''EPSG_CRS'''
|<font color="grey">(en-US)</font> European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System
+
|[[Datei:EN-US.png]]European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''EPSG_CA'''
 
|'''EPSG_CA'''
|<font color="grey">(en-US)</font> European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis
+
|[[Datei:EN-US.png]]European Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''DataOperation'''
 
|'''DataOperation'''
|<font color="grey">(en-US)</font> DataOperation
+
|[[Datei:EN-US.png]]DataOperation
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''BindingRealm'''
 
|'''BindingRealm'''
|<font color="grey">(en-US)</font> BindingRealm
+
|[[Datei:EN-US.png]]BindingRealm
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7V3Conformance'''
 
|'''hl7V3Conformance'''
|<font color="grey">(en-US)</font> HL7V3Conformance
+
|[[Datei:EN-US.png]]HL7V3Conformance
 
| colspan="2" |<p>Description: Identifies allowed codes for HL7aTMs v3 conformance property.</p>
 
| colspan="2" |<p>Description: Identifies allowed codes for HL7aTMs v3 conformance property.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''iso21000-6-2004E-RDD'''
 
|'''iso21000-6-2004E-RDD'''
|<font color="grey">(en-US)</font> ISO/IEC 21000-6:2004(E) Rights Data Dictionary
+
|[[Datei:EN-US.png]]ISO/IEC 21000-6:2004(E) Rights Data Dictionary
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ContextConductionStyle'''
 
|'''ContextConductionStyle'''
|<font color="grey">(en-US)</font> ContextConductionStyle
+
|[[Datei:EN-US.png]]ContextConductionStyle
 
| colspan="2" |<p>The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.</p>
 
| colspan="2" |<p>The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''MSH'''
 
|'''MSH'''
|<font color="grey">(en-US)</font> MeSH
+
|[[Datei:EN-US.png]]MeSH
 
| colspan="2" |<p>Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004</p>
 
| colspan="2" |<p>Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7ApprovalStatus'''
 
|'''hl7ApprovalStatus'''
|<font color="grey">(en-US)</font> HL7ApprovalStatus
+
|[[Datei:EN-US.png]]HL7ApprovalStatus
 
| colspan="2" |<p>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.</p>
 
| colspan="2" |<p>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.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7VoteResolution'''
 
|'''hl7VoteResolution'''
|<font color="grey">(en-US)</font> HL7VoteResolution
+
|[[Datei:EN-US.png]]HL7VoteResolution
 
| colspan="2" |<p>Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).</p>
 
| colspan="2" |<p>Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7CMETAttribution'''
 
|'''hl7CMETAttribution'''
|<font color="grey">(en-US)</font> HL7CMETAttribution
+
|[[Datei:EN-US.png]]HL7CMETAttribution
 
| colspan="2" |<p></p>
 
| colspan="2" |<p></p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7PublishingSection'''
 
|'''hl7PublishingSection'''
|<font color="grey">(en-US)</font> HL7PublishingSection
+
|[[Datei:EN-US.png]]HL7PublishingSection
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'section's (major business categories)</p>
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'section's (major business categories)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7PublishingSubSection'''
 
|'''hl7PublishingSubSection'''
|<font color="grey">(en-US)</font> HL7PublishingSubSection
+
|[[Datei:EN-US.png]]HL7PublishingSubSection
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'sub-section's (business sub-categories)</p>
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'sub-section's (business sub-categories)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7PublishingDomain'''
 
|'''hl7PublishingDomain'''
|<font color="grey">(en-US)</font> HL7PublishingDomain
+
|[[Datei:EN-US.png]]HL7PublishingDomain
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'domain's (specific content area)</p>
 
| colspan="2" |<p>Description: Codes for HL7 publishing 'domain's (specific content area)</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''hl7ITSType'''
 
|'''hl7ITSType'''
|<font color="grey">(en-US)</font> HL7ITSType
+
|[[Datei:EN-US.png]]HL7ITSType
 
| colspan="2" |<p>Description: Codes identifying types of HL7 Implementation Technology Specifications</p>
 
| colspan="2" |<p>Description: Codes identifying types of HL7 Implementation Technology Specifications</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''RoleLinkStatus'''
 
|'''RoleLinkStatus'''
|<font color="grey">(en-US)</font> RoleLink Status
+
|[[Datei:EN-US.png]]RoleLink Status
 
| colspan="2" |<p>Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.</p>
 
| colspan="2" |<p>Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.</p>
 
|-
 
|-
 
|0-L
 
|0-L
 
|'''ActUSPrivacyLaw'''
 
|'''ActUSPrivacyLaw'''
|<font color="grey">(en-US)</font> Act US Privacy Law
+
|[[Datei:EN-US.png]]Act US Privacy Law
 
| colspan="2" |<p>Description: A jurisdictional mandate in the US relating to privacy.</p>
 
| colspan="2" |<p>Description: A jurisdictional mandate in the US relating to privacy.</p>
 
|}
 
|}

Version vom 18. November 2012, 12:46 Uhr

Codesystem Name Codesystem Id Version / Eingangsdatum Status
CodeSystem 2.16.840.1.113883.5.22 2012-07-24 definitiv
Level/Typ Code Anzeigename Beschreibung
0-L AS4 EN-US.pngASTM E1238/ E1467 Universal

American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467).

0-L ACR EN-US.pngAmerican College of Radiology finding codes

Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA.

0-L ATC EN-US.pngAmerican Type Culture Collection

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

0-L AS4E EN-US.pngAS4 Neurophysiology Codes

ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2.

0-L CDS EN-US.pngCDC Surveillance

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.

0-L CD2 EN-US.pngCDT-2 Codes

American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611.

0-L CE EN-US.pngCEN ECG diagnostic codes

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

0-L CLP EN-US.pngCLIP

Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports.

0-L C4 EN-US.pngCPT-4

American Medical Association, P.O. Box 10946, Chicago IL 60610.

0-L C5 EN-US.pngCPT-5

American Medical Association, P.O. Box 10946, Chicago IL 60610.

0-L DCL EN-US.pngDICOM Class Label

From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034

0-L DCM EN-US.pngDICOM modality codes

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,

0-L DQL EN-US.pngDICOM Query Label

HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI.

0-L ENZC EN-US.pngEnzyme Codes

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.

0-L E EN-US.pngEUCLIDES

Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.

0-L E5 EN-US.pngEuclides quantity codes

Available from Euclides Foundation International nv (see above)

0-L E6 EN-US.pngEuclides Lab method codes

Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60.

0-L E7 EN-US.pngEuclides Lab equipment codes

Available from Euclides Foundation International nv (see above)

0-L FDK EN-US.pngFDA K10

Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes).

0-L HPC EN-US.pngHCFA Procedure Codes (HCPCS)

Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) modifiers.

0-L HI EN-US.pngHealth Outcomes

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.

0-L HB EN-US.pngHIBCC

Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018.

0-L HHC EN-US.pngHome Health Care

Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC.

0-L ICS EN-US.pngICCS

Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105.

0-L I9C EN-US.pngICD-9CM

Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests).

0-L I9 EN-US.pngICD9

World Health Publications, Albany, NY.

0-L I10P EN-US.pngICD-10 Procedure Codes

Procedure Coding System (ICD-10-PCS). See http://www/hcfa.gov/stats/icd10.icd10.htm for more information.

0-L I10 EN-US.pngICD-10

World Health Publications, Albany, NY.

0-L ICDO EN-US.pngInternational Classification of Diseases for Oncology

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.

0-L IC2 EN-US.pngICHPPC-2

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.

0-L ICSD EN-US.pngInternational Classification of Sleep Disorders

International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902

0-L IBT EN-US.pngISBT

International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169.

0-L IUPP EN-US.pngIUPAC/IFCC Property Codes

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/

0-L IUPC EN-US.pngIUPAC/IFCC Component Codes

Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP.

0-L JC8 EN-US.pngJapanese Chemistry

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)

0-L LN EN-US.pngLogical Observation Identifier Names and Codes (LOINC)

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.

0-L NIC EN-US.pngNursing Intervention Classification

Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa

0-L OHA EN-US.pngOmaha System

Omaha Visiting Nurse Association, Omaha, NB.

0-L NDA EN-US.pngNANDA

North American Nursing Diagnosis Association, Philadelphia, PA.

0-L POS EN-US.pngPOS Codes

HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm).

0-L RC EN-US.pngRead Classification

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

0-L SNM EN-US.pngSystemized Nomenclature of Medicine (SNOMED)

Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL.

0-L SNM3 EN-US.pngSNOMED International

SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034..

0-L SNT EN-US.pngSNOMED topology codes (anatomic sites)

College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034.

0-L SDM EN-US.pngSNOMED- DICOM Microglossary

College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM).

0-L UC EN-US.pngUCDS

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.

0-L UPC EN-US.pngUniversal Product Code

The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458; (513) 435 3070

0-L UML EN-US.pngUnified Medical Language

National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894.

0-L CDCA EN-US.pngCDC Analyte Codes

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

0-L CDCM EN-US.pngCDC Methods/Instruments Codes

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

0-L CVX EN-US.pngCDC Vaccine Codes

National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333

0-L MVX EN-US.pngCDC Vaccine Manufacturer Codes

National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333

0-L CAS EN-US.pngChemical abstract codes

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.

0-L CST EN-US.pngCOSTART

International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD.

0-L FDDX EN-US.pngFirst DataBank Diagnostic Codes

Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC.

0-L FDDC EN-US.pngFirst DataBank Drug Codes

National Drug Data File. Proprietary product of First DataBank, Inc. (800) 633-3453, or http://www.firstdatabank.com.

0-L MDDX EN-US.pngMedispan Diagnostic Codes

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.

0-L MEDX EN-US.pngMedical Economics Diagnostic Codes

Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.

0-L MEDC EN-US.pngMedical Economics Drug Codes

Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc. (800) 223-0581.

0-L MGPI EN-US.pngMedispan GPI

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.

0-L NDC EN-US.pngNational drug codes

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

0-L MEDR EN-US.pngMedical Dictionary for Drug Regulatory Affairs (MEDRA)

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

0-L W1-W2 EN-US.pngWHO rec# drug codes

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.

0-L W4 EN-US.pngWHO rec# code with ASTM extension

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

0-L WC EN-US.pngWHO ATC

WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above.

0-L ART EN-US.pngWHO Adverse Reaction Terms

WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden.

0-L UMD EN-US.pngMDNS

Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone: 215-825-6000, Fax: 215-834-1275.

0-L NUBC-UB92 EN-US.pngNational Uniform Billing Council, UB 92

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

0-L Dentition EN-US.pngDentition

0-L CSAID EN-US.pngCAN/CSA-Z795-96 (R2001)

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

0-L CCI EN-US.pngCanadian Classification of Health Interventions

CCI - Canadian Classification of Health Interventions, developed to accompany ICD-10-CA, maintained by CIHI (Canadian Institute for Health Information). For example: sections 3.AA-3.BZ Diagnostic Imaging Interventions on the Nervous System 3.AN.^ ^.^ ^ Diagnostic Imaging Interventions on the Brain 3.AN.40. ^ ^ Magnetic Resonance Imaging, Brain Incudes: That for meninges, ventricles, cerebellum, brain stem, cisterna [of brain], posterior fossa MRI, brain 3.AN.40.VA without contrast 3.AN.40.VC following intravenous injection of contrast 3.AN.40.VZ following percutaneous injection of contrast CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca

0-L AcknowledgementDetailType EN-US.pngAcknowledgement Detail Type

0-L MessageWaitingPriority EN-US.pngMessage Waiting Priority

Indicates that the receiver has messages for the sender

0-L EncounterAcuity EN-US.pngEncounter Acuity

The level of resource intensiveness of patient care.

0-L ISO3166-1 EN-US.pngISO 3166 2 Character Country Codes

Two character country codes

0-L ISO3166-2 EN-US.pngISO 3166 3 Character Country Codes

Three character country codes

0-L ISO3166-3 EN-US.pngISO 3166 Numeric country Codes

Numeric country codes

0-L AdministrativeGender EN-US.pngAdministrativeGender

The gender of a person used for adminstrative purposes (as opposed to clinical gender)

0-L ActRelationshipCheckpoint EN-US.pngActRelationshipCheckpoint

0-L ProcessingID EN-US.pngProcessingID

0-L ActMood EN-US.pngActMood

0-L ActRelationshipType EN-US.pngActRelationshipType

The source is an excerpt from the target.

0-L DataType EN-US.pngDataType

0-L NullFlavor EN-US.pngNullFlavor

0-L CompressionAlgorithm EN-US.pngCompressionAlgorithm

0-L ProcessingMode EN-US.pngProcessingMode

0-L IntegrityCheckAlgorithm EN-US.pngIntegrityCheckAlgorithm

0-L TelecommunicationAddressUse EN-US.pngTelecommunicationAddressUse

0-L PostalAddressUse EN-US.pngPostalAddressUse

0-L OrganizationNameType EN-US.pngOrganizationNameType

0-L CalendarType EN-US.pngCalendarType

0-L QueryPriority EN-US.pngQueryPriority

0-L ProbabilityDistributionType EN-US.pngProbabilityDistributionType

0-L PeriodicIntervalOfTimeAbbreviation EN-US.pngPeriodicIntervalOfTimeAbbreviation

0-L GTSAbbreviation EN-US.pngGTSAbbreviation

0-L QueryStatusCode EN-US.pngQueryStatusCode

State attributes for Query event

0-L Race EN-US.pngRace

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.

0-L RelationalOperator EN-US.pngRelationalOperator

0-L AcknowledgementCondition EN-US.pngAcknowledgementCondition

0-L ActInvoiceElementModifier EN-US.pngActInvoiceElementModifier

Processing consideration and clarification codes.

0-L ActSite EN-US.pngActSite

An anatomical location on an organism which can be the focus of an act.

0-L ActUncertainty EN-US.pngActUncertainty

0-L AmericanIndianAlaskaNativeLanguages EN-US.pngAmericanIndianAlaskaNativeLanguages

American Indian and Alaska Native languages currently being used in the United States.

0-L Calendar EN-US.pngCalendar

0-L CommunicationFunctionType EN-US.pngCommunicationFunctionType

Describes the type of communication function that the associated entity plays in the associated transmission.

0-L ContextControl EN-US.pngContextControl

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.

0-L Currency EN-US.pngCurrency

The currency unit as defined in ISO 4217

0-L EmployeeJobClass EN-US.pngEmployeeJobClass

0-L RelationshipConjunction EN-US.pngRelationshipConjunction

0-L EntityCode EN-US.pngEntityCode

0-L EntityStatus EN-US.pngEntityStatus

The status of an instance of the RIM Entity class.

0-L ManagedParticipationStatus EN-US.pngManagedParticipationStatus

The status of an instance of the RIM Participation class.

0-L ObservationValue EN-US.pngObservationValue

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.

0-L ParticipationMode EN-US.pngParticipationMode

Identifies the primary means by which an Entity participates in an Act.

0-L ProcedureMethod EN-US.pngProcedureMethod

Identifies the technique used to perform a procedure.

0-L QueryQuantityUnit EN-US.pngQueryQuantityUnit

Values in this domain specify the units of a query quantity limited request.

0-L QueryResponse EN-US.pngQueryResponse

Values in this domain allow a query response system to return a precise response status.

0-L RoleStatus EN-US.pngRoleStatus

The status of an instance of the RIM Role class.

0-L SetOperator EN-US.pngSetOperator

0-L RoleLinkType EN-US.pngRoleLinkType

0-L SubstanceAdminSubstitution EN-US.pngSubstanceAdminSubstitution

Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.

0-L SubstitutionCondition EN-US.pngSubstitutionCondition

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.

0-L CodingRationale EN-US.pngCodingRationale

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.

0-L PatientImportance EN-US.pngPatientImportance

Patient VIP code

0-L ReligiousAffiliation EN-US.pngReligious Affiliation

Assigment of spiritual faith affiliation

0-L EducationLevel EN-US.pngEducation Level

Years of education that a person has completed

0-L ResponseLevel EN-US.pngResponseLevel

Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include

0-L ResponseModality EN-US.pngResponseModality

0-L RoleClass EN-US.pngRoleClass

0-L RoleCode EN-US.pngRoleCode

Specific classification codes for further qualifying RoleClass codes.

0-L RouteOfAdministration EN-US.pngRouteOfAdministration

0-L Sequencing EN-US.pngSequencing

0-L ActRelationshipJoin EN-US.pngActRelationshipJoin

0-L SpecimenType EN-US.pngSpecimenType

0-L ActRelationshipSplit EN-US.pngActRelationshipSplit

0-L TableCellHorizontalAlign EN-US.pngTableCellHorizontalAlign

These values are defined within the XHTML 4.0 Table Model

0-L TableCellScope EN-US.pngTableCellScope

These values are defined within the XHTML 4.0 Table Model

0-L TableCellVerticalAlign EN-US.pngTableCellVerticalAlign

These values are defined within the XHTML 4.0 Table Model

0-L TableFrame EN-US.pngTableFrame

These values are defined within the XHTML 4.0 Table Model

0-L TableRules EN-US.pngTableRules

These values are defined within the XHTML 4.0 Table Model

0-L TargetAwareness EN-US.pngTargetAwareness

0-L TimingEvent EN-US.pngTimingEvent

0-L ActStatus EN-US.pngActStatus

Contains the names (codes) for each of the states in the state-machine of the RIM Act class.

0-L TribalEntityUS EN-US.pngTribalEntityUS

INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS

0-L UnitsOfMeasure EN-US.pngUnitsOfMeasureCaseInsensitive

0-L URLScheme EN-US.pngURLScheme

A Universal Resource Locator (URL) is a type of telecommunications address specified as Internet standard RFC 1738 [1]. The URL specifies the protocol and the contact point defined by that protocol for the resource.

0-L VaccineManufacturer EN-US.pngVaccineManufacturer

The manufacturer of a vaccine.

0-L VaccineType EN-US.pngVaccineType

The kind of vaccine.

0-L VocabularyDomainQualifier EN-US.pngVocabularyDomainQualifier

Vocabulary domain qualifiers are concepts that are used in domain constraints to specify behavior of the new domain.

0-L AddressPartType EN-US.pngAddressPartType

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

0-L AcknowledgementType EN-US.pngAcknowledgementType

Acknowledgement code as described in HL7 message processing rules.

0-L MaritalStatus EN-US.pngMaritalStatus

0-L Charset EN-US.pngCharset

Internet Assigned Numbers Authority (IANA) Charset Types

0-L CodeSystem EN-US.pngCodeSystem

Code systems used in HL7 standards.

0-L ConceptGenerality EN-US.pngConceptGenerality

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.

0-L Confidentiality EN-US.pngConfidentiality

0-L ContainerCap EN-US.pngContainerCap

The type of cap associated with a container

0-L ContainerSeparator EN-US.pngContainerSeparator

A material in a blood collection container that facilites the separation of of blood cells from serum or plasma

0-L EntityDeterminer EN-US.pngEntityDeterminer

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.

0-L DeviceAlertLevel EN-US.pngDeviceAlertLevel

Domain values for the Device.Alert_levelCode

0-L DocumentCompletion EN-US.pngDocumentCompletion

Identifies the current completion state of a clinical document.

0-L DocumentStorage EN-US.pngDocumentStorage

Identifies the storage status of a document.

0-L EditStatus EN-US.pngEditStatus

The status of an entry as it pertains to its review and incorporation into the HL7 domain specification database.

0-L EncounterAccident EN-US.pngEncounterAccident

0-L EncounterAdmissionSource EN-US.pngEncounterAdmissionSource

0-L EncounterReferralSource EN-US.pngEncounterReferralSource

This domain is defined in UB92 and applies to US realm only

0-L ActCode EN-US.pngActCode

The table that provides the detailed or rich codes for the Act classes.

0-L EncounterSpecialCourtesy EN-US.pngEncounterSpecialCourtesy

0-L EntityClass EN-US.pngEntityClass

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.

0-L EntityHandling EN-US.pngEntityHandling

0-L EntityNamePartQualifier EN-US.pngEntityNamePartQualifier

0-L EntityNamePartType EN-US.pngEntityNamePartType

0-L EntityNameUse EN-US.pngEntityNameUse

0-L EntityRisk EN-US.pngEntityRisk

The vocabulary table for the Entity.riskCode attribute

0-L EquipmentAlertLevel EN-US.pngEquipmentAlertLevel

0-L Ethnicity EN-US.pngEthnicity

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.

0-L GenderStatus EN-US.pngGenderStatus

0-L HealthcareProviderTaxonomyHIPAA EN-US.pngHealthcareProviderTaxonomyHIPAA

0-L HL7CommitteeIDInRIM EN-US.pngHL7CommitteeIDInRIM

Holds the codes used to identify the committees and SIGS of HL7 in RIM repository tables.

0-L HL7ConformanceInclusion EN-US.pngHL7ConformanceInclusion

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.

0-L HL7DefinedRoseProperty EN-US.pngHL7DefinedRoseProperty

The property Ids that HL7 has defined for customizing Rational Rose.

0-L HL7UpdateMode EN-US.pngHL7UpdateMode

The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.

0-L HtmlLinkType EN-US.pngHtmlLinkType

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

0-L ActClass EN-US.pngActClass

0-L LanguageAbilityMode EN-US.pngLanguageAbilityMode

0-L LanguageAbilityProficiency EN-US.pngLanguageAbilityProficiency

0-L LivingArrangement EN-US.pngLivingArrangement

A code depicting the living arrangements of a person

0-L LocalMarkupIgnore EN-US.pngLocalMarkupIgnore

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"

0-L LocalRemoteControlState EN-US.pngLocalRemoteControlState

0-L MapRelationship EN-US.pngMapRelationship

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

0-L ActPriority EN-US.pngActPriority

0-L MaterialType EN-US.pngMaterialType

0-L MDFAttributeType EN-US.pngMDFAttributeType

0-L MdfHmdMetSourceType EN-US.pngMdfHmdMetSourceType

Code to identify the source of a Message Element Type represented in the 'of MET' column of an HMD.

0-L MdfHmdRowType EN-US.pngMdfHmdRowType

The row type codes for the tabular representation of a Hierarchical Message Description.

0-L MdfRmimRowType EN-US.pngMdfRmimRowType

The row types for the tabular representation of an R-MIM.

0-L MDFSubjectAreaPrefix EN-US.pngMDFSubjectAreaPrefix

The standard prefixes used in Rose for RIM subject areas that determine the role or function of each subject area.

0-L MediaType EN-US.pngMediaType

Internet Assigned Numbers Authority (IANA) Mime Media Types

0-L ActReason EN-US.pngActReason

0-L MessageCondition EN-US.pngMessageCondition

0-L ModifyIndicator EN-US.pngModifyIndicator

0-L ObservationInterpretation EN-US.pngObservationInterpretation

0-L ObservationMethod EN-US.pngObservationMethod

0-L OrderableDrugForm EN-US.pngOrderableDrugForm

0-L ParameterizedDataType EN-US.pngParameterizedDataType

0-L ParticipationFunction EN-US.pngParticipationFunction

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

0-L ParticipationSignature EN-US.pngParticipationSignature

0-L CalendarCycle EN-US.pngCalendarCycle

0-L ParticipationType EN-US.pngParticipationType

0-L PaymentTerms EN-US.pngPaymentTerms

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.

0-L PersonDisabilityType EN-US.pngPersonDisabilityType

A code identifying a person's disability.

0-L MIME EN-US.pngMIME

IETF MIME media types

0-L NOC EN-US.pngNOC

NOC - Nursing Outcome Codes

0-L CAMNCVS EN-US.pngCAMNCVS

CAM & Nursing Coding Vocabulary Set

0-L PNDS EN-US.pngPerioperative Nursing Data Set

The PNDS provides standardized terms and codes for patient problems/nursing diagnoses, nursing interventions including actual or expected (goal) outcomes. The PNDS provides standardized terms and codes for nursing diagnoses (a subset of NANDA), nursing interventions and outcomes. The outcomes and interventions are in a relational database. The PNDS intervention and outcome statements are attached in an Access Database. The NANDA diagnoses in the PNDS have already been registered by HL7.

0-L NMMDS EN-US.pngNursing Management Minimum Data Set

The NMMDS is the minimum set of items of information with uniform definitions and categories concerning the specific dimension of the context of patient care delivery. It represents the minimum data used to support the management and administration of patient/nursing care delivery across all types of settings. The NMMDS is composed of seventeen (17) data elements organized into three categories: environment, nurse resources, and financial resources. See Tables 1-3 for the elements and related definitions organized by each categories. The NMMDS most appropriately focuses at the first level of accountability for patient/client/family/community nursing care: this may be the delivery unit, service, or center of excellence level. The NMMDS supports numerous constructed variables as well as aggregation of data at the unit, institution, network, and system, etc levels. This minimum data set provides the structure for the collection of uniform information that influences quality of patient care, directly and indirectly.

0-L MDC EN-US.pngISO 11073-10101 Health informatics - Point-of-care

The nomenclature relates primarily to vital signs monitoring, but also includes semantics of other medical devices that are commonly used in acute care settings. There are multiple coding partitions each of which has a systematic name consisting of a set of base concepts and differentiating criteria.

0-L ABCcodes EN-US.pngABCcodes

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

0-L MEDCIN EN-US.pngMEDCIN

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.

0-L MULTUM EN-US.pngMultum Lexicon

Broadly, the fields and values in the Multum Lexicon and the VantageRx Database are intended to be available for use in any HL7 message that includes a reference to non-veterinary drug products or active ingredients that are either approved for sale by the FDA or readily available in the United States. The following inter-related definitions recently circulated by us to the HL7 Vocabulary Technical Committee explain the scope of what we mean by "drug product" and "active ingredient." (A definition for "drug ingredient" is also provided here because the definition of "active ingredient" is reliant on this term.) Drug Product A drug product is a manufactured or extemporaneously-compounded physiologically-active material intended by the preparer to achieve therapeutic, diagnostic, or preventative effects via biochemical mechanisms when applied to an epithelial surface or placed in an internal body space of a targeted organism. Drug Ingredient A drug ingredient is a chemical compound or biologic agent that occurs in a drug product. Active Ingredient An active ingredient is a drug ingredient that mediates one or more of the intended therapeutic, diagnostic, or preventative effects of a drug product and is present in sufficient quantities to achieve such effects according to the allopathic tradition of healthcare practice.

0-L RCFB EN-US.pngThe Read Codes Four Byte Set:

The Read Codes Four Byte Set consists of 4 alphanumeric characters. This version contains approximately 40,000 codes arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs

0-L RCV2 EN-US.pngThe Read Codes Version 2

The Read Codes Version 2 contains over 70,000 coded concepts arranged in a hierarchical structure. Top level hierarchy sections: Disorders Findings Surgical procedures Investigations Occupations Drugs

0-L NAACCR EN-US.pngNAACCR

NAACCR Cancer Registry

0-L UCUM EN-US.pngUCUM

Unified Code for Units of Measure

0-L IETF1766 EN-US.pngIETF RFC 1766

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

0-L NAICS EN-US.pngNorth American Industry Classification System

North American Industry Classification System(NAICS) for the United States, a new economic classification system that replaces the 1987 Standard Industrial Classification (SIC) for statistical purposes. NAICS is a system for classifying establishments by type of economic activity. Its purposes are: (1) to facilitate the collection, tabulation, presentation, and analysis of data relating to establishments, and (2) to promote uniformity and comparability in the presentation of statistical data describing the economy. NAICS will be used by Federal statistical agencies that collect or publish data by industry.

0-L ISO4217 EN-US.pngISO4217

ISO 4217 currency code

0-L CodeSystemType EN-US.pngHL7 Code System Type

0-L ConceptStatus EN-US.pngHL7 Coded Concept Status

0-L ConceptProperty EN-US.pngHL7 Value Set and Coded Concept Property Codes

0-L ConceptCodeRelationship EN-US.pngPossible Concept Code Relationships

0-L HL7StandardVersionCode EN-US.pngHL7StandardVersionCode

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.

0-L ICD-10-CA EN-US.pngCanadianDiagnosisCodesICD-10-CA

Canadian Coding Standards ICD-10 CA. These standards are a compilation of international rules of coding as established by the World Health Organization (International Classification of Diseases, 10th Revision, Volume 2) and the Diagnosis Typing Standard developed to denote case complexity for application in Canadian facilities. For example: L40 Psoriasis L40.0 Psoriasis vulgaris Nummular psoriasis Plaque psoriasis L40.1 Generalized pustular psoriasis Impetigo herpetiformis Von ZumbuschaTMs disease L40.2 Acrodermatitis continua L40.3 Pustulosis palmaris et plantaris L40.4 Guttate psoriasis L40.5* Arthropathic psoriasis (M07.0-M07.3*)(M09.0*) L40.8 Other psoriasis Erythroderma psoraticum Erythrodermic psoriasis Flexural psoriasis L40.9 Psoriasis unspecified They are maintained by CIHI (Canadian Institute for Health Information). CIHI Toronto Attn: Director of Standards 90 Eglinton Avenue, Suite 300 Toronto, Ontario Canada M4P 2Y3 Phone: (416) 481.2002 Fax: (416) 481-2950 www.cihi.ca

0-L HL7ITSVersionCode EN-US.pngHL7 ITS Version Code

HL7 implementation technology specification versions. These codes will document the ITS type and version for message encoding. The code will appear in the instances based upon rules expressed in the ITS, and do not appear in the abstract message, either as it is presented to received from the ITS.

0-L NUCCProviderCodes EN-US.pngNUCC Health Care Provider Taxonomy

The Provider Taxonomy Code List is published (released) twice a year on July 1st and January 1st. The July publication is effective for use on October 1st and the January publication is effective for use on April 1st. The time between the publication release and the effective date is considered an implementation period to allow providers, payers and vendors an opportunity to incorporate any changes into their systems. This listing includes Active codes approved for use effective April 1st, 2003, version 3.0; and codes that are New and approved for use effective October 1st, 2003, version 3.1.

0-L StyleType EN-US.pngStyleType

The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style

0-L ActRelationshipSubset EN-US.pngActRelationshipSubset

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.

0-L AcknowledgementDetailCode EN-US.pngAcknowledgementDetailCode

A site specific problem code

0-L IETF3066 EN-US.pngTags for the Identification of Languages

from OID registry

0-L ResponseMode EN-US.pngResponseMode

Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.

0-L QueryParameterValue EN-US.pngQueryParameterValue

The domain of coded values used as parameters within QueryByParameter queries.

0-L SpecialArrangement EN-US.pngSpecialArrangement

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.

0-L EPSG-GeodeticParameterDataset EN-US.pngEPSG Geodetic Parameter Dataset

Description: The EPSG (European Petroleum Survey Group) dataset represents all Datums, coordinate references (projected and 2D geographic) and coordinate systems (including Cartesian coordinate systems) used in surveying worldwide. Each record includes a 4-8 digit unique identifier. The current version is available from http://www.epsg.org/. The database contains over 4000 records covering spatial data applications worldwide.

0-L SCDHEC-GISSpatialAccuracyTiers EN-US.pngSCDHEC GIS Spatial Accuracy Tiers

Description: The South Carolina Department of Health and Environmental Control GIS Spatial Data Accuracy Tiers have been derived from the National Standard for Spatial Data Accuracy as a means to categorize the accuracy of spatial data assignment utilizing a variety of tools for capturing coordinates including digitizers, geocoding software and global positioning system devices.

0-L ContentProcessingMode EN-US.pngContentProcessingMode

Description:Identifies the order in which content should be processed.

0-L TransmissionRelationshipTypeCode EN-US.pngTransmissionRelationshipTypeCode

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.

0-L QueryRequestLimit EN-US.pngQueryRequestLimit

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.

0-L ActExposureLevelCode EN-US.pngActExposureLevelCode

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.

0-L ExposureMode EN-US.pngExposureMode

Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.

0-L HealthcareServiceLocation EN-US.pngHealthcare Service Location

A comprehensive classification of locations and settings where healthcare services are provided. This value set is based on the National Healthcare Safety Network (NHSN) location code system that has been developed over a number of years through CDC's interaction with a variety of healthcare facilities and is intended to serve a variety of reporting needs where coding of healthcare service locations is required.

0-L IdentifierScope EN-US.pngIdentifierScope

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.

0-L IdentifierReliability EN-US.pngIdentifierReliability

Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.

0-L TriggerEventID EN-US.pngTriggerEventID

Description:Trigger Event ID as published in the standard.

0-L TelecommunicationCapabilities EN-US.pngTelecommunicationCapabilities

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.

0-L AddressUse EN-US.pngAddressUse

Description: Uses of Addresses. Lloyd to supply more complete description.

0-L OPINIONS EN-US.pngOnline Product Identification Number Index of Nova Scotia

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

0-L HC-AIC EN-US.pngActive Ingredient Code

Description: A code assigned to any component that has medicinal properties, and supplies pharmacological activity or other direct effect in the diagnosis, cure, mitigation, treatment or prevention of disease, or to affect the structure or any function of the body of man or other animals. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index_e.html

0-L HC-AIGC EN-US.pngActive Ingredient Group Code

Description: Codes for particular grouping of active ingredients. This is the first 5 characters of active ingredient group number. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index_e.html

0-L HC-DIN EN-US.pngHealth Canada Drug Id Number

Description: A Drug Identification Number (DIN) is a number assigned by Health Canada to a drug product prior to being marketed in Canada. It consists of eight digits (numbers) generated by a computer system in the Submission and Information Policy Division. http://www.hc-sc.gc.ca/dhp-mps/prodpharma/databasdon/index_e.html

0-L HC-AIGN EN-US.pngActive Ingredient Group Number

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

0-L HC-NPN EN-US.pngHealth Canada Natural Product Number

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-prod/lnhpd-bdpsnh-eng.php

0-L AHFS EN-US.pngAHFS Pharmacologic-Therapeutic Classification

Description: The AHFS Pharmacologic-Therapeutic Classification has been in use in hospitals in the United States since its inception in 1959. An integral part of the American Hospital Formulary Service, the AHFS classification allows the grouping of drugs with similar pharmacologic, therapeutic, and/or chemical characteristics. Today, the AHFS classification is used by many people outside of hospitals.

0-L BodySite EN-US.pngHL7 table 0163 - Body site

Description: HL7 version 2.x Body site used in chapter(s) 4; HL7 table 0163

0-L EntityNameUseR2 EN-US.pngEntityNameUseR2

Description:A set of codes advising a system or user which name in a set of names to select for a given purpose.

0-L EntityNamePartTypeR2 EN-US.pngEntityNamePartTypeR2

Description:Indicates whether the name part is a given name, family name, prefix, suffix, etc.

0-L EntityNamePartQualifierR2 EN-US.pngEntityNamePartQualifierR2

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.

0-L EPSG_CRS EN-US.pngEuropean Petroleum Survey Group Geodetic Parameter Dataset Coordinate Reference System

Description: The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.

0-L EPSG_CA EN-US.pngEuropean Petroleum Survey Group Geodetic Parameter Dataset Coordinate Axis

Description:The set of values found in the Coord Axis Code column of the Coordinate Axis table as maintained in the EPSG geodetic parameter dataset. These define the axis for coordinate systems for geographic coordinates.

0-L DataOperation EN-US.pngDataOperation

0-L BindingRealm EN-US.pngBindingRealm

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.

0-L hl7V3Conformance EN-US.pngHL7V3Conformance

Description: Identifies allowed codes for HL7aTMs v3 conformance property.

0-L iso21000-6-2004E-RDD EN-US.pngISO/IEC 21000-6:2004(E) Rights Data Dictionary

ISO/IEC 21000-6:2004 describes a Rights Data Dictionary which comprises a set of clear, consistent, structured, integrated and uniquely identified terms to support the MPEG-21 Rights Expression Language (REL), ISO/IEC 21000-5. Annex A specifies the methodology for and structure of the RDD Dictionary, and specifies how further Terms may be defined under the governance of a Registration Authority, requirements for which are described in Annex C. Taken together, these specifications and the RDD Dictionary and Database make up the RDD System. Use of the RDD System will facilitate the accurate exchange and processing of information between interested parties involved in the administration of rights in, and use of, Digital Items, and in particular it is intended to support ISO/IEC 21000-5 (REL). Clause 6 describes how ISO/IEC 21000-6:2004 relates to ISO/IEC 21000-5. As well as providing definitions of terms for use in ISO/IEC 21000-5, the RDD System is designed to support the mapping of terms from different namespaces. Such mapping will enable the transformation of metadata from the terminology of one namespace (or Authority) into that of another namespace. Mapping, to ensure minimum ambiguity or loss of semantic integrity, will be the responsibility of the Registration Authority. Provision of automated trm look-up is also a requirement. The RDD Dictionary is a prescriptive dctionary, in the sense that it defines a single meaning for a trm represented by a particular RddAuthorized TermName, but it is also inclusive in that it can recognize the prescription of other Headwords and definitions by other Authorities and incorporates them through mappings. The RDD Dictionary also supports the circumstance that the same name may have different meanings under different Authorities. ISO/IEC 21000-6:2004describes audit provisions so that additions, amendments and deletions to Terms and their attributes can be tracked. ISO/IEC 21000-6:2004 recognizes legal definitions as and only as Terms from other Authorities that can be mapped into the RDD Dictionary. Therefore Terms that are directly authorized by the RDD Registration Authority neither define nor prescribe intellectual property rights or other legal entities.

0-L ContextConductionStyle EN-US.pngContextConductionStyle

The styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.

0-L MSH EN-US.pngMeSH

Medical Subject Headings (MeSH). Bethesda (MD): National Library of Medicine, 2004

0-L hl7ApprovalStatus EN-US.pngHL7ApprovalStatus

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.

0-L hl7VoteResolution EN-US.pngHL7VoteResolution

Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).

0-L hl7CMETAttribution EN-US.pngHL7CMETAttribution

0-L hl7PublishingSection EN-US.pngHL7PublishingSection

Description: Codes for HL7 publishing 'section's (major business categories)

0-L hl7PublishingSubSection EN-US.pngHL7PublishingSubSection

Description: Codes for HL7 publishing 'sub-section's (business sub-categories)

0-L hl7PublishingDomain EN-US.pngHL7PublishingDomain

Description: Codes for HL7 publishing 'domain's (specific content area)

0-L hl7ITSType EN-US.pngHL7ITSType

Description: Codes identifying types of HL7 Implementation Technology Specifications

0-L RoleLinkStatus EN-US.pngRoleLink Status

Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.

0-L ActUSPrivacyLaw EN-US.pngAct US Privacy Law

Description: A jurisdictional mandate in the US relating to privacy.