Assessment scale TermInfo of observations that together yield a summary evaluation of a particular condition. Examples include the Braden (used for assessing pressure ulcer risk), APGAR Score (used to assess the health of a newborn). association HL7 V3 Core Glossary eference from one class to another class or to itself, or a connection between two objects (instances of classes). For more information refer to the Relationships section of the Version 3 Guide. Attribute HL7 V3 Core Glossary Abstraction of a particular aspect of a class. Attributes become the data values that are passed in HL7 messages. Attribute SCT TermInfo Attributes express characteristics of SNOMED CT concepts. Example: Concept Arthritis IS-A Arthropathy IS-A Inflammatory disorder FINDING-SITE structure ASSOCIATED-MORPHOLOGY Inflammation In this example, Arthritis has two attributes: and ASSOCIATED-MORPHOLOGY. The value of the attribute FINDING-SITE is Joint structure. SNOMED CTconcepts form relationships to each other through attributes. Attribute XML TermInfo Attributes are used to associate name-value pairs with elements. B bag HL7 V3 Core Glossary orm of collection whose members are unordered, and need not be unique. Binding realm Core Principles and Properties of V3 Models ll information models within a particular Binding Realm share the same conformance bindings. In non-technical terms, it can be considered a dialect where speakers use the semantics of the language but agree to use certain terms that are specific to their community; it is a context of use for terminology in HL7 models. Binding Realms may be defined by jurisdictional boundaries and are often HL7 Affiliates, or sub-national jurisdictional entities within the Affiliate purview. Binding Realms may also be based on other factors such as type of patient (e.g. human vs. veterinary, pediatric vs. geriatric), type of medicine (e.g. dentistry vs. psychiatry), etc.. HL7 V3 Core Glossary One of the allowed values for conformance requirements. Blank means that conformance for this element is to be negotiated on a site-specific basis.
CMET HL7 V3 Core Glossary See Common Message Element Type. coded attribute HL7 V3 Core Glossary Attribute in the Reference Information Model (RIM) with a base data type of CD, CE, CS, or CV. coding system HL7 V3 Core Glossary chem for representing concepts usi short concept identifiers to denote the concepts that are members of the system; defines a set of unique concept codes. Examples of coding systems are ICD-9, LOINC and SNOMED. collection HL7 V3 Core Glossary Aggregation of similar objects. The of collection used by HL7 are set, bag, and list. Objects which MAY be found in collections include data types and message element types. common message element type CMET HL7 V3 Core Glossary essage type in a Hierarchical Message Description (HMD) that MAY be included by reference in other HMD's. For more information refer to the Common Message Element Types section of the Version 3 Guide. concept identifier HL7 V3 Core Glossary nique identification assigned to a concept by the HL7 organization. Concept SCT linical concept to a unique ConceptId has been assigned. concept domain Core Principles and Properties of V3 Models An HL7 Concept Domain is a named category of like concepts (a semantic type) that is specified in the Vocabulary Declaration of an attribute in a information model or property in a data type, whose data types are coded or potentially coded, and may be used in a Context Binding. Concept Domains exist to constrain the intent of the coded element while deferring the binding of the element to a specific set of codes until later in the
one or more Hierarchical Message Descriptions (HMD). A single message can be shown as a particular pathway through the classes within an R-MIM. For more information refer to the Information Model section of the Version 3 Guide. required HL7 V3 Core Glossary One of the allowed values in conformance requirements. Abbreviated as R, it means that the message elements SHALL appear every time that particular message type is used for an interaction. If the data is available, the element SHALL carry the data, otherwise a blank MAY be sent. RIM TermInfo See Reference Information Model. Defined in Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5 R-MIM HL7 V3 Core Glossary See Refined Message Information Model. role HL7 V3 Core Glossary . A Reference Information Modelclass that defines the competency of an Entity class. Each role is played by one Entity (the Entity that is in the role) and is usually scoped by another. In UML, each end of an association is designated as a role to reflect the function that class plays in the association. S schema HL7 V3 Core Glossary iagrammatic presentation, a structured framework, or a plan. A set of requirements that need to be met in order for a document or set of data to be a valid expression within the context of a particular grammar. Scope HL7 V3 Core Glossary efinition of the range or extent of a project undertaken by a Technical Committee. SCT TermInfo Systematic Nomenclature of Medicine Clinical Term Section HL7 V3 Core Glossary ethod of grouping related information into domains. domains include Infrastructure Management, Administrative Management, and Health & Clinical Management. Semantic HL7 V3 Core Glossary eaning of something as distinct from its exchange representation. Syntax can change without affecting semantics. semantic interoperability TermInfo receiving application should be able to retrieve and process communicated information, in the same way that it
system HL7 V3 Core Glossary nd user application T TermInfo TermInfo roject started by NASA and adopted by HL7 Vocabulary Committee to define how to use SNOMED in HL7 RIM record transfers. Terminology TermInfo Terms TermInfo member of a terminology; a defined or limited vocabulary of or concepts, for example: ICD, SNOMED, LOINC. tight HL7 V3 Core Glossary Tightly coupled application assume that common information about the subject classes participating in a message is available to system components outside of the specific message. trigger HL7 V3 Core Glossary vent which, when recorded or recognized by an application, indicates the need for an information flow to one or more other applications, resulting in one or more interactions. U uncertaintyCode TermInfo ode indicating whether the Act statement as a whole, with its subordinate components has been asserted to be uncertain in any way. V
Version 3 Guide HL7 V3 Core Glossary A companion to the Version 3 Standard contains the methodological information an HL7 member needs to understand the Version 3 standard. set Core Principles and Properties of V3 Models A Value Set represents a uniquely identifiable set of valid concept identifiers, where any concept identifier in a coded element can be tested to determine whether it is a member of the Value Set at a specific point in time. A concept identifier in a Value Set may be a single concept code or a post-coordinated expression of a combination of codes. vocabulary vocabulary declaration Core Principles and Properties of V3 Models The Vocabulary Declaration identifies the constraints on the coded expressions that can be used as well as the vocabulary conformance expectations for implementers of the data element. A Vocabulary Declaration is the semantic constraint for a coded model element or data type property. W W3C HL7 V3 Core Glossary The Wide Web Consortium, an international industry consortium X XML HL7 V3 Core Glossary See Extensible Markup Language. Y no words starting with Y in this list Z no words starting with Z in this list