Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.1 ActRelationshipsa class in the HL7 clinical statement model. Used to be express links or associations between different clinical statements.
These linkages may be of different types expressed using the typeCode attribute. Examples of typeCode values include “contains”,
“pertain to”, “caused by”, and “reason for”.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.2 AgencyA permanent or semi-permanent organization responsible for the provision of emergency medical services within a given jurisdictional
area
[Source:
Emergency Medical Services]
2.3 Agency EMS Care CertificationLevel of care the agency is permitted to provide by the licensing authority
[Source:
Emergency Medical Services]
2.4 AliquotA portion of a specimen submitted for analysis. It may be scoped by the original specimen. An aliquot is a type of specimen
in which, the player is a material taken as a sample from another pre-existing specimen (scoper). For example the part of
a specimen on which a particular analysis is carried out.
[Source:
Laboratory]
2.5 AlleleMutually exclusive forms of the same gene, occupying the same locus on homologous chromosomes, and governing the same biochemical
and developmental process. In the HL7 model we use the class name IndividualAllele to emphasize that even if it is a non-variant
gene, it is expected that the individual sequencing of the patient gene will have DNA variations such as non-coding SNPs or
SNPs with unknown significance.
[Source:
Clinical Genomics]
2.6 Ambulatory EncounterA comprehensive term for health care provided in a facility or setting that provides diagnostic, therapeutic and health maintenance
services for persons not requiring stays that exceed 24 hours (e.g. a practitioner's office, clinic setting, or hospital)
on a nonresident and non-emergency basis. The term ambulatory usually implies that the patient has come to the location and
is not assigned to a bed. Sometimes referred to as an outpatient encounter.
[Source:
Patient Administration]
2.7 Analysis RegionThe analysis region defines an area in time upon which algorithms performed some analysis. The analysis may be for the derivation
of a median beat, and/or interpretation statements, global measurements, etc. If the rhythm waveforms are long enough to
require (local) analysis in multiple places, a region will define each.
[Source:
Regulated Studies]
2.8 AnimalA subtype of Living Subject representing any animal-of-interest to the Personnel Management domain. An instance of an animal
is uniquely identifiable and, as a result, able to be certified, licensed, or otherwise credentialed by an appropriate Credentialing
Authority for the purpose of involvement in one or more healthcare processes. Examples include a German Shepard trained as
a seeing eye dog, or a kitten licensed to a patient for comfort therapy.
[Source:
Personnel Management]
2.9 AnimalA subtype of Living Subject representing any animal-of-interest to the Personnel Management domain. An instance of an animal
is uniquely identifiable and, as a result, able to be certified, licensed, or otherwise credentialed by an appropriate Credentialing
Authority for the purpose of involvement in one or more healthcare processes. Examples include a German Shepard trained as
a seeing eye dog, or a kitten licensed to a patient for comfort therapy.
[Source:
Personnel Management]
2.10 AnimalA subtype of Living Subject representing any animal-of-interest to the Personnel Management domain. An instance of an animal
is uniquely identifiable and, as a result, able to be certified, licensed, or otherwise credentialed by an appropriate Credentialing
Authority for the purpose of involvement in one or more healthcare processes. Examples include a German Shepard trained as
a seeing eye dog, or a kitten licensed to a patient for comfort therapy.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.11 AnimalA subtype of Living Subject representing any animal-of-interest to the Personnel Management domain. An instance of an animal
is uniquely identifiable and, as a result, able to be certified, licensed, or otherwise credentialed by an appropriate Credentialing
Authority for the purpose of involvement in one or more healthcare processes. Examples include a German Shepard trained as
a seeing eye dog, or a kitten licensed to a patient for comfort therapy.
[Source:
Personnel Management]
2.12 AnimalA subtype of Living Subject representing any animal-of-interest to the Personnel Management domain. An instance of an animal
is uniquely identifiable and, as a result, able to be certified, licensed, or otherwise credentialed by an appropriate Credentialing
Authority for the purpose of involvement in one or more healthcare processes. Examples include a German Shepard trained as
a seeing eye dog, or a kitten licensed to a patient for comfort therapy.
[Source:
Personnel Management]
2.13 annotation
A note following a
Domain Message Information Model (DMIM) diagram that
explains the DMIM or the modeling behind the DMIM.
[Source:
Core Glossary]
2.14 ANSIAmerican National Standards Institute (www.ansi.org)
[Source:
Emergency Medical Services]
2.15 ANSIAmerican National Standards Institute
[Source:
Core Glossary]
2.16 AntigenA foreign substance, such as a transplanted organ, that triggers the body to try to destroy it. This response may be the production
of antibodies, which try to destroy the antigen (the transplanted organ).
[Source:
Clinical Genomics]
2.17 AntigenA component of a disease-causing agent that stimulates an immune response. More commonly, the disease which a vaccine is supposed
to protect against. In the context of immunization, the latter is the meaning of interest.
[Source:
Immunization]
2.18 ApplicationThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.19 ApplicationThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.20 ApplicationThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.21 ApplicationAll submissions that are grouped together for regulatory purposes.
[Source:
Regulated Products]
2.22 ApplicationThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.23 ApplicationThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.24 application
A software program or set of related programs that provide
some useful healthcare capability or functionality.
[Source:
Core Glossary]
2.25 Application or AssignmentThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.26 Application or AssignmentThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.27 Application or AssignmentThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.28 Application or AssignmentThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.29 Application or AssignmentThe collection of data (structured and unstructured) that a Person submits to an organization in the context of requesting
or applying for/being assigned to a Position. (NOTE: An Application does NOT include the Person's Qualifications or various
Credentials (which are represented explicitly elsewhere in the model), but is simply a signed or otherwise verified statement
by the Person applying for the Position that the data submitted in the context of the application process (including the Person's
Qualifications/Credentials) are complete, accurate, etc. An Attestation is normally date/time stamped.)
[Source:
Personnel Management]
2.30 application role
An abstraction that expresses a portion of the messaging behavior of an
information system.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.31 artifact
Any deliverable resulting from the discovery, analysis, and design activities
leading to the creation of
message specifications.
[Source:
Core Glossary]
2.32 ASCIIAmerican Standard Code for Information Interchange, a common 8-bit character encoding set
[Source:
Core Glossary]
2.33 Assessment or evaluationThe assessment or evaluation is a determination of whether vaccine doses administered to a patient are valid based on an accepted
immunization schedule.
[Source:
Immunization]
2.34 Assessment scalea collection of observations that together yield a summary evaluation of a particular condition. Examples include the Braden
Scale (used for assessing pressure ulcer risk), APGAR Score (used to assess the health of a newborn).
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.35 AssignmentA collection of data documenting the association between an instance of a Party (normally a Person) and a Position. The
minimal data in an Assignment are date/time of Assignment and Person/Organization making the Assignment. An Assignment also
usually includes a time period after which the Assignment is invalid and must be redone if the association between the Person
and the Position is to continue.
[Source:
Personnel Management]
2.36 AssignmentA collection of data documenting the association between an instance of a Party (normally a Person) and a Position. The
minimal data in an Assignment are date/time of Assignment and Person/Organization making the Assignment. An Assignment also
usually includes a time period after which the Assignment is invalid and must be redone if the association between the Person
and the Position is to continue.
[Source:
Personnel Management]
2.37 AssignmentA collection of data documenting the association between an instance of a Party (normally a Person) and a Position. The
minimal data in an Assignment are date/time of Assignment and Person/Organization making the Assignment. An Assignment also
usually includes a time period after which the Assignment is invalid and must be redone if the association between the Person
and the Position is to continue.
[Source:
Personnel Management]
2.38 AssignmentA collection of data documenting the association between an instance of a Party (normally a Person) and a Position. The
minimal data in an Assignment are date/time of Assignment and Person/Organization making the Assignment. An Assignment also
usually includes a time period after which the Assignment is invalid and must be redone if the association between the Person
and the Position is to continue.
[Source:
Personnel Management]
2.39 AssignmentA collection of data documenting the association between an instance of a Party (normally a Person) and a Position. The
minimal data in an Assignment are date/time of Assignment and Person/Organization making the Assignment. An Assignment also
usually includes a time period after which the Assignment is invalid and must be redone if the association between the Person
and the Position is to continue.
[Source:
Personnel Management]
2.40 association
A reference 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.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.41 association composition
See
composite
aggregation
[Source:
Core Glossary]
2.42 association role name
A name for each end of an
association.
The name is a short verb phrase depicting the
role of the
class at
the opposite end of the association from the perspective of
the class adjacent to the role.
[Source:
Core Glossary]
2.43 attribute
An abstraction of a particular aspect of a
class. Attributes become the
data values that are passed in HL7
messages.
For more information refer to the
Attributes section of the Version 3 Guide.
[Source:
Core Glossary]
2.44 Attribute (HL7)An abstraction of a particular aspect of a class. Attributes become the data values that are passed in HL7 messages.
For more information refer to the Attributes section of the V3 Guide.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.45 Attribute (SCT)Attributes express characteristics of SNOMED CT concepts. Example:
Concept Arthritis
IS-A Arthropathy
IS-A Inflammatory disorder
FINDING-SITE Joint structure
ASSOCIATED-MORPHOLOGY Inflammation
In this example, Arthritis has two attributes: FINDING-SITE and ASSOCIATED-MORPHOLOGY. The value of the attribute FINDING-SITE
is Joint structure.
SNOMED CT concepts form relationships to each other through attributes.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.46 Attribute (XML)Attributes are used to associate name-value pairs with elements.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.47 attribute type
A classifier for the meaning of an
attribute. In HL7 Version 3, attribute type is
indicated by a suffix added to the attribute name.
[Source:
Core Glossary]
2.48 AuthorAuthor is 'A party that originates an act and therefore has responsibility for the information
given in the act and ownership of this Act. Example: the report writer, the person writing the act
definition, the guideline author, the placer of an order, the EKG cart (device) creating a report, etc.
Every Act should have an Author...' -HL7 RIM Definition
When combined with the Care Provision Act, the implication is that the author
has current responsibility for Care Provision or responsibility for coordination of Care Provision
to the Targets of Care. Two use cases are important:
1) When the author and performer are the same, then the statement of
responsibility regards the author as performer.
2) When the author and performer are the same, then the statement of
responsibility regards the author as performer.
When the author and performer are different, then
the statement of responsibility regards the performer.
The set of use cases implied is that the responsibility for care is being:
1) Started or continued by the author (mood = event), a)for the author or b)for another performer
2) Requested form another performer (mod = request)
Promised by the author (mood = promise)
Rejected by the author (mood = event)
Discontinued by the author (mood = event), a) for the author or b) for another performer
[Source:
Care Provision]
2.49 AutologousA blood donation where the donor is the intended recipient.
[Source:
Blood, Tissue and Organ]
2.50 bag
A form of
collection whose
members are unordered, and need not be unique.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.51 BatteryA battery is a set of closely related observations. The components of a battery should have a generally accepted clinical,
functional or logical relationship to one another. In event mood a battery contains separate valued observations for
each of its subcomponents. In definition mood a battery defines a set of required and optional subcomponents. A request
for battery may be represented as a single observation in request mood with a code that refers to the defined set of
subcomponents. Examples include blood pressure, complete blood count, chemistry panel.
[Source:
Laboratory]
2.52 BBAbreviation for Blood Bank
[Source:
Blood, Tissue and Organ]
2.53 blank
One of the allowed values for
conformance
requirements. Blank means that conformance for this
element is to be negotiated on a site-specific basis.
[Source:
Core Glossary]
2.54 Bone MarrowA spongy tissue inside large bones where the body blood cells (red blood cells, white blood cells and platelets) are made.
[Source:
Clinical Genomics]
2.55 Bone Marrow Transplant (BMT)Healthy bone marrow is given to patients whose marrow is damaged.
[Source:
Clinical Genomics]
2.56 BTOAbreviation for Blood, Tissue & Organ
[Source:
Blood, Tissue and Organ]
2.57 BystanderA person who witnesses an emergency and is able to notify an EMS agency or provide information to an EMS crew
[Source:
Emergency Medical Services]
2.58 Canonical formthe standard or basic structure of a post coordinated expression, a set of linked concepts
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.59 CAPThe College of American Pathologists. A not-for-profit medical society serving nearly 16,000 physician members and the laboratory
community throughout the world. The College of American Pathologists, In collaboration with the United Kingdom’s National
Health Service, developed SNOMED Clinical Terms.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.60 CapabilityA quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.61 CapabilityA quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
[Source:
Personnel Management]
2.62 CapabilityA quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
[Source:
Personnel Management]
2.63 CapabilityA quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
[Source:
Personnel Management]
2.64 CapabilityA quantitative, semi-quantitative, or qualitative assessment of the ability of an instance of a Party in a Role to perform
and/or participate in a specific activity or task. An a subtype of Credential, a Capability is assigned to an instance of
a Party (the instance with the ability) by another instance of Party (the Person or Organization assessing the capability).
A Capability is often a specific (e.g. 'can do this task' (Person), or 'has 5 slots available' (Organization)).
[Source:
Personnel Management]
2.65 cardinality
Property of a data element (the number of times a data element
MAY repeat within an individual occurrence of an object view)
or column in the
Hierarchical Message Description (the minimum and
maximum number of occurrences of the
message element).
[Source:
Core Glossary]
2.66 Care Provider"Performer" is an HL7 Participation that identifies 'A person who actually and principally carries out the action...may be
the patient in self-care...' -HL7 RIM Definition
When combined with the Care Provision Act, the post-coordinated concept is "Care Provider."
[Source:
Care Provision]
2.67 Care Provision"CareProvision" is an HL7 Act that describes 'the taking on of the responsibility by a performer for care activities of a
subject of care.
Discussion: The care event can exist without any care actions having taken place. The scope of the care is identified by Act.code.
For example:
Preferred primary care provision: the primary care physician being the primary performer participation, author being the patient;
Referral from general practitioner to specialist (a PCPR in request mood, where the author participant is the GP, and the
primary performer participation is the specialist);
A case manager to a patient or group of patients;
Assigning nurses to patients each shift;
Care of herd of animals;
Care of contaminated environmental site;
Care of a device.
[Source:
Care Provision]
2.68 CDAClinical Document Architecture -- Specification for the structure and semantics of "clinical documents" for the purpose of exchange.-
[Source:
Core Glossary]
2.69 CertificateA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
[Source:
Personnel Management]
2.70 CertificateA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.71 CertificateA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
[Source:
Personnel Management]
2.72 CertificateA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
[Source:
Personnel Management]
2.73 CertificateA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the Certificate. A Certificate is often viewed as
'less formal' than a Credential. However, in this model, a Credential is an abstract concept that captures the notion of
verifiable documentation various types of skills, etc. claimed to be possessed by a Person or Organization (see Credential)
[Source:
Personnel Management]
2.74 Certificate of medical necessitySee Certification of Transport Necessity
[Source:
Emergency Medical Services]
2.75 Certificate of VerificationA collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
[Source:
Personnel Management]
2.76 Certificate of VerificationA collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
[Source:
Personnel Management]
2.77 Certificate of VerificationA collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
[Source:
Personnel Management]
2.78 Certificate of VerificationA collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
[Source:
Personnel Management]
2.79 Certificate of VerificationA collection of data documenting that a specific instance of a Credential has been verified/validated in association with
the requirement for that credential for either an Assignment of a Party in a Role to a Position or the requirement for a particular
instance of a Credential in order for a Party in a Role to qualify for a specific instance of a Privilege. A Certificate
of Verification will minimally include a definitive identification of the verifier, a date/time stamp of verification, and
(optionally) a structured or unstructured statement of the verification process, contacts, etc.
[Source:
Personnel Management]
2.80 Certification Of Transport NecessityAn attestation for billing purposes that transport services are medically indicated
[Source:
Emergency Medical Services]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.81 Character DataText in a particular coding (e.g., ASCII), as distinguished from binary data.
[Source:
Core Glossary]
2.82 Chief ComplaintThe primary reason a patient requires attention; typically the only complaint treated
[Source:
Emergency Medical Services]
2.83 choice
A
message construct that includes
alternative portions of the message. For a choice due to
specialization, the sender picks one of the alternatives and
sends it along with a flag.
[Source:
Core Glossary]
2.84 choice due to specialization
A choice that arises when a
Hierarchical Message
Description includes (a) an object view which is associated
with a
class that is a
superclass of two or more object
views, or (b) an object view which is a superclass of one or more object
views and MAY itself be instantiated. Under this circumstance different
message instances MAY contain
different object views. The choice structure is used to
accommodate the alternatives.
[Source:
Core Glossary]
2.85 class
An abstraction of a thing or concept in a particular
application
domain.
For more information refer to the
Classes
section of the Version 3 Guide.
[Source:
Core Glossary]
2.86 Class I AntigensThere are two classes of MHC antigens, Class I and Class II. Class I antigens alert killer T-cells (T-8 or CD-8 protein) to
the presence of body cells that have been invaded by bacteria or viruses, or changed by cancer or disease.
[Source:
Clinical Genomics]
2.87 Class II AntigensClass II antigens, located on B-cells and other immune cells, can capture and break down antigens, making them more visible
to the helper T-cells (T-4 or CD-4 protein).
[Source:
Clinical Genomics]
2.88 classifier attribute
An
attribute used in
generalization
hierarchies to indicate which of the
specializations
is the focus of the
class
.
For more information refer to the
Attributes section of the Version 3 Guide.
[Source:
Core Glossary]
2.89 Client/patientThe person receiving the immunizations or having recommendations made.
[Source:
Immunization]
2.90 Clinical decision supportThe ability to use data to discover/justify the proper activities planned for a patient.
[Source:
Care Provision]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.91 Clinical DocumentA clinical document is a documentation of clinical observations and services, with the following characteristics:
- Persistence: A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory
requirements (NOTE: There is a distinct scope of persistence for a clinical document, independent of the persistence of any
XML-encoded CDA document instance).
- Stewardship: A clinical document is maintained by an organization entrusted with its care.
- Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated.
- Context: A clinical document establishes the default context for its contents.
- Wholeness: Authentication of a clinical document applies to the whole and does not apply to portions of the document without
the full context of the document.
- Human readability: A clinical document is human readable.
A CDA document is a defined and complete information object that can include text, images, sounds, and other multimedia content.
[Source:
Clinical Document Architecture]
2.92 Clinical finding (SCT)Concepts that represent the result of a clinical observation, assessment or judgment. These concepts are used for documenting
clinical disorders and symptoms and examination findings.
Within the “clinical finding” hierarchy is the sub-hierarchy of “disease”. Concepts that are descendants of “disease” are
always and necessarily abnormal.
Note: As expected, this definition includes concepts that would be used to represent HL7 Observations. However, it is worth
noting that the definition of a finding in SNOMED CT is that it combines the question (see Observable entity) with the answering
value.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.93 Clinical PhenotypePhenotype is properties that are observed. In the case of clinical phenotype it is the clinical condition such as disease,
sensitivity to a drug etc that are observed in an individual.
[Source:
Clinical Genomics]
2.94 Clinical StatementAn expression of a discrete item of clinical, clinically-related or public health information that is recorded because of
its relevance to the care of patients (persons, animals and other entities). Clinical or public health information can be
expressed with different levels of granularity and therefore the extent and detail conveyed in a single statement may vary.
To be regarded as a Clinical Statement, a concept must be associated with a patient or other entity in a manner which makes
clear:
-
Its temporal context
-
Its relationship to the entity or entities
-
In the case of an observation, its mood and presence, absence or value
-
In the case of a procedure, its mood and status
This clarity may be achieved by
[Source:
Clinical Statement]
2.95 Clinical statement model HL7
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.96 clinical statement pattern
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.97 clinical statement project HL7
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.98 clone
A
class from the
Reference
Information Model
(RIM) that has been used in a specialized context and whose
name differs from the RIM class from which it was replicated.
This makes it possible to represent specialized uses of more
general classes to support the needs of messaging.
[Source:
Core Glossary]
2.99 CMET
See
Common Message Element Type.
[Source:
Core Glossary]
2.100 CMET Message Information Model
A form of
Refined Message Information Model (RMIM) constructed
to represent the totality of concepts embodied in the individual RMIMs
needed to support the definition of HL7's
Common Message Element Types.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.101 CMIM
See
CMET Message
Information Model.
[Source:
Core Glossary]
2.102 CNESee
extensibility qualifier
[Source:
Core Glossary]
2.103 coded attribute
An
attribute in the
Reference
Information Model
(RIM) with a base
data type of
CD, CE, CS, or CV.
[Source:
Core Glossary]
2.104 Coded, No ExtensionsSee
extensibility qualifier
[Source:
Core Glossary]
2.105 Coded, With ExtensionsSee
extensibility qualifier
[Source:
Core Glossary]
2.106 coding strength
An
extensibility qualifier
that specifies whether or not a code set can be expanded to meet
local implementation needs.
[Source:
Core Glossary]
2.107 coding system
A scheme for representing concepts using (usually) 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.
[Source:
Core Glossary]
2.108 Collaborating'To work jointly with others'-Webster
This use assumes the care providers are collaborating around the care of a specific subject.
[Source:
Care Provision]
2.109 collection
An aggregation of similar
objects.
The forms of collection used by HL7 are
set
,
bag, and
list. Objects which MAY be
found in collections include
data types
and
message element
types.
[Source:
Core Glossary]
2.110 common message element type (CMET)
A
message 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.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.111 Component rulesThe collection of rules relating to all schedule doses in a schedule series.
[Source:
Immunization]
2.112 composite aggregation
A type of
association between
objects, indicating a
whole-part relationship.
[Source:
Core Glossary]
2.113 composite data type
A
data type assigned to a
message element type that
contains one or more components, each of which is represented
by an assigned data type.
[Source:
Core Glossary]
2.114 composite message element type
A
message element type
that contains subordinate heterogeneous
message
types.
[Source:
Core Glossary]
2.115 Concept (SCT)A clinical concept to which a unique ConceptId has been assigned.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.116 concept identifier
A unique identification assigned to a concept by the
HL7 organization.
[Source:
Core Glossary]
2.117 Concepts a member of a terminology; a defined or limited vocabulary of terms or concepts, for example: ICD, SNOMED, LOINC.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.118 conformance claim
A
specification written by HL7
to precisely define the behavior of an application with respect
to its HL7 interfaces, and which MAY be designated functional
or technical. A functional conformance claim is simply a
statement that an application conforms to a particular
application role. A technical
conformance claim (also referred to as a Technical Statements of Performance
Criteria) defines the behavior of an application in some
other sense than the
messages it
sends or receives. This MAY include the
Implementation Technology
Specifications that it supports, the use of specific
optional protocols or character sets, or many other
behaviors.
[Source:
Core Glossary]
2.119 conformance claim set
A list of the identifiers of specific HL7
conformance claims, used by a
sponsor to describe the conformance of its application.
[Source:
Core Glossary]
2.120 conformance requirement
A column in the
Hierarchical Message
Description (HMD) that designates whether the
system SHALL communicate an
attribute's
value if a value is available. Allowed values are
required (must be included),
not required (may be left out) or
not
permitted (may never be included.) Items listed as
not required in the HL7 specification SHALL be declared by a
vendor as either required or not permitted when a
conformance claim is asserted
for that
message type.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.121 conformance verbIn HL7 Version 3 Specifications, the correct verb form for indicating a requirement is "SHALL." The correct verb form for
indicating a recommendation is "SHOULD." The correct verb form for an option is "MAY."
Universally accepted standardization terminology does not recognize "must". Use "SHALL" to indicate a mandatory aspect or
an aspect on which there is no option.
The negatives are SHALL NOT, SHOULD NOT, MAY NOT.
The Publishing Facilitator's Guide requires the Conformance Verbs to be capitalized when they are used to indicate conformance
criteria, to differentiate from common usage of the words.
The source for this usage is ANSI.
[Source:
Core Glossary]
2.122 connection
In an
information model, a
specified relationship between two
classes
.
[Source:
Core Glossary]
2.123 constraint
Narrowing down of the possible values for an
attribute; a suggestion of
legal values for an attribute (by indicating the
data type that applies, by
restriction of the data type, or by definition
of the
domain of an attribute as
a subset of the domain of its data type). MAY also include
providing restrictions on data types. A constraint imposed on
an
association MAY limit the
cardinality of the association
or alter the navigability of the association (direction in which
the association can be navigated). A
Refined Message Information Model (RMIM)
class MAY be constrained by
choosing a subset of its
Reference
Information Model (RIM) properties (i.e., classes
and attributes) or by cloning, in which the class’ name is
changed.
For more information refer to the
Constraints section of the Version 3 Guide.
[Source:
Core Glossary]
2.124 ConsultandIndividual (s) seeking genetic counseling/tetsing.
[Source:
Clinical Genomics]
2.125 contact CMETA CMET variant that provides sufficient information to allow the object identified to be contacted. This is likely to have
the content of identified and confirmable plus telephone number.
[Source:
Common Model Element Types]
2.126 Context modelconcepts can be placed in defined or refined in specific contexts related to subject (e.g. subject of record, family member,
disease contact, etc.), time, finding (e.g. unknown, present, absent, goal, expectation, risk, etc.) or procedure (e.g. not
done, not to be done, planned, requested, etc)
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.127 control event wrapper
A
wrapper that contains
domain specific administrative
information related to the "controlled event" which is being
communicated as a messaging interaction. The control event
wrapper is used only in
messages
that convey status, or in commands for logical operations being
coordinated between applications (e.g., the coordination of
query specification/query response interactions).
[Source:
Core Glossary]
2.128 coupling
-
1. An interaction between systems or between properties of a system.
-
2. With regard to application roles
, refers to whether or not additional information
about the subject classes
participating in a message may be
commonly available to system components outside of the specific message.
[Source:
Core Glossary]
2.129 CPRCardio-pulmonary resuscitation
[Source:
Emergency Medical Services]
2.130 CredentialA license issued by a regulatory authority permitting a person or agency to provide a service, or a certification issued by
a professional organization attesting to that person or organization's capability to provide a service
[Source:
Emergency Medical Services]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.131 Credential (Definition and Instantiation)An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
[Source:
Personnel Management]
2.132 Credential (Definition and Instantiation)An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
[Source:
Personnel Management]
2.133 Credential (Definition and Instantiation)An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
[Source:
Personnel Management]
2.134 Credential (Definition and Instantiation)An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
[Source:
Personnel Management]
2.135 Credential (Definition and Instantiation)An abstract concept (i.e. there are no physical instances of Credential per se) that represents the various collections of
data associated with a verifiable claim by a Person or Organization as to one or more skills, abilities, education, experience,
etc. A Credential collects (at minimum) the date/time of issuance and an associated expiration date after which the credential
must be renewed to remain valid. The important differentiator between a Credential (or, more correctly, one of its concrete
subtypes) and a Qualification is that the former (Credential) can always be verified in terms of the Credential being issued
by/associated with a 'credentialing organization' responsible for issuing an instance of a particular credential to an instance
of a Party, whereas the latter (Qualification) is simply a statement by the Party of a particular skill, ability, etc. (NOTE:
The notion of 'verifiable' that differentiates a Credential from a Qualification is similar to the difference between a Responsibility
and a Privilege in that both a Credential and a Privilege involve a formal relationship between at least two instances of
Party, whereas a Qualification and a Responsibility do not possess this level of 'contract' formalism.)
[Source:
Personnel Management]
2.136 CrewThe normal set of EMS professionals dispatched with a unit
[Source:
Emergency Medical Services]
2.137 CriterionA rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
[Source:
Personnel Management]
2.138 CriterionA rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
[Source:
Personnel Management]
2.139 CriterionA rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
[Source:
Personnel Management]
2.140 CriterionA rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.141 CriterionA rule which defines the manner in which a particular Qualification (including a Credential) or collection of Qualifications
are associated with a given Position. An instance of a Criterion may be either a Time-based Criterion (e.g. <xxx> for at
least 3 years) or a Non-time-based Criterion (e.g. certified as either an <x> or a <y>).
[Source:
Personnel Management]
2.142 CWESee
extensibility qualifier
[Source:
Core Glossary]
2.143 DAMDomain analysis model: An information model constructed to represent the concepts in a problem domain.
[Source:
Emergency Medical Services]
2.144 data type
The structural format of the data carried in an
attribute.
It MAY
constrain the set of
values an attribute may assume.
For more information refer to the
Data Types section of the Version 3 Guide.
[Source:
Core Glossary]
2.145 DCIData Collection Instrument. A specification of a structured set of fields for which values are to be collected in the course
of a clinical trial.
[Source:
Regulated Studies]
2.146 default value
In HL7
messages, the value for an
attribute that is to be used by
message receivers if no value is given.
[Source:
Core Glossary]
2.147 DescriptionA structured or non-structured collection of (usually) text that collectively defines an instance of a Position. Examples
include 'Job Descriptions' on file for the various Jobs/Job Titles within an Organization.
[Source:
Personnel Management]
2.148 DescriptionA structured or non-structured collection of (usually) text that collectively defines an instance of a Position. Examples
include 'Job Descriptions' on file for the various Jobs/Job Titles within an Organization.
[Source:
Personnel Management]
2.149 DescriptionA structured or non-structured collection of (usually) text that collectively defines an instance of a Position. Examples
include 'Job Descriptions' on file for the various Jobs/Job Titles within an Organization.
[Source:
Personnel Management]
2.150 DescriptionA structured or non-structured collection of (usually) text that collectively defines an instance of a Position. Examples
include 'Job Descriptions' on file for the various Jobs/Job Titles within an Organization.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.151 DescriptionA structured or non-structured collection of (usually) text that collectively defines an instance of a Position. Examples
include 'Job Descriptions' on file for the various Jobs/Job Titles within an Organization.
[Source:
Personnel Management]
2.152 Determinant PeptideA conserved region of a protein responsible for the certain function of the protein.
[Source:
Clinical Genomics]
2.153 Diagnosisresult of a cognitive process whereby signs, symptoms, test results, and other relevant data are evaluated to determine the
condition afflicting a patient, directs administrative and clinical workflow, where for instance the assertion of an admission
diagnosis establishes care paths, order sets, etc., something that is billed for in a clinical encounter. In such a scenario,
an application typically has a defined context where the billable object gets entered.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.154 DICOMDigital Imaging and Communication in Medicine
[Source:
Core Glossary]
2.155 DICOM, SRDICOM Structured Reporting
[Source:
Core Glossary]
2.156 DispatchThe process of identifying an appropriate unit for the type of notification received and instructing that unit to respond
[Source:
Emergency Medical Services]
2.157 DispositionDomain message information model: A constrained information model constructed to represent the concepts in a problem domain
in a form in which every feature is assigned to a corresponding feature in the HL7 Reference Information Model. Due to its
implication of message-specificity, the use of this term may be discontinued.
[Source:
Emergency Medical Services]
2.158 distal class
From the perspective of a
class
in an
information model, it is
the class at the opposite end of an
association between the two.
[Source:
Core Glossary]
2.159 DMIM
See
Domain Message Information Model.
[Source:
Core Glossary]
2.160 DocumentRegulatory processes require the submission of documents from the Applicant to the Regulatory Authority. These documents are
varied in focus and are often defined by the field of study (i.e., GLP or GCP guidelines) or by the regulatory application
requirements of the region or Regulatory Authority (e.g., Integrated Summary of Safety, Pharmacokinetics Written Summary).
The RPS message specification provides for the defining of documents in the message.
[Source:
Regulated Products]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.161 Document RootThe element in an
XML document that contains all other elements; the first element in a document.
[Source:
Core Glossary]
2.162 domain
-
1. A particular area of interest. For example, the domain for HL7 is
healthcare.
-
2. The set of possible values of a data type
, attribute, or data
type component. See also vocabulary domain
.
-
3. A special interest group within HL7,
such as Pharmacy, Laboratory, or Patient Administration.
[Source:
Core Glossary]
2.163 domain expert
An individual who is knowledgeable about the concepts in a
particular problem area within the healthcare arena and/or is
experienced with using or providing the functionality of that area.
[Source:
Core Glossary]
2.164 Domain Message Information Model
A form of
Refined Message
Information Model (RMIM) constructed to represent
the totality of concepts embodied in the individual RMIMs
needed to support the communication requirements of a particular
HL7 domain.
For more information refer to the
Information Model
section of the Version 3 Guide.
[Source:
Core Glossary]
2.165 domain name
The name assigned to a
vocabulary domain.
[Source:
Core Glossary]
2.166 domain specification
The specification of a
vocabulary domain.
[Source:
Core Glossary]
2.167 DonorAn individual from whom an organ or tissue is removed for transplantation.
[Source:
Clinical Genomics]
2.168 Dose rulesDose rules are the dose specific rules that validate a given immunization or control the recommendations for the next dose.
[Source:
Immunization]
2.169 Down's syndromeThis syndrome is associated with a chromosomal condition where the individual has 47 instead of 46 chromosomes. This syndrome
is associated with mental retardation.
[Source:
Clinical Genomics]
2.170 EducationA subtype of Credential that documents a particular Person's accomplishments, awards, skills, time of involvement, etc. in
the context of a recognized educational institution (e.g. high school, college, graduate school, non-degree granting training
programs, vocational training, etc.)
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.171 EducationA subtype of Credential that documents a particular Person's accomplishments, awards, skills, time of involvement, etc. in
the context of a recognized educational institution (e.g. high school, college, graduate school, non-degree granting training
programs, vocational training, etc.)
[Source:
Personnel Management]
2.172 EducationA subtype of Credential that documents a particular Person's accomplishments, awards, skills, time of involvement, etc. in
the context of a recognized educational institution (e.g. high school, college, graduate school, non-degree granting training
programs, vocational training, etc.)
[Source:
Personnel Management]
2.173 EducationA subtype of Credential that documents a particular Person's accomplishments, awards, skills, time of involvement, etc. in
the context of a recognized educational institution (e.g. high school, college, graduate school, non-degree granting training
programs, vocational training, etc.)
[Source:
Personnel Management]
2.174 EducationA subtype of Credential that documents a particular Person's accomplishments, awards, skills, time of involvement, etc. in
the context of a recognized educational institution (e.g. high school, college, graduate school, non-degree granting training
programs, vocational training, etc.)
[Source:
Personnel Management]
2.175 EMDEmergency Medical Dispatch
[Source:
Emergency Medical Services]
2.176 Emergency EncounterA patient encounter that takes place at a dedicated healthcare service delivery location where the patient receives immediate
evaluation and treatment, provided until the patient can be discharged or responsibility for the patient's care is transferred
elsewhere (for example, the patient could be admitted as an inpatient or transferred to another facility.)
[Source:
Patient Administration]
2.177 EMSEmergency medical services: a branch of emergency services dedicated to providing out-of-hospital acute medical care and/or
transport to definitive care, to patients with illnesses and injuries which the patient, or the medical practitioner, believes
constitutes a medical emergency.
[Source:
Emergency Medical Services]
2.178 EMS IncidentAn event requiring emergency medical services, including inter-facility transport needs as well as disasters, accidents, and
other mishaps
[Source:
Emergency Medical Services]
2.179 EMS Incident LocationThe location where the emergency occurs, and to which the EMS unit is dispatched
[Source:
Emergency Medical Services]
2.180 EMS ProfessionalA person trained and licensed to provide EMS services
[Source:
Emergency Medical Services]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.181 EncounterAn interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing
the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical
therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational
therapy, telephone call.
[Source:
Patient Administration]
2.182 Encounter, AmbulatorySee term
Ambulatory Encounter instead.
[Source:
Patient Administration]
2.183 Encounter, EmergencySee term
Emergency Encounter instead.
[Source:
Patient Administration]
2.184 Encounter, FieldSee term
Field Encounter instead.
[Source:
Patient Administration]
2.185 Encounter, Home HealthSee term
Home Health Encounter instead.
[Source:
Patient Administration]
2.186 Encounter, InpatientSee term
Inpatient Encounter instead.
[Source:
Patient Administration]
2.187 Encounter, Short StaySee term
Short Stay Encounter instead.
[Source:
Patient Administration]
2.188 Encounter, VirtualSee term
Virtual Encounter instead.
[Source:
Patient Administration]
2.189 entry point
The point at which a
Common Message Element Type (CMET) is inserted into a
Refined Message Information Model
(RMIM).
[Source:
Core Glossary]
2.190 Episode of Care"Encounter" is an HL7 Class that describes 'An interaction between a patient and healthcare participant(s) for the purpose
of providing patient service(s) or assessing the health status of a patient.' - HL7 RIM Definition
Episode of Care is a collection of one or more encounters that address the same target of care and that include a relationship
to the same Episode of Illness or Condition
[Source:
Care Provision]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.191 event
-
1. A stimulus that causes a noteworthy change in the
state of an
object, or a signal that invokes the behavior of an
object. See also trigger event.
-
2. A vocabulary domain
value for Mood.
[Source:
Core Glossary]
2.192 Event Mood'Event' is 'A service that actually happens, may be an ongoing service or a documentation of a past service.' - HL7 RIM Definition
When combined with the Act Care Provision and a Performer, the Event Mood of the Act distinguishes whether the performer actually
has (or had) Responsibility for Care.
[Source:
Care Provision]
2.193 ExperienceA subtype of Credential that documents a particular instance of Party's (most often a Person's) accomplishments, skills, time
of involvement, etc. in a particular context, usually a Position or Role. QUESTION: Is this where Internship, Residency,
etc. go?
[Source:
Personnel Management]
2.194 ExperienceA subtype of Credential that documents a particular instance of Party's (most often a Person's) accomplishments, skills, time
of involvement, etc. in a particular context, usually a Position or Role. QUESTION: Is this where Internship, Residency,
etc. go?
[Source:
Personnel Management]
2.195 ExperienceA subtype of Credential that documents a particular instance of Party's (most often a Person's) accomplishments, skills, time
of involvement, etc. in a particular context, usually a Position or Role. QUESTION: Is this where Internship, Residency,
etc. go?
[Source:
Personnel Management]
2.196 ExperienceA subtype of Credential that documents a particular instance of Party's (most often a Person's) accomplishments, skills, time
of involvement, etc. in a particular context, usually a Position or Role. QUESTION: Is this where Internship, Residency,
etc. go?
[Source:
Personnel Management]
2.197 ExperienceA subtype of Credential that documents a particular instance of Party's (most often a Person's) accomplishments, skills, time
of involvement, etc. in a particular context, usually a Position or Role. QUESTION: Is this where Internship, Residency,
etc. go?
[Source:
Personnel Management]
2.198 Expression (SCT)A collection of references to one or more concepts used to express an instance of a clinical idea.
An expression containing a single concept identifier is referred to as a pre-coordinated expression. An expression that contains
two or more concept identifiers is a post-coordinated expression. The concept identifiers within a post-coordinated expression
are related to one another in accordance rules expressed in the SNOMED CT Concept Model. These rules allow concepts to be:
- combined to represent clinical ideas which are subtypes of all the referenced concepts
- E.g. “tuberculosis” + “lung infection”
- applied as refinements to specified attributes of a more general concept.
- E.g. “asthma” : “severity” = “severe”
Notes:
The SNOMED CT compositional grammar provides one way to represent an expression.
The HL7 messaging standard supports communication of SNOMED CT expressions using the “concept descriptor” (CD) data type.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.199 extensibility qualifier
A
vocabulary domain qualifier
used in a
domain specification,
which indicates whether or not the existing
vocabulary domain can be
extended with additional values. There are two possible
values: CNE (coded, no extension) and CWE (coded with extension).
For more information refer to the
Vocabulary Domain Qualifiers section of the Version 3 Guide.
[Source:
Core Glossary]
2.200 Extensible Markup Language
A meta-language that defines a
syntax used to define other
domain
-specific, semantic, structured markup languages. Based on
SGML (Standard Generalized Markup Language), it
consists of a set of rules for defining semantic tags used to
mark up the content of documents. Abbreviated as XML.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.201 FDAFood and Drug Administration in the United States of America
[Source:
Regulated Reporting]
2.202 Field EncounterA patient encounter that takes place both outside a dedicated service delivery location and outside a patient's residence.
Example locations might include an accident site and at a supermarket.
[Source:
Patient Administration]
2.203 Filler OrderAn order created by a fulfiller. This may be in response to a Placer order which it seeks to fulfill or it may be initiated
independently. These may also be in response to a paper order received by the Filler. These are always in the Promise (PRMS)
Mood.
[Source:
Laboratory]
2.204 Findings'The results of an investigation'-Webster
'an observation; a condition discovered'--Dorland
[Source:
Care Provision]
2.205 function point
Any function,
user transaction,
or other
interaction or
event in the
sponsor’s application which, when it occurs, does
or may correspond to an HL7
trigger
event. Used to describe the conformance of an
information system with the HL7 standard.
[Source:
Core Glossary]
2.206 Gene ExpressionGene Expression is the cellular process that starts with the production of messenger RNA (mRNA) by chromosomal DNA in a process
called transcription.
[Source:
Clinical Genomics]
2.207 generalization
An
association between two
classes, referred to as
superclass and
subclass, in which the subclass
is derived from the superclass. The subclass inherits all
properties from the superclass, including
attributes, relationships, and
states, but also adds new ones to extend the
capabilities of the parent class. Essentially, a
specialization from the
point-of-view of the subclass.
For more information refer to the
Relationships section of the Version 3 Guide.
[Source:
Core Glossary]
2.208 generalization hierarchy
All
superclasses and
subclasses with a common
root superclass.
[Source:
Core Glossary]
2.209 GeneticLocusA genetic locus is a position in a genome (or linkage map) of a particular given sequence. The given sequence could be that
of a gene, allele, marker, etc. An example of a locus is 6p21.3 in cytogenetic nomenclature. This locus is for chromosome
6, short arm (p), region 2, band 1, subband 3. This is a specification for a position on a chromosome, not for what is actually
found at that position. Note that the HL7 specs recognize several nomenclatures for specifying a locus.
[Source:
Clinical Genomics]
2.210 GenotypeThe genetic constitution of an organism or cell, as distinct from its expressed features or phenotype. In particular it is
the allelic makeup of an organism with regard to an observed trait. In the HL7 models, the use of the Genotype term (and the
root class - GeneticLocus) encompasses all genomic aspects related to a specific chromosomal or mitochondrial locus, including
DNA sequence variations, gene expression and proteomics.
[Source:
Clinical Genomics]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.211 graphical expression
A visual representation of a
model
that uses graphic symbols to represent
the components of the model and the relationships that exist
between those components.
[Source:
Core Glossary]
2.212 grid view
A complete view of the
message type
definition, which, due to its size, is presented in
a scrollable format.
[Source:
Core Glossary]
2.213 HaplotypeThe particular combination of alleles in a defined region of some chromosome.
[Source:
Clinical Genomics]
2.214 HDFHL7 Development Framework, which documents the process for HL7 standards development
[Source:
Emergency Medical Services]
2.215 Health Record ExtractsPortions of the HL7 Electronic Health Record (EHR) Domain that are copied from the larger EHR for a specific purpose.
--based on health record terminology from Australia's HealthConnect project
[Source:
Care Provision]
2.216 Health Record SummaryA judgment or assessment based on parts of a health record that produces a shortened version of the parts assessed.
-based on a definition from Australia's HealthConnect project
[Source:
Care Provision]
2.217 Hierarchical Message Description
A
specification of the exact
fields of a
message and their
grouping, sequence, optionality, and
cardinality. This specification contains
message types for one or more
interactions, or that represent one or
more
common message
element types. This is the primary normative
structure for HL7 messages.
[Source:
Core Glossary]
2.218 HITSPHealth Information Technology Standards Panel (www.hitsp.org)
[Source:
Emergency Medical Services]
2.219 HL7Health Level Seven, an ANSI-recognized standards development organization in the healthcare interoperability space (www.hl7.org)
[Source:
Emergency Medical Services]
2.220
HL7
Health Level 7
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.221 HLAHuman Leukocyte Antigens (HLA): Molecule found on cells in the body that characterize each person as unique. These antigens
are inherited from your parents. In donor-recipient matching, HLA determines whether someone will accept an organ from a donor.
[Source:
Clinical Genomics]
2.222 HMD
See
Hierarchical Message Description.
[Source:
Core Glossary]
2.223 Home Health EncounterA patient encounter where services are provided or supervised by a practitioner at the patient's residence. Services may
include recurring visits for chronic or terminal conditions or visit(s) facilitating recuperation.
[Source:
Patient Administration]
2.224 HTMLHypertext Markup Language, a specification of the
W3C that provides markup of documents for display in a web browser
[Source:
Core Glossary]
2.225 ICD(9 or 10)International Classification of Diseases(version 9 or 10) is a terminology published by the National Center for Health Statistics
which is a branch of the CDC.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.226 ICSRIndividual Case Safety Report
[Source:
Regulated Reporting]
2.227 identified CMETA CMET variant that is a proper subset of universal and is intended to provide sufficient information to identify the object(s)
modeled by the CMET. This variant is only suitable for use within TIGHTLY COUPLED SYSTEMS ONLY. This variant provides ONLY
the ID (and code where applicable) and Name. Other variants may not be substituted at runtime.
[Source:
Common Model Element Types]
2.228 identified-confirmable CMETA CMET variant that extends the identified variant by adding just sufficient additional information to allow the identity
of object modeled to be confirmed by a number of corroborating items of data; for instance a patient's date of birth and
current address.
[Source:
Common Model Element Types]
2.229 identified-informational CMETA CMET variant that contains the same attributes and associations present in the confirmable CMET (or the identified/confirmable
if the confirmable does not exist), however the informational variant of dependant CMETs is used, which relaxes the constraints
on dependant CMETs. This allows more flexible use of the CMET.
[Source:
Common Model Element Types]
2.230 identifier attribute
An
attribute used to identify an
instance of a
class.
For more information refer to the
Attributes section of the Version 3 Guide.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.231 IHE PCCIntegrating the Healthcare Enterprise (www.ihe.net) Patient Care Coordination domain
[Source:
Emergency Medical Services]
2.232 IHTSDOThe International Health Terminology Standards Development Organisation. An international organisation established as an association
under Danish Law. It has responsibility for the ongoing maintenance, development, quality assurance, and distribution of SNOMED
CT
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.233 ImmunizationThe record of the event of receiving an immunization. Sometimes referred to as a shot or a dose of vaccine.
[Source:
Immunization]
2.234 Immunization historyThe collection of immunizations received by the client/patient.
[Source:
Immunization]
2.235 Immunization scheduleA schedule is the collection of schedule series. In most cases, a schedule is published and supported by health jurisdictions
or groups, such as the ACIP in the US.
[Source:
Immunization]
2.236 Immunization StatusImmunization Status describes a person's progress towards meeting the goals for a particular vaccine.
[Source:
Immunization]
2.237 implementation technology
A technology selected for use in encoding and sending HL7
messages. For example,
XML is being
used as an implementation technology for Version 3.
[Source:
Core Glossary]
2.238 Implementation Technology Specification
A
specification that describes
how HL7
messages are sent using a
specific
implementation technology
. It includes, but is not
limited to, specifications of the method of encoding the messages,
rules for the establishment of
connections
and transmission timing and procedures for dealing
with errors.
For more information refer to the
Implementation Technology Specifications section
of the Version 3 Guide.
[Source:
Core Glossary]
2.239 inclusion
The
specification in the
Hierarchical
Message Description indicating whether an element of a
message type MAY be null in some
message instances. Contrast
this with conformance.
[Source:
Core Glossary]
2.240 IndividualAlleleOne of the different forms of a gene is called an Allele. In humans one allele comes from the paternal chromosome and another
from the maternal chromosome. Different alleles bring about variation in inherited characteristics. By Individual we mean
that it is possible to represent the actual sequence of an individual which might contain SNPs that are not part of the allele
definition.
[Source:
Clinical Genomics]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.241 information modela class model in object oriented programming
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.242 information model
A structured
specification,
expressed graphically and/or narratively, of the information
requirements of a
domain. An
information model describes the
classes
of information required and the
properties of those
classes, including
attributes,
relationships, and
states.
Examples in HL7 are the
Domain Reference Information Model,Reference Information Model,
and
Refined Message Information
Model.
For more information refer to the
Information Model
section of the Version 3 Guide.
[Source:
Core Glossary]
2.243 informational CMETA CMET variant that includes approximately the same attributes and associations present in the identified/confirmable CMET,
however the entry class id is required, not mandatory. This allows more flexible use of the CMET.
[Source:
Common Model Element Types]
2.244 inheritance
In a
generalization relationship,
the
subclass inherits all
properties from the
superclass,
including
attributes,
relationships, and
states,
unless otherwise specified.
[Source:
Core Glossary]
2.245 Inpatient EncounterA patient encounter where a patient is admitted by a hospital or equivalent facility, assigned to a location where patients
generally stay at least overnight and provided with room, board, and continuous nursing service.
[Source:
Patient Administration]
2.246 instance
A case or an occurrence. For example, an instance of a
class is an
object.
[Source:
Core Glossary]
2.247 instancesin object oriented programming an instance is a real member of an abstract class
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.248 interaction
A single, one-way information flow that supports a communication
requirement expressed in a
scenario.
[Source:
Core Glossary]
2.249 interaction diagram
A graphical representation of communications between
application roles. An
interaction diagram may also be referred to as a ladder diagram,
sequence diagram, or storyboard interaction diagram.
[Source:
Core Glossary]
2.250 interaction list
A list of the
interactions that
appear in an
interaction diagram.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.251 interaction model
A
specification of the
responsibilities of
message senders
and receivers.
[Source:
Core Glossary]
2.252 interaction narrative
A narrative description of each
interaction
contained in an
interaction list
.
[Source:
Core Glossary]
2.253 internal data type
An HL7
data type defined to
support the definition of other data
types, but which may not be assigned as the type for a data
field itself.
[Source:
Core Glossary]
2.254 interoperabilityIn this context, interoperability refers to the ability of two or more computer systems to exchange information.
- Main Entry: in·ter·op·er·a·bil·i·ty
- Function: noun
- Date: 1977
- ability of a system (as a weapons system) to use the parts or equipment of another system
- Source: Merriam-Webster web site
- interoperability
- ability of two or more systems or components to exchange information and to use the information that has been exchanged.
- Source: IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries, IEEE, 1990
“Functional” interoperability is the capability to reliably exchange information without error
“Semantic" interoperability is the ability to interpret, and, therefore, to make effective use of the information so exchanged.
In our context, "effective use" means that the information can be used in any type of computable algorithm (appropriate) to
that information
[Source:
Core Glossary]
2.255 IS04The HITSP specification for Emergency Responder - Electronic Health Record Interoperability
[Source:
Emergency Medical Services]
2.256 IsolateA micro-organism on which observations are made. This may be obtained from a specimen submitted for analysis or it may be
submitted in its own right. It may be scoped by the original specimen. An isolate is a type of specimen in which, the player
is a culture of a type micro organism that has been isolated from other micro organisms and/or its source matrix. The scoping
entity is the original specimen or culture.
[Source:
Laboratory]
2.257 ITS
See
Implementation Technology Specification.
[Source:
Core Glossary]
2.258 joint state
A summarization of multiple partial
states
in a
state machine.
[Source:
Core Glossary]
2.259 JurisdictionThe authority to license agencies and professionals to provide EMS services in a geographic area
[Source:
Emergency Medical Services]
2.260 ladder diagram
See
interaction
diagram.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.261 LicenseA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the License. The difference between a License and
a Certificate is found in the amount of legal/regulatory context surrounding the issuing organization, a License typically
being issued by known regulatory agencies (e.g. State government), a Certificate being issued by a non-regulatory institution
(e.g. school, continuing education center, etc.)
[Source:
Personnel Management]
2.262 LicenseA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the License. The difference between a License and
a Certificate is found in the amount of legal/regulatory context surrounding the issuing organization, a License typically
being issued by known regulatory agencies (e.g. State government), a Certificate being issued by a non-regulatory institution
(e.g. school, continuing education center, etc.)
[Source:
Personnel Management]
2.263 LicenseA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the License. The difference between a License and
a Certificate is found in the amount of legal/regulatory context surrounding the issuing organization, a License typically
being issued by known regulatory agencies (e.g. State government), a Certificate being issued by a non-regulatory institution
(e.g. school, continuing education center, etc.)
[Source:
Personnel Management]
2.264 LicenseA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the License. The difference between a License and
a Certificate is found in the amount of legal/regulatory context surrounding the issuing organization, a License typically
being issued by known regulatory agencies (e.g. State government), a Certificate being issued by a non-regulatory institution
(e.g. school, continuing education center, etc.)
[Source:
Personnel Management]
2.265 LicenseFormal permission granted to an EMS professional in a jurisdiction by an authority to provide EMS services
[Source:
Emergency Medical Services]
2.266 LicenseA subtype of Credential that documents that an instance of a Party (Person or Organization) has satisfied a set of criteria
(skills, knowledge, etc.) defined by the Organization or Person issuing the License. The difference between a License and
a Certificate is found in the amount of legal/regulatory context surrounding the issuing organization, a License typically
being issued by known regulatory agencies (e.g. State government), a Certificate being issued by a non-regulatory institution
(e.g. school, continuing education center, etc.)
[Source:
Personnel Management]
2.267 life cycle
See
state machine.
[Source:
Core Glossary]
2.268 LIFO
Last in-first out. See
push-down stack.
[Source:
Core Glossary]
2.269 list
A form of
collection whose
members are ordered, and need not be unique.
[Source:
Core Glossary]
2.270 literary expression
A representation of a
model in
text. The literary expression seeks to
balance the need for a rigorous, unambiguous description
of the model with the need for a rendition that can be easily read and
interpreted by individuals who understand the general concepts
underlying object-oriented models, but who may not be schooled in
formal model definition languages.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.271 Living SubjectThe abstract super-class (parent class) of Person and Animal
[Source:
Personnel Management]
2.272 Living SubjectThe abstract super-class (parent class) of Person and Animal
[Source:
Personnel Management]
2.273 Living SubjectThe abstract super-class (parent class) of Person and Animal
[Source:
Personnel Management]
2.274 Living SubjectThe abstract super-class (parent class) of Person and Animal
[Source:
Personnel Management]
2.275 Living SubjectThe abstract super-class (parent class) of Person and Animal
[Source:
Personnel Management]
2.276 LocusMatchingLocus is a position in a chromosome of a particular gene or allele. LocusMatching is the similarity in the locus between the
donor and recipient.
[Source:
Clinical Genomics]
2.277 LOINCLogical Observation Identifiers Names and Codes is terminology with a focus on clinical and laboratory observtions maintained
by The Regenstrief Institute (www.regenstrief.org)
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.278 LOINCLogical Observations, Identifiers, Names, and Codes
[Source:
Core Glossary]
2.279 loosely coupled
Loosely coupled
application roles
do not assume that common information about the subject
classes participating in a
message is available to system
components outside of the specific message.
[Source:
Core Glossary]
2.280 mandatory
If an
attribute is
designated as mandatory, all
message
elements which make use of this
attribute SHALL contain a non-null value or they SHALL have a default
that is not null. This requirement is indicated in the "mandatory" column in
the
Hierarchical Message Description.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.281 mandatory association
An
association with a
multiplicity minimum greater
than zero on one end. A fully mandatory association is one with
a multiplicity minimum greater than zero on both ends.
[Source:
Core Glossary]
2.282 markupComputer-processable annotations within a document. Markup encodes a description of a document’s storage layout and logical
structure. In the context of HL7 Version 3, markup syntax is according to the
XML Recommendation.
[Source:
Core Glossary]
2.283 Master Files
Common lookup tables used by one or more application systems.
[Source:
Core Glossary]
2.284 MAYThe conformance verb MAY is used to indicate a possibility. See the
conformance verb definition for more information.
[Source:
Core Glossary]
2.285 MDF
See
Message
Development Framework.
[Source:
Core Glossary]
2.286 Median Beat AnnotationsJust like annotations on the rhythm data, annotations can be made on the median beat. Fudicial markings related to the measurements
specified by the trial protocol can be made globally (on all leads) or locally (on some leads). Episode annotations (such
as arrhythmias, ST elevation episodes, etc.) would not be made on the median beat (for obvious reasons). Refer to examples
from rhythm waveforms annotations.
[Source:
Regulated Studies]
2.287 Median Beat WaveformsComputer algorithms can derive a representative beat from a series of beats having the same morphology (same focus, etc.).
Sometimes a trial protocol will specify the usage of a "median beat" for taking measurements. If a median beat is used, and
the rhythm data from which it is derived is wanted by the FDA, the median beat is related to the rhythm waveforms via an analysis
region. The median is typically composed of as many leads as the rhythm waveforms from which it was derived. The relative
time represents time within the representative cycle, not time relative to the beginning of the rhythm waveforms.
[Source:
Regulated Studies]
2.288 message
A package of information communicated from one application to another. See
also
message type and
message instance.
[Source:
Core Glossary]
2.289 Message Development Framework
The collection of
models,
methods, and tools that comprise the
methodology for specifying
HL7 Version 3 messages. This
framework is used by the developers of the HL7 standards.
[Source:
Core Glossary]
2.290 message element
A unit of structure within a
message type.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.291 message element type
A portion of a
message type
that describes one of the elements of the
message.
[Source:
Core Glossary]
2.292 message instance
A
message, populated with data
values, and formatted for a specific
transmission based on a particular
message type.
[Source:
Core Glossary]
2.293 message payload
Data carried in a
message.
[Source:
Core Glossary]
2.294 message type
A set of rules for constructing a
message
given a specific set of instance data. As such, it
also serves as a guide for parsing
a message to recover the instance data.
[Source:
Core Glossary]
2.295 meta-model
A
model used to specify other models. For
example, the meta-model for a relational database system might specify
elements of type ‘Table’, ‘Record’, and
‘Field.’.
[Source:
Core Glossary]
2.296 methodology
Methods or rules followed in a particular discipline.
[Source:
Core Glossary]
2.297 MIMEMultipurpose Internet Mail Extensions (MIME,
RFC 2046)
[Source:
Core Glossary]
2.298 minimal CMET
minimal CMETA CMET variant that provides more than identified, but not as much as universal. There are not expected to be many of these.
[Source:
Common Model Element Types]
2.299 model
A representation of a
domain that
uses abstraction to express the relevant concepts. In HL7, the
model consists of a collection of
schema
and other documentation.
[Source:
Core Glossary]
2.300 model of meaningthe universal sematic representation of an expression, distinguised from the “model of use” which may have local interpretations
or context, for example an application my place some clincial statements in a “Negative” column meaning “ruled out”. Those
statements would have to be modified (transformed into a cannonical form) to be correctly understood when transmitted to a
third party.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.301 Model of use the “model of use” may have local interpretations or context, for example an application my place some clincial statements
in a “Negative” column meaning “ruled out”. Those statements would have to be transformed into a cannonical form to be correctly
understood when transmitted to a third party. Distinguished from the “model of meaning” which stand on its own, which can
be universally understood.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.302 Mood'Mood' is 'A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command,
possibility, etc.' - HL7 RIM Definition
When combined with the Act Care Provision and a Performer, the Mood of the Act distinguishes whether the performer actually
has (or had) Responsibility for Care, whether the performer is requested to take on responsibility, or whether the performer
is promising to take on responsibility for care.
Mood for other Acts in the DMIM may take on the myriad of moods that are described in the HL7 RIM documentation under values
for "moodCode."
[Source:
Care Provision]
2.303 moodCodeThe HL7 Act.moodCode is defined as “a code distinguishing whether an Act is conceived of as a factual statement or in some
other manner as a command, possibility, goal, etc”.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.304 multiplicity
-
1. In the information model,
multiplicity is a specification
of the minimum and maximum number of objects
from each class that
can participate in an association.
Multiplicity is specified for each end of the association.
-
2. In the
Hierarchical Message Description (HMD), multiplicity
depicts the minimum and maximum number of occurrences of a
message element
expression in a collection.
[Source:
Core Glossary]
2.305 MutationHeritable change in the DNA sequence. A mutation - or alteration - in a particular gene-DNA often results in a certain disease.
[Source:
Clinical Genomics]
2.306 NamespaceA qualifier added to an XML tag to ensure uniqueness among XML elements.
[Source:
XML Implementation Technology Specification, Release 2]
2.307 navigability
Direction in which an
association
can be navigated (either one way or both ways).
[Source:
Core Glossary]
2.308 negationIndAct.negationInd is defined by HL7 as “An indicator specifying that the Act statement is a negation of the Act as described
by the descriptive attributes”.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.309 NEMSISNational Emergency Medical Services Information System (www.nemsis.org)
[Source:
Emergency Medical Services]
2.310 NEMSIS TACNEMSIS Technical Assistance Center, an organization funded and chartered by the US government to support EMS agencies using
the NEMSIS dataset
[Source:
Emergency Medical Services]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.311 NHSUnited Kingdom’s National Health Service
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.312 NHTSANational Highway Traffic Safety Administration (www.nhtsa.dot.gov)
[Source:
Emergency Medical Services]
2.313 Non-Time-based Criterion
[Source:
Personnel Management]
2.314 Non-Time-based Criterion
[Source:
Personnel Management]
2.315 Non-Time-based Criterion
[Source:
Personnel Management]
2.316 Non-Time-based Criterion
[Source:
Personnel Management]
2.317 Non-Time-based Criterion
[Source:
Personnel Management]
2.318 normal formsee cannonical form: the standard or basic structure of a post coordinated expression (set of linked concepts)
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.319 not permitted
One of the allowed values in
conformance requirements. Abbreviated as NP, it
means that the
message element
is never sent for that
message type.
[Source:
Core Glossary]
2.320 NotificationThe process of bringing an emergent medical problem to the attention of an EMS dispatcher
[Source:
Emergency Medical Services]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.321 NPSANational Patient Safety Agency (UK)
[Source:
Regulated Reporting]
2.322 null
A value for a data element which indicates the absence of data. A number
of “flavors” of null are possible and are enumerated in the
domain NullFlavor.
[Source:
Core Glossary]
2.323 object
An
instance of a
class. A part of an information
system containing a collection of related data (in the form of
attributes) and
procedures (methods) for operating on that data.
For more information refer to the
Classes
section of the Version 3 Guide.
[Source:
Core Glossary]
2.324 object identifier
A scheme to provide globally unique identifiers. This object
identifier (OID) scheme is an ISO
standard (ISO 8824:1990), and has been adopted as a CSA standard
(Z243.110).
The HL7 OID Registry is available online.
[Source:
Core Glossary]
2.325 object identity
The feature that the existence of an
object
is independent of any values associated with the object.
[Source:
Core Glossary]
2.326 object-based
Any method, language, or system that supports
object identity,
classification, and encapsulation. An object-based system does
not support
specialization
. Ada is an example of an object-based
implementation language.
[Source:
Core Glossary]
2.327 Observable entity (SCT)Concepts in this hierarchy represent a question about something which may be observed or measure. An observable entity combined
with a result, constitutes a finding.
For instance, the concept Left ventricular end-diastolic pressure (observable entity) in effect represent the question “What
is the value of the left ventricular end diastolic pressure?”
When Left ventricular end-diastolic pressure (observable entity) is given a value it represents a finding.
For example:
Increased left ventricular end-diastolic pressure is a finding with the value Increased.
Left ventricular end-diastolic pressure combined with a separately expressed value such as 95 mmHg also behaves as a finding.
Note: This definition includes concepts that would be used to represent the code attribute of HL7 Observations.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.328 ObservationAn Act of recognizing and noting information about the subject, and whose immediate and primary outcome (post-condition) is
new data about a subject. Observations often involve measurement or other elaborate methods of investigation, but may also
be simply assertive statements.
Discussion: Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name
and the Observation.value is the value of the property. Such a construct is also known as a “variable” (a named feature that
can assume a value); hence, the Observation class is always used to hold generic name-value-pairs or variables, even though
the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or
it may be an assertion or setting of a parameter.
As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes
a description of what was actually observed (“results” or “answers”); and those “results” or “answers” are part of the observation
and not split off into other objects.
Note: This definition refers to the action rather than the outcome of the observation but in the discussion continues to refer
to the “results” or “answers” as being a part of the observation. The general idea of an HL7 Observation therefore includes
three distinct types of concept from a SNOMED CT perspection “Observable entities” (things that can be measured), “Measurement
procedures” (a type of procedure used to make a measurement or observation) and “Clinical finding” (expressing both the name
of the observation and its value).
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.329 Observations
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.330 obsolescent message type
A
message type that has been
marked for deletion in a future version of HL7.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.331 obsolete message type
A
message type, previously
declared obsolescent, that has been removed or replaced in a
particular version of HL7.
[Source:
Core Glossary]
2.332 Occurrence OrderAn single instance of a recurring order. Each instance occurs at a specific point in time.
[Source:
Laboratory]
2.333 OID
See
object identifier.
[Source:
Core Glossary]
2.334 optional
See
inclusion.
[Source:
Core Glossary]
2.335 Order SetSee Profile.
[Source:
Laboratory]
2.336 OrganizationA formalized group of persons with a common purpose (e.g. administrative, legal, political, etc.) and infrastructure necessary
to achieve said purpose.. An Organization is recognized as an entity from the perspective of one or more authorities and/or
other organizations external to the Organization-of-Interest including legal, social, etc. Instances of Organization include:
Joint Commission for Accreditation of Healthcare Organizations, Province of British Columbia, California State Board of Medical
Examiners, etc.
[Source:
Personnel Management]
2.337 OrganizationA formalized group of persons with a common purpose (e.g. administrative, legal, political, etc.) and infrastructure necessary
to achieve said purpose.. An Organization is recognized as an entity from the perspective of one or more authorities and/or
other organizations external to the Organization-of-Interest including legal, social, etc. Instances of Organization include:
Joint Commission for Accreditation of Healthcare Organizations, Province of British Columbia, California State Board of Medical
Examiners, etc.
[Source:
Personnel Management]
2.338 OrganizationA formalized group of persons with a common purpose (e.g. administrative, legal, political, etc.) and infrastructure necessary
to achieve said purpose.. An Organization is recognized as an entity from the perspective of one or more authorities and/or
other organizations external to the Organization-of-Interest including legal, social, etc. Instances of Organization include:
Joint Commission for Accreditation of Healthcare Organizations, Province of British Columbia, California State Board of Medical
Examiners, etc.
[Source:
Personnel Management]
2.339 OrganizationA formalized group of persons with a common purpose (e.g. administrative, legal, political, etc.) and infrastructure necessary
to achieve said purpose.. An Organization is recognized as an entity from the perspective of one or more authorities and/or
other organizations external to the Organization-of-Interest including legal, social, etc. Instances of Organization include:
Joint Commission for Accreditation of Healthcare Organizations, Province of British Columbia, California State Board of Medical
Examiners, etc.
[Source:
Personnel Management]
2.340 OrganizationA formalized group of persons with a common purpose (e.g. administrative, legal, political, etc.) and infrastructure necessary
to achieve said purpose.. An Organization is recognized as an entity from the perspective of one or more authorities and/or
other organizations external to the Organization-of-Interest including legal, social, etc. Instances of Organization include:
Joint Commission for Accreditation of Healthcare Organizations, Province of British Columbia, California State Board of Medical
Examiners, etc.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.341 Organizeran object class in the HL7 Clinical Statement model, which can be an ActContainer, which is a navigational structure or heading
used to group a set of acts sharing a common context, include such structures as folders, documents, document sections, and
batteries. Values may be drawn from the SNOMED CT Care Record Elements hierarchy.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.342 OutcomeThe observation on the subject made following a specific intervention or collection of interventions on the subject or related
subjects - paraphrased from the Nursing Terminology Summit.
[Source:
Care Provision]
2.343 PackageSee Profile.
[Source:
Laboratory]
2.344 partial state
Part of a
state machine. A
state machine MAY have multiple partial
states effective at the same time; the multiple
partial states can be summarized to one
joint state of the state machine.
[Source:
Core Glossary]
2.345 PartyAn abstract class that is the parent class for Organization and Person.
[Source:
Personnel Management]
2.346 PartyAn abstract class that is the parent class for Organization and Person.
[Source:
Personnel Management]
2.347 PartyAn abstract class that is the parent class for Organization and Person.
[Source:
Personnel Management]
2.348 PartyAn abstract class that is the parent class for Organization and Person.
[Source:
Personnel Management]
2.349 PartyAn abstract class that is the parent class for Organization and Person.
[Source:
Personnel Management]
2.350 Patient Care ResponsibilityMost governments describe the accountability a care provider has for a person under care. Although the specifics of this responsibility
vary from jurisdiction to jurisdiction, the concept is general at the international level. In many cases, this accountability
is present even without personal contact between the care provider and the patient or delivery of services, e.g. responsibility
of a public health clinic for a population of patients; an enrollment of a patient in the patient panel of a physician.
[Source:
Care Provision]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.351 Patient EncounterSee term
Encounter instead.
[Source:
Patient Administration]
2.352 Patient SafetyThe multidisciplinary approach used by an organization to reduce the risk and occurrence of harm to patients as a result of
their healthcare.
[Source:
Regulated Reporting]
2.353 Patient Safety IncidentAny unintended, expected or unexpected incident(s) that could have or did lead to harm for one or more patients receiving
health care services. These incidents may include errors of omission or commission.
[Source:
Regulated Reporting]
2.354 Patternsa method or technique for solving a type of problem, an object model that is generally effective for a type of problem and
can be easily adapted to your particular instance of the problem.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.355 PayerA person or organization responsible for paying medical bills
[Source:
Emergency Medical Services]
2.356 Person- A subtype of Living Subject representing single human being who, in the context of the Personnel Management domain, must
also be uniquely identifiable through one or more legal documents (e.g. Driver's License, Birth Certificate, etc.) Instances
of Person include: John Smith, RN, Mary Jones, MD, etc.
[Source:
Personnel Management]
2.357 Person- A subtype of Living Subject representing single human being who, in the context of the Personnel Management domain, must
also be uniquely identifiable through one or more legal documents (e.g. Driver's License, Birth Certificate, etc.) Instances
of Person include: John Smith, RN, Mary Jones, MD, etc.
[Source:
Personnel Management]
2.358 Person- A subtype of Living Subject representing single human being who, in the context of the Personnel Management domain, must
also be uniquely identifiable through one or more legal documents (e.g. Driver's License, Birth Certificate, etc.) Instances
of Person include: John Smith, RN, Mary Jones, MD, etc.
[Source:
Personnel Management]
2.359 Person- A subtype of Living Subject representing single human being who, in the context of the Personnel Management domain, must
also be uniquely identifiable through one or more legal documents (e.g. Driver's License, Birth Certificate, etc.) Instances
of Person include: John Smith, RN, Mary Jones, MD, etc.
[Source:
Personnel Management]
2.360 Person- A subtype of Living Subject representing single human being who, in the context of the Personnel Management domain, must
also be uniquely identifiable through one or more legal documents (e.g. Driver's License, Birth Certificate, etc.) Instances
of Person include: John Smith, RN, Mary Jones, MD, etc.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.361 Pertinent InformationAn HL7 Act Relationship that asserts a 'very unspecific relationship from one item of clinical information to another. It
does not judge about the role the pertinent information plays.' - HL7 RIM definition
[Source:
Care Provision]
2.362 Placer OrderAn order placed and maintained by a Placer system. Its status can only be changed by the placer. This must be in Request (RQO)
mood
[Source:
Laboratory]
2.363 PMHPast Medical History
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.364 PolypeptideA peptide is composed of a chain that may be considered as derived from linking amino acids by forming peptide bonds. Polypeptides
are long stretches of such peptide chains. A protein is made up of a polypeptide chain plus other chemical groups.
[Source:
Clinical Genomics]
2.365 PositionWithin the context of an instance of an Organization, a Position is a named collection of various duties, Responsibilities,
and/or Privileges. A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be
created/defined in terms of the Qualifications (including various forms of Credentials that a Person much have to qualify
for an Assignment to that Position). A Position is considered a subtype of Role because of the common domain perspective
that a 'base' or 'functional' role (e.g. Staff Physician) is often necessary before the (e.g. person) in a given 'base/functional'
role can be assigned to other roles (e.g. Chair of Department of Cardiology, Director of ICU, etc.). The collection of duties,
responsibilities, and/or privileges associated with a given Position is, at minimum, contained in a Description associated
with the Position. The presence of a Description implies that the Position may exist ('be defined') irrespective of whether
an instance of a Party in a Role has been assigned to the position.
[Source:
Personnel Management]
2.366 PositionWithin the context of an instance of an Organization, a Position is a named collection of various duties, Responsibilities,
and/or Privileges. A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be
created/defined in terms of the Qualifications (including various forms of Credentials that a Person much have to qualify
for an Assignment to that Position). A Position is considered a subtype of Role because of the common domain perspective
that a 'base' or 'functional' role (e.g. Staff Physician) is often necessary before the (e.g. person) in a given 'base/functional'
role can be assigned to other roles (e.g. Chair of Department of Cardiology, Director of ICU, etc.). The collection of duties,
responsibilities, and/or privileges associated with a given Position is, at minimum, contained in a Description associated
with the Position. The presence of a Description implies that the Position may exist ('be defined') irrespective of whether
an instance of a Party in a Role has been assigned to the position.
[Source:
Personnel Management]
2.367 PositionWithin the context of an instance of an Organization, a Position is a named collection of various duties, Responsibilities,
and/or Privileges. A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be
created/defined in terms of the Qualifications (including various forms of Credentials that a Person much have to qualify
for an Assignment to that Position). A Position is considered a subtype of Role because of the common domain perspective
that a 'base' or 'functional' role (e.g. Staff Physician) is often necessary before the (e.g. person) in a given 'base/functional'
role can be assigned to other roles (e.g. Chair of Department of Cardiology, Director of ICU, etc.). The collection of duties,
responsibilities, and/or privileges associated with a given Position is, at minimum, contained in a Description associated
with the Position. The presence of a Description implies that the Position may exist ('be defined') irrespective of whether
an instance of a Party in a Role has been assigned to the position.
[Source:
Personnel Management]
2.368 PositionWithin the context of an instance of an Organization, a Position is a named collection of various duties, Responsibilities,
and/or Privileges. A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be
created/defined in terms of the Qualifications (including various forms of Credentials that a Person much have to qualify
for an Assignment to that Position). A Position is considered a subtype of Role because of the common domain perspective
that a 'base' or 'functional' role (e.g. Staff Physician) is often necessary before the (e.g. person) in a given 'base/functional'
role can be assigned to other roles (e.g. Chair of Department of Cardiology, Director of ICU, etc.). The collection of duties,
responsibilities, and/or privileges associated with a given Position is, at minimum, contained in a Description associated
with the Position. The presence of a Description implies that the Position may exist ('be defined') irrespective of whether
an instance of a Party in a Role has been assigned to the position.
[Source:
Personnel Management]
2.369 PositionWithin the context of an instance of an Organization, a Position is a named collection of various duties, Responsibilities,
and/or Privileges. A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be
created/defined in terms of the Qualifications (including various forms of Credentials that a Person much have to qualify
for an Assignment to that Position). A Position is considered a subtype of Role because of the common domain perspective
that a 'base' or 'functional' role (e.g. Staff Physician) is often necessary before the (e.g. person) in a given 'base/functional'
role can be assigned to other roles (e.g. Chair of Department of Cardiology, Director of ICU, etc.). The collection of duties,
responsibilities, and/or privileges associated with a given Position is, at minimum, contained in a Description associated
with the Position. The presence of a Description implies that the Position may exist ('be defined') irrespective of whether
an instance of a Party in a Role has been assigned to the position.
[Source:
Personnel Management]
2.370 post-coordinationthe linking of concepts or terms to refine or qualify, to represent more precise meanings.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.371 Postcoordination (HL7)Representation of the meaning of a class by a combination of different attributes.
(could be single attribute within CD datatype / single class / multi class)
Note: This definition is not stated in HL7 documents but is inferred from usage in relation to particular attributes like
Procedure.methodCode and Procedure.targetSiteCode.
Contrast this with the definition of post-coordination in SNOMED CT documentation which refers to a collection of concept
identifiers which may be applied to a single HL7 attribute.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.372 Postcoordination (SCT)Representation of a clinical idea using a combination of two or more concept identifiers.
A combination of concept identifiers used to represent a single clinical idea is referred to as a post-coordinated expression
(see expression). Many clinical ideas can also be represented using a single SNOMED CT concept identifier (see pre-coordination).
Some clinical ideas may be represented in several different ways. SNOMED CT technical specifications include guidance of logical
transformations that reduce equivalent expressions to a common canonical form.
Example: SNOMED CT includes the following concepts:
Fracture of bone (conceptId= 125605004)
Finding site (conceptId= 363698007)
Bone structure of femur (conceptId= 181255000)
SNOMED CT also includes a pre-coordinated concept for this procedure
Fracture of femur (conceptId= 71620000)
It is possible to represent “fracture of femur” in different ways:
71620000 (pre-coordinated expression)
125605004 : 363698007 = 181255000 (post-coordinated expression).
Note: In an HL7 representation a SNOMED CT expression is represented in a single HL7 attribute using the HL7 CD (Concept Descriptor)
data type.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.373 Pre-coordinationcreation of a new Concept in a terminiology, often a post-coordinated expression that links or qualifies several concepts.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.374 Precoordination (HL7) Representation of the meaning of a class by a single attribute.
(as in SCT but also could cover single attribute post-coordination)
Note: This definition is not stated in HL7 documents but is inferred from usage in relation to particular attributes
like Procedure.methodCode and Procedure.targetSiteCode.
Contrast this with the definition of pre-coordination in SNOMED CT documentation which implies a single concept identifier
is used to represent a meaning.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.375 Precoordination (SCT) Representation of a clinical idea using a single concept identifier.
A single concept identifier used to represent a specific meaning is referred to as a pre-coordinated expression (see expression).
SNOMED CT also allows the use of post-coordinated expressions (see post-coordination) to represent a meaning using a combination
of two or more concept identifiers.
However, including commonly used concepts in a pre-coordinated form makes the terminology easier to use.
For examples see post-coordination.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.376 predicate reference
In the
Hierarchical Message Description,
a
message element
that is referred to in the predicate defining the conditional
presence of another message element.
[Source:
Core Glossary]
2.377 Preliminary ReportA preliminary report contains completed results that are valid for a point in time with the information currently available.
This report is not expected to be revised but may be replaced with a subsequent preliminary report or a final report.. The
order remains active until a final report has been issued that sets the order and its components to 'completed'. For example,
a preliminary report for a blood culture reads 'no growth after 24 hours'; the order status remains active. The final report
of 'no growth after 7 days' is subsequently issued and the order status is set to 'completed'.
[Source:
Laboratory]
2.378 primitive data type
A
data type that is defined as a
single entity, and whose full semantic is contained in its definition.
[Source:
Core Glossary]
2.379 primitive message element type
A
message element type
that contains a single datum, with no subordinate
components. Examples include String and Number.
[Source:
Core Glossary]
2.380 PrivilegeA subtype of Responsibility that is differentiated from Responsibility by virtue of the fact that it is associated with specific
Credentials rather than simply Qualifications. Although Privileges may be associated with a Position (e.g. the Position of
Attending Physician may be associated with Admitting Privileges), a Person in a Role may, in addition, apply for other Privileges.
Each application involves at least one other Party who must review the Person-in-a-Role's specific Credentials required in
order for the Privilege to be granted. Requirements may be defined by the Granting Party and/or by external organizations.
NOTE: A Privilege differs from a Responsibility in that the association/assignment of a Privilege to a Person-in-a-Role requires
the interaction of at least two instances of Party, i.e. the Person-in-a-Role (who may or may not be in a Position) requesting
the Privilege and the Person/Organization-in-a-Role granting the Privilege. In the sense that it requires a 2-Party interaction,'
the concept Privilege is therefore similar to Credential.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.381 PrivilegeA subtype of Responsibility that is differentiated from Responsibility by virtue of the fact that it is associated with specific
Credentials rather than simply Qualifications. Although Privileges may be associated with a Position (e.g. the Position of
Attending Physician may be associated with Admitting Privileges), a Person in a Role may, in addition, apply for other Privileges.
Each application involves at least one other Party who must review the Person-in-a-Role's specific Credentials required in
order for the Privilege to be granted. Requirements may be defined by the Granting Party and/or by external organizations.
NOTE: A Privilege differs from a Responsibility in that the association/assignment of a Privilege to a Person-in-a-Role requires
the interaction of at least two instances of Party, i.e. the Person-in-a-Role (who may or may not be in a Position) requesting
the Privilege and the Person/Organization-in-a-Role granting the Privilege. In the sense that it requires a 2-Party interaction,'
the concept Privilege is therefore similar to Credential.
[Source:
Personnel Management]
2.382 PrivilegeA subtype of Responsibility that is differentiated from Responsibility by virtue of the fact that it is associated with specific
Credentials rather than simply Qualifications. Although Privileges may be associated with a Position (e.g. the Position of
Attending Physician may be associated with Admitting Privileges), a Person in a Role may, in addition, apply for other Privileges.
Each application involves at least one other Party who must review the Person-in-a-Role's specific Credentials required in
order for the Privilege to be granted. Requirements may be defined by the Granting Party and/or by external organizations.
NOTE: A Privilege differs from a Responsibility in that the association/assignment of a Privilege to a Person-in-a-Role requires
the interaction of at least two instances of Party, i.e. the Person-in-a-Role (who may or may not be in a Position) requesting
the Privilege and the Person/Organization-in-a-Role granting the Privilege. In the sense that it requires a 2-Party interaction,'
the concept Privilege is therefore similar to Credential.
[Source:
Personnel Management]
2.383 PrivilegeA subtype of Responsibility that is differentiated from Responsibility by virtue of the fact that it is associated with specific
Credentials rather than simply Qualifications. Although Privileges may be associated with a Position (e.g. the Position of
Attending Physician may be associated with Admitting Privileges), a Person in a Role may, in addition, apply for other Privileges.
Each application involves at least one other Party who must review the Person-in-a-Role's specific Credentials required in
order for the Privilege to be granted. Requirements may be defined by the Granting Party and/or by external organizations.
NOTE: A Privilege differs from a Responsibility in that the association/assignment of a Privilege to a Person-in-a-Role requires
the interaction of at least two instances of Party, i.e. the Person-in-a-Role (who may or may not be in a Position) requesting
the Privilege and the Person/Organization-in-a-Role granting the Privilege. In the sense that it requires a 2-Party interaction,'
the concept Privilege is therefore similar to Credential.
[Source:
Personnel Management]
2.384 PrivilegeA subtype of Responsibility that is differentiated from Responsibility by virtue of the fact that it is associated with specific
Credentials rather than simply Qualifications. Although Privileges may be associated with a Position (e.g. the Position of
Attending Physician may be associated with Admitting Privileges), a Person in a Role may, in addition, apply for other Privileges.
Each application involves at least one other Party who must review the Person-in-a-Role's specific Credentials required in
order for the Privilege to be granted. Requirements may be defined by the Granting Party and/or by external organizations.
NOTE: A Privilege differs from a Responsibility in that the association/assignment of a Privilege to a Person-in-a-Role requires
the interaction of at least two instances of Party, i.e. the Person-in-a-Role (who may or may not be in a Position) requesting
the Privilege and the Person/Organization-in-a-Role granting the Privilege. In the sense that it requires a 2-Party interaction,'
the concept Privilege is therefore similar to Credential.
[Source:
Personnel Management]
2.385 ProbandFirst affected family member coming to medlcal attention.
[Source:
Clinical Genomics]
2.386 Problema clinical statement that a clinician chooses to add to a problem list.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.387 Procedure (HL7)An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.
Discussion: Applied to clinical medicine, procedure is but one among several types of clinical activities such as observation,
substance-administrations, and communicative interactions (e.g. teaching, advice, psychotherapy, represented simply as Acts
without special attributes). Procedure does not subsume those other activities nor is procedure subsumed by them. Notably
Procedure does not comprise all acts of whose intent is intervention or treatment. Whether the bodily alteration is appreciated
or intended as beneficial to the subject is likewise irrelevant, what counts is that the act is essentially an alteration
of the physical condition of the subject.
Note: This definition and the associated discussion exclude many activities which are subsumed by the more general sense of
the word “procedure” which is used in the SNOMED CT definition.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.388 Procedure (SCT) Concepts that represent the purposeful activities performed in the provision of health care. This hierarchy includes a broad
variety of activities, including but not limited to invasive procedures (Excision of intracranial artery), administration
of medicines (Pertussis vaccination), imaging procedures (Radiography of chest), education procedures (Instruction in use
of inhaler), and administrative procedures (Medical records transfer).
Note: As expected, this definition includes concepts that would be used to represent HL7 Procedures. However, it also includes
measurement procedures and actions that involve administration of a substance. Therefore, the code attribute of many HL7 Observations
and SubstanceAdministration Acts may also be expressed using concepts from the SNOMED procedures hierarchy.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.389 ProfileA group of orderable items requested together as an ordering or billing convenience. These are generally configured on the
requesting application and are expanded into order items before being sent to a fulfiller.
[Source:
Laboratory]
2.390 Promise Mood'Promise' is 'An intent to perform a service that has the strength of a commitment, i.e., other parties may rely on the originator
of such promise that said originator will see to it that the promised act will be fulfilled. A promise can be either solicited
or unsolicited.' - HL7 RIM Definition
When combined with the Act Care Provision and a Performer, the Promise Mood of the Act distinguishes whether the performer
is promising to take on responsibility for care.
[Source:
Care Provision]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.391 property
-
1. Any attribute,
association, method, or
state model defined for a
class or
object.
-
2. In a
Hierarchical Message Description (HMD), the column
that states the name of the class, attribute or
association
role name as it appears in the
Reference
Information Model (RIM).
[Source:
Core Glossary]
2.392 ProtocolA set of medical instructions to be followed under a specified set of circumstances
[Source:
Emergency Medical Services]
2.393 PS:GINPatient Safety: Generic Incident Notification
[Source:
Regulated Reporting]
2.394 PS:RUMPatient Safety: Root causes and Underlying factors Message
[Source:
Regulated Reporting]
2.395 Public Safety DispatcherA person trained and licensed to dispatch EMS units
[Source:
Emergency Medical Services]
2.396 push-down stack
Also known as a “last in-first out” (LIFO)
list, a list
maintained by a Technical Committee as it analyses the
Refined Message Information Model
(RMIM) and builds a
Hierarchical Message Description, in which the last
class added
is always the first class removed. (A metaphoric reference to the spring-loaded
plate carriers used in institutional dining halls, where the new
plates added to the top of the stack push down the earlier plates, so
the newest plate is taken off the stack first).
[Source:
Core Glossary]
2.397 Qualification (Definition and Instatiation)The supertype/parent of Credential. A statement of a specific capability, competency, and/or capacity which may either be
asserted by or required for a Role or Position. An attribute of a Qualification may be whether or not a scoper Party requires
the Qualification for an Initial Application to a Role/Position, as opposed to requiring it for Reapplication to the named
Role or Position. A Qualification is differentiated from a Credential by virtue of the fact that a Credential carries the
requirement of both the assertion and the validation ('vetting') of the capability, competency, and/or capacity, whereas the
Qualification is simply the assertion per se.
[Source:
Personnel Management]
2.398 Qualification (Definition and Instatiation)The supertype/parent of Credential. A statement of a specific capability, competency, and/or capacity which may either be
asserted by or required for a Role or Position. An attribute of a Qualification may be whether or not a scoper Party requires
the Qualification for an Initial Application to a Role/Position, as opposed to requiring it for Reapplication to the named
Role or Position. A Qualification is differentiated from a Credential by virtue of the fact that a Credential carries the
requirement of both the assertion and the validation ('vetting') of the capability, competency, and/or capacity, whereas the
Qualification is simply the assertion per se.
[Source:
Personnel Management]
2.399 Qualification (Definition and Instatiation)The supertype/parent of Credential. A statement of a specific capability, competency, and/or capacity which may either be
asserted by or required for a Role or Position. An attribute of a Qualification may be whether or not a scoper Party requires
the Qualification for an Initial Application to a Role/Position, as opposed to requiring it for Reapplication to the named
Role or Position. A Qualification is differentiated from a Credential by virtue of the fact that a Credential carries the
requirement of both the assertion and the validation ('vetting') of the capability, competency, and/or capacity, whereas the
Qualification is simply the assertion per se.
[Source:
Personnel Management]
2.400 Qualification (Definition and Instatiation)The supertype/parent of Credential. A statement of a specific capability, competency, and/or capacity which may either be
asserted by or required for a Role or Position. An attribute of a Qualification may be whether or not a scoper Party requires
the Qualification for an Initial Application to a Role/Position, as opposed to requiring it for Reapplication to the named
Role or Position. A Qualification is differentiated from a Credential by virtue of the fact that a Credential carries the
requirement of both the assertion and the validation ('vetting') of the capability, competency, and/or capacity, whereas the
Qualification is simply the assertion per se.
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.401 Qualification (Definition and Instatiation)The supertype/parent of Credential. A statement of a specific capability, competency, and/or capacity which may either be
asserted by or required for a Role or Position. An attribute of a Qualification may be whether or not a scoper Party requires
the Qualification for an Initial Application to a Role/Position, as opposed to requiring it for Reapplication to the named
Role or Position. A Qualification is differentiated from a Credential by virtue of the fact that a Credential carries the
requirement of both the assertion and the validation ('vetting') of the capability, competency, and/or capacity, whereas the
Qualification is simply the assertion per se.
[Source:
Personnel Management]
2.402 queryQueries are the primary mechanism for retrieving information from computer systems. Many database management systems use the
Structured Query Language (SQL) standard query format.
[Source:
Core Glossary]
2.403 RCVSee term
Reference Change Value instead.
[Source:
Laboratory]
2.404 Real Time Location SystemA Real Time Location System (RTLS) captures, processes and stores information about the location of tracking tags associated
with resources (patients, providers, equipment) as they move around a healthcare facility.
[Source:
Registries]
2.405 realm
A
vocabulary
domain qualifier used in a
domain specification,
which allows the
vocabulary
domain of a
coded attribute to be
specialized according to the geographical, organizational, or
political environment where the HL7 standard is being used.
For more information refer to the
Vocabulary Domain Qualifiers section of the Version 3 Guide.
[Source:
Core Glossary]
2.406 receiver responsibility
An obligation on an
application
role that receives an
interactionas defined in the
interaction model.
[Source:
Core Glossary]
2.407 RecommendationA recommendation is guidance on when the next dose is due and is based on a standard set of rules. This may consider both
the history of vaccines already received and client conditions.
[Source:
Immunization]
2.408 Recurring OrderAn order for a series of requests to be performed over time.
[Source:
Laboratory]
2.409 recursion
An
association that leads
from a
class directly or indirectly
back to that class.
[Source:
Core Glossary]
2.410 Reference Change ValueThe Reference Change Value (formerly known as critical difference) is derived from the analytical and biological variability
in the measured parameters. It provides an estimate of the significance of change between serial results and provides an
index that will enable interpretation of results by the user or end user systems. Results changes >= to the RCV of 0.99
probability are said to be "highly significant", changes >= RCV at 0.95% probability but <= to the RCV at 0.99 are said
to be "significant".
[Source:
Laboratory]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.411 Reference Information Model
The HL7
information model
from which all other information models
(e.g., RMIMs) and
messages
are derived.
For more information refer to the
Information Model
section of the Version 3 Guide.
[Source:
Core Glossary]
2.412 Refined Message Information Model
An information structure that represents the requirements for a
set of
messages. A
constrained
subset of the
Reference Information Model (RIM) which MAY contain additional
classes that are cloned from
RIM classes. Contains those classes,
attributes,
associations,
and
data types that are needed to
support one or more
Hierarchical Message Descriptions (HMD). A single
message can be shown as a particular pathway through the
classes within an RMIM.
For more information refer to the
Information Model
section of the Version 3 Guide.
[Source:
Core Glossary]
2.413 Region SpecificationThere are 2 basic types of regions: a fully specified region and a partially specified one. The fully specified region is
one where each dimension within the Observation Series to be included in the region has a boundary defined. For example,
if an episode of ST elevation is observed in leads V4 and V5, a fully specified region would contain 3 boundaries: one for
time, one for V4, and one for V5. The boundary in time would be specified with an interval in time (IVL<PQ>). The boundaries
on V4 and V5 would be infinite intervals (the entire range of voltages for both leads are to be included in the region for
ST elevation). A partially specified region assumes all dimensions in the Observation Series are included in the region except
for the boundaries specified. For example, if a global QRS onset is observed, only a boundary for time is required. All
the other dimensions (leads) would be included in the partially specified region.
[Source:
Regulated Studies]
2.414 RelationshipA class used to collect instances of a class as either Source or Target of the intervening Relationship instance
[Source:
Personnel Management]
2.415 RelationshipA class used to collect instances of a class as either Source or Target of the intervening Relationship instance
[Source:
Personnel Management]
2.416 RelationshipA class used to collect instances of a class as either Source or Target of the intervening Relationship instance
[Source:
Personnel Management]
2.417 RelationshipA class used to collect instances of a class as either Source or Target of the intervening Relationship instance
[Source:
Personnel Management]
2.418 RelationshipA class used to collect instances of a class as either Source or Target of the intervening Relationship instance
[Source:
Personnel Management]
2.419 Request Mood'Request' is 'A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service
performer).' - HL7 RIM Definition
When combined with the Act Care Provision and a Performer, the Request Mood of the Act distinguishes whether the performer
is requested to take on responsibility for care.
[Source:
Care Provision]
2.420 required
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.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.421 ReshapingReshaping is the process of creating a specific serialization model from a HL7 static model. The process consists of two parts;
The removal of attributes with fixed values and the flattening of associations.
[Source:
XML Implementation Technology Specification, Release 2]
2.422 ResponsibilityA defined task, associated with a Position. A given Responsibiltiy may be Required (Y/N) A responsibility may be required
or optional. The optionality of a particular Responsibility as part of the definition of a Position may ultimately end up
being Required when a particular Person is Assigned to a Position.
[Source:
Personnel Management]
2.423 ResponsibilityA defined task, associated with a Position. A given Responsibiltiy may be Required (Y/N) A responsibility may be required
or optional. The optionality of a particular Responsibility as part of the definition of a Position may ultimately end up
being Required when a particular Person is Assigned to a Position.
[Source:
Personnel Management]
2.424 ResponsibilityA defined task, associated with a Position. A given Responsibiltiy may be Required (Y/N) A responsibility may be required
or optional. The optionality of a particular Responsibility as part of the definition of a Position may ultimately end up
being Required when a particular Person is Assigned to a Position.
[Source:
Personnel Management]
2.425 ResponsibilityA defined task, associated with a Position. A given Responsibiltiy may be Required (Y/N) A responsibility may be required
or optional. The optionality of a particular Responsibility as part of the definition of a Position may ultimately end up
being Required when a particular Person is Assigned to a Position.
[Source:
Personnel Management]
2.426 ResponsibilityA defined task, associated with a Position. A given Responsibiltiy may be Required (Y/N) A responsibility may be required
or optional. The optionality of a particular Responsibility as part of the definition of a Position may ultimately end up
being Required when a particular Person is Assigned to a Position.
[Source:
Personnel Management]
2.427 responsibility
An action required of the receiver of a
message.
[Source:
Core Glossary]
2.428 ResultA value obtained from an observation and reported against the appropriate Observation Act code. Results are in Event (EVN)
mood
[Source:
Laboratory]
2.429 Result CorrectedA result that replaces a previously reported 'Complete' result.
[Source:
Laboratory]
2.430 Result PartialA partial result refers to a multi-component result when some but not all components have been reported. The order has not
yet been fulfilled and is still active. Each atomic result reported may be 'Active' or 'Completed'.
[Source:
Laboratory]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.431 Result PreliminaryA result that is expected to be replaced with a revised result at a later stage. This result should be treated with a degree
of caution as it is subject to change. For example, a toxicology screen identifies the presence of an unidentified opiate.
This preliminary result is not set to completed and will be updated later with the specific drug and set to complete. A preliminary
result is not the same as a preliminary report. See preliminary report.
[Source:
Laboratory]
2.432 Result RevisedA result that replaces a previously reported result that was not 'Complete'. The Revised result may have a 'Complete' status
or may remain 'Active'
[Source:
Laboratory]
2.433 Rhythm Waveform AnnotationsSome annotations will be specific to areas in time but will apply to all the leads. For example, the presence of an arrhythmia,
or a period of time where the patient was performing some activity that affects the ECG. Pacer spikes and perhaps beat locations
are also indicated as points or areas in time. Fudicial markings made by superimposing all the leads would also fall into
this category. * Rhythm annotation example * Patient activity example * Pacer spikes example * Beat location example * Beat
classification example * Global fudicial markings example Other annotations will be specific to areas in time AND one or more
leads. Annotations falling into this category include fudicial markings for beat measurements made on particular leads, lead-specific
episodes such as ST elevation, etc. * Fudicial markings example * Isoelectric example * ST elevation example
[Source:
Regulated Studies]
2.434 Rhythm WaveformsThese are the waveforms directly collected from the subject and used for clinical trial research. If measurements were taken
from these, annotations should show the fudicial markings for those measurements. The specific set of fudicial markings is
specified by the trial protocol. If the waveforms have been enhanced to facilitate the measurement process, control variables
should indicate what enhancements were made. For example, filtering, etc.
[Source:
Regulated Studies]
2.435 RIM
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.436 RIM
See
Reference
Information Model.
[Source:
Core Glossary]
2.437 RMIM
See
Refined Message Information Model.
[Source:
Core Glossary]
2.438 RMIM diagram
A diagrammatic representation of a
Refined Message Information Model (RMIM). Possible
formats include
UML and the HL7 RMIM graphic format.
[Source:
Core Glossary]
2.439 RoleA named context in which a Party (usually, but not always, a Person) is identified in a context-of-interest. Roles represent
specific semantics involved in the relationship between two (and only two) instances of a Party: one instance of a Party
plays a Role scoped by another instance of a Party. Note that the naming of the Role may be formal or informal within the
organization, but that the identity of the instance of Person (or Organization) playing the Role does not end when the Role
itself ends. In addition, a Role specifies a competency, capability, and/or capacity which the Entity assuming the Role scoper
piece of the relationship implicitly or explicitly acknowledges as being present/possessed by the Entity assuming the Role
player portion of the relationship. In particular, the Personnel Management domain is particularly interested in the various
Roles associated with all aspects of healthcare delivery, as well as the various Acts by which a given Role is defined, identified,
guaranteed, or acknowledged by the scoper Party. (NOTE: The more formal association of a Person in a Role Assigned to a
Position with associated Responsibilities and/or Privileges is explicitly covered elsewhere in the Domain Analysis Model)
[Source:
Personnel Management]
2.440 RoleA named context in which a Party (usually, but not always, a Person) is identified in a context-of-interest. Roles represent
specific semantics involved in the relationship between two (and only two) instances of a Party: one instance of a Party
plays a Role scoped by another instance of a Party. Note that the naming of the Role may be formal or informal within the
organization, but that the identity of the instance of Person (or Organization) playing the Role does not end when the Role
itself ends. In addition, a Role specifies a competency, capability, and/or capacity which the Entity assuming the Role scoper
piece of the relationship implicitly or explicitly acknowledges as being present/possessed by the Entity assuming the Role
player portion of the relationship. In particular, the Personnel Management domain is particularly interested in the various
Roles associated with all aspects of healthcare delivery, as well as the various Acts by which a given Role is defined, identified,
guaranteed, or acknowledged by the scoper Party. (NOTE: The more formal association of a Person in a Role Assigned to a
Position with associated Responsibilities and/or Privileges is explicitly covered elsewhere in the Domain Analysis Model)
[Source:
Personnel Management]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.441 RoleA named context in which a Party (usually, but not always, a Person) is identified in a context-of-interest. Roles represent
specific semantics involved in the relationship between two (and only two) instances of a Party: one instance of a Party
plays a Role scoped by another instance of a Party. Note that the naming of the Role may be formal or informal within the
organization, but that the identity of the instance of Person (or Organization) playing the Role does not end when the Role
itself ends. In addition, a Role specifies a competency, capability, and/or capacity which the Entity assuming the Role scoper
piece of the relationship implicitly or explicitly acknowledges as being present/possessed by the Entity assuming the Role
player portion of the relationship. In particular, the Personnel Management domain is particularly interested in the various
Roles associated with all aspects of healthcare delivery, as well as the various Acts by which a given Role is defined, identified,
guaranteed, or acknowledged by the scoper Party. (NOTE: The more formal association of a Person in a Role Assigned to a
Position with associated Responsibilities and/or Privileges is explicitly covered elsewhere in the Domain Analysis Model)
[Source:
Personnel Management]
2.442 RoleA named context in which a Party (usually, but not always, a Person) is identified in a context-of-interest. Roles represent
specific semantics involved in the relationship between two (and only two) instances of a Party: one instance of a Party
plays a Role scoped by another instance of a Party. Note that the naming of the Role may be formal or informal within the
organization, but that the identity of the instance of Person (or Organization) playing the Role does not end when the Role
itself ends. In addition, a Role specifies a competency, capability, and/or capacity which the Entity assuming the Role scoper
piece of the relationship implicitly or explicitly acknowledges as being present/possessed by the Entity assuming the Role
player portion of the relationship. In particular, the Personnel Management domain is particularly interested in the various
Roles associated with all aspects of healthcare delivery, as well as the various Acts by which a given Role is defined, identified,
guaranteed, or acknowledged by the scoper Party. (NOTE: The more formal association of a Person in a Role Assigned to a
Position with associated Responsibilities and/or Privileges is explicitly covered elsewhere in the Domain Analysis Model)
[Source:
Personnel Management]
2.443 RoleA named context in which a Party (usually, but not always, a Person) is identified in a context-of-interest. Roles represent
specific semantics involved in the relationship between two (and only two) instances of a Party: one instance of a Party
plays a Role scoped by another instance of a Party. Note that the naming of the Role may be formal or informal within the
organization, but that the identity of the instance of Person (or Organization) playing the Role does not end when the Role
itself ends. In addition, a Role specifies a competency, capability, and/or capacity which the Entity assuming the Role scoper
piece of the relationship implicitly or explicitly acknowledges as being present/possessed by the Entity assuming the Role
player portion of the relationship. In particular, the Personnel Management domain is particularly interested in the various
Roles associated with all aspects of healthcare delivery, as well as the various Acts by which a given Role is defined, identified,
guaranteed, or acknowledged by the scoper Party. (NOTE: The more formal association of a Person in a Role Assigned to a
Position with associated Responsibilities and/or Privileges is explicitly covered elsewhere in the Domain Analysis Model)
[Source:
Personnel Management]
2.444 role
-
1. A function or position.
-
2. 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.
-
3. In UML, each end of an association
is designated as a role to
reflect the function that class plays in the association.
[Source:
Core Glossary]
2.445 role name
See
association role
name.
[Source:
Core Glossary]
2.446 root class
The
class on which a
message is based. Usually the
root class for a family of messages is either the
subject class or the
class that will be first represented in the set of messages
to be built.
[Source:
Core Glossary]
2.447 RTLSSee term
Real Time Location System instead.
[Source:
Registries]
2.448 RTLS Tracking TagA Real Time Location System (RTLS) Tracking Tag (or more simply Tracking Tag) is a device that is attached to an entity (such
as a patient, provider, or medical device) that is used in conjunction with a Real Time Location System to track the movement
of that entity
.
[Source:
Registries]
2.449 Sandbag MethodThe sandbag method of referencing templates in a message instance involves the use of the infratructure templateId attribute
set to the template identifier at the point in the instace where conformance to a template is asserted AND every class in
the template is referenced (named) at the corresponding point in the instance using templateId this binds parts of the instance
to specific parts of the identified template constraints definition.
[Source:
HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates, Release 1]
2.450 scenario
A statement of relevant
events
from the problem
domain, defined
as a sequence of
interactions.
The scenario provides one set of interactions that the
modeling committee expects will typically occur in the domain.
Usually, a
sequence diagram is
constructed to show a group of
interactions for a single
scenario.
Each scenario is displayed
as a subset of the
interaction model.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.451 Schedule doseA schedule dose represents one of the expected doses in a series.
[Source:
Immunization]
2.452 Schedule seriesA series is the constellation of vaccine doses that meet the criteria to be considered protected against members of a vaccine
group. More than one series may meet those goals and some series may be amended based on history. For instance, there are
several series that can meet the goals of HIB. The number of doses recommended for one of these series changes, based on current
age and history of vaccination.
[Source:
Immunization]
2.453 schema
-
1. A diagrammatic presentation, a structured framework, or a plan.
-
2. 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. For example, XML Schema is a
specification in SGML
of the structure of a document or set of data.
[Source:
Core Glossary]
2.454 schema view
A link to the
schema used to
validate XML messages that conform to a particular
message type.
[Source:
Core Glossary]
2.455 scope
-
1. A definition of the range or extent of a project undertaken
by a Technical Committee.
-
2. A means of constraining a
role
(i.e. a role is “scoped by” an entity).
[Source:
Core Glossary]
2.456 SCTSNOMED-CT Systematic Nomenclature of Medicine Clinical Term
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.457 SDOStandards development organization
[Source:
Emergency Medical Services]
2.458 section
In the HL7 Version 3 Guide, a method of grouping related information
into
domains.
These domains include Infrastructure Management,
Administrative Management, and Health & Clinical Management.
[Source:
Core Glossary]
2.459 SemanticIn the context of a technical specification, semantic refers to the meaning of something as distinct from its exchange representation.
Syntax can change without affecting semantics.
[Source:
Core Glossary]
2.460
semantic interoperabilitya receiving application should be able to retrieve and process communicated information, in the same way that it is able to
retrieve and process information that originated within that application.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.461 sequence diagram
See
interaction diagram
.
[Source:
Core Glossary]
2.462 SerializationA frequent requirement is to output a final result tree as an XML document (or in other formats such as HTML). This process
is referred to as serialization.
[Source:
XML Implementation Technology Specification, Release 2]
2.463 Serialization ModelThis is the model comprised of classes with attributes that correspond directly to the XML elements and attributes that appear
in instances. A serialisation model is derived from a RIM based model using the rules defined by the Reshaping Annotations.
For an Actual Serialisation Model the XML elementa nd attributes take names from the model, whereas the Standard Validation
Model, and any Templates, are Serialisation Models where the class and attribute names may not correspond to the XML elements
and attributes.
[Source:
XML Implementation Technology Specification, Release 2]
2.464 ServiceA specific service, e.g., a medical procedure
[Source:
Emergency Medical Services]
2.465 Service LevelThe level of service provided, particularly with regard to urgency
[Source:
Emergency Medical Services]
2.466 Service TypeCategory of emergency medical service, e.g., rescue, transport, hazardous materials response
[Source:
Emergency Medical Services]
2.467 set
A form of
collection which
contains an unordered
list of
unique elements of a single type.
[Source:
Core Glossary]
2.468 SGMLStandard Generalized Markup Language, ISO 8879:1986(E) as amended and corrected
[Source:
Core Glossary]
2.469 SHALLThe conformance verb SHALL is used to indicate a requirement. See the
conformance verb definition for more information.
[Source:
Core Glossary]
2.470 Shell MethodThe shell method of referencing templates in a message instance involves the use of the infrastructure templateId attribute
set to a template identifier at the point in the instance where conformance to a template is asserted.
[Source:
HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates, Release 1]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.471 Short Stay EncounterA patient encounter where the patient is admitted to a health care facility for a predetermined length of time, usually less
than 24 hours.
[Source:
Patient Administration]
2.472 SHOULDThe conformance verb SHOULD is used to indicate a recommendation. See the
conformance verb definition for more information.
[Source:
Core Glossary]
2.473 SiteA location from which a unit may be dispatched
[Source:
Emergency Medical Services]
2.474 SiteCodethe Concept code for the location on the body of an observation or procedure
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.475 SNOMEDSystematic Nomenclature of Medicine
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.476 SNOMEDSystematized Nomenclature of Medicine
[Source:
Core Glossary]
2.477 SNPA variation that occurs in human DNA which is common and minute. These variations are usually inherited in families or might
be idiosyncratic.
[Source:
Clinical Genomics]
2.478 SNP-HaplotypePatterns of SNPs on a block of DNA.
[Source:
Clinical Genomics]
2.479 specialization
An
association between two
classes (designated
superclass and
subclass),
in which the subclass is derived from the superclass. The
subclass inherits all properties from the superclass,
including
attributes,
relationships, and
states, but
also adds new ones to extend the capabilities of the superclass.
[Source:
Core Glossary]
2.480 Specific Serialization ModelThe specific serialization model for a static model is the model expressed in UML or an XSD schema document by applying the
reshaping rules to the rim based expression of the static model.
[Source:
XML Implementation Technology Specification, Release 2]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.481 specification
A detailed description of the required characteristics of a product.
[Source:
Core Glossary]
2.482 SpecimenA sample obtained from a subject on which observations are performed. A specimen is a type of partitive role in which, the
player is a material taken as a sample from a source scoping entity. For example, a specimen of venous blood taken from a
patient for a laboratory investigation.
[Source:
Laboratory]
2.483 sponsor (of an application)
In the context of
conformance claims
, the vendor, in-house developer, or provider of
public domain software for a healthcare information system.
[Source:
Core Glossary]
2.484 Standing OrderAn instruction for care in force indefinitely for emergency use in the absence of a medical doctor
[Source:
Emergency Medical Services]
2.485 state
A named condition of a
classinstance (
object) that can be tested by
examination of the instance's
attributes
and
associations.
For more information refer to the
Dynamic Behavior section of the Version 3 Guide.
[Source:
Core Glossary]
2.486 state attribute
An
attribute describing the
current
state of an
object.
For more information refer to the
Attributes section of the Version 3 Guide.
[Source:
Core Glossary]
2.487 state diagram
A graphical representation of a
state transition model showing
states
as vertices (nodes) and
state transitions as directed arcs (arrows) between the nodes.
[Source:
Core Glossary]
2.488 state flag
A discrete value of a single enumerated
domain
of partial
states. State
flags are included in a state
attribute
in a
message instance
that indicates the
joint state
of an object.
[Source:
Core Glossary]
2.489 state machine
A description of the life cycle for
instances
of a
class, defined by a
state transition model.
[Source:
Core Glossary]
2.490 state transition
A change in the
state of an
object, as a result of a change
in its
attributes
or
associations.
For more information refer to the
Dynamic Behavior section of the Version 3 Guide.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.491 state transition model
A graphical representation of the life cycle of a
class. The
model depicts all of the relevant
states of a class, and the valid transitions
from state to state.
[Source:
Core Glossary]
2.492 Static ModelThis is the definition of a particular HL7 static model, and exists as an XML document that conforms to the MIF specification.
[Source:
XML Implementation Technology Specification, Release 2]
2.493 steward committee
The Technical Committee within HL7 which has primary responsibility
for specifying properties for a
class
in the
Reference Information Model (RIM). The steward
committee must be consulted on any proposed changes to the
properties of classes under its stewardship.
[Source:
Core Glossary]
2.494 stewardship representative
An individual member of the
steward committee, authorized by the
committee to speak on behalf of the committee, and to represent the
interests of the steward committee.
[Source:
Core Glossary]
2.495 storyboard
A narrative of relevant
events
defined using
interaction
diagramsor use cases. The storyboard provides one set
of
interactions that the
modeling committee expects will typically
occur in the
domain.
[Source:
Core Glossary]
2.496 storyboard diagram
See
interaction diagram.
[Source:
Core Glossary]
2.497 structural attribute
An
attribute whose coded
values are needed to fully interpret the
class with which it is
associated.
[Source:
Core Glossary]
2.498 stylesheetA file that describes how to display an XML document of a given type
[Source:
Core Glossary]
2.499 sub-section
In the HL7 Version 3 Guide, a
section
within a major section.
[Source:
Core Glossary]
2.500 sub-state
An identifiable
state of a
class that has a more specific
definition than, and is entirely encompassed within the scope
of, its
super-state.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.501 subclass
A
class that is the
specialization of
another class (
superclass).
[Source:
Core Glossary]
2.502 subject area
A convenient aggregation of
modelclasses used to partition large
models into manageable subsets.
[Source:
Core Glossary]
2.503 subject class
A
class that a Technical
Committee designates as the central focus of a
collection of
messages.
[Source:
Core Glossary]
2.504 SubmissionA compilation of the contents of one or more submission units supporting a specific regulatory purpose or decision. In most
cases, the compilation of the submission units is utilized in the assessment of a product's quality, safety and effectiveness.
[Source:
Regulated Products]
2.505 Submission UnitA package of files as well as all file references shipped to the agency at one time. The file references are collectively
called the submission unit message.
[Source:
Regulated Products]
2.506 Submission Unit MessageAn XML construct containing all file references (not including the files) in a submission unit which describe the properties
of the files (attributes and metadata information), the links that cross reference files and the operations to perform on
files.
[Source:
Regulated Products]
2.507 super-state
A
state of a
class that encompasses two or more independent
sub-states.
[Source:
Core Glossary]
2.508 superclass
A
class that is the
generalization of one or more
other classes (
subclasses).
[Source:
Core Glossary]
2.509 surface form (of a concept)
A code value or textual description that represents a concept
identified by an HL7
concept identifier. There MAY be many different
surface forms associated with a single concept identifier.
[Source:
Core Glossary]
2.510 system
-
1. An end user application.
-
2. In HL7, a group of messages
that work together.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.511 table view
An expression of the
Hierarchical Message Description (HMD) common and
message type definition
condensed in size to fit on a printed page.
[Source:
Core Glossary]
2.512 Targets of Care'Subject' is an HL7 Participation that identifies the 'The principle target that the service acts on, e.g. the patient in
physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room
(cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects. Consumables and devices used as tools for
a service are not subjects. However, a device may be a subject of a maintenance service. '- HL7 RIM definition.
'Indirect Target' is an HL7 Participation differentiated from Direct Target by 'A Target that is not substantially present
in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the
act.' HL7 examples include 'record target,' which 'indicates whose medical record holds the documentation of this act. This
is especially important when the subject of the service is not the patient himself.' - HL7 RIM definition.
When combined with the Care Provision Act, the post-coordinated concepts are 'Targets of Care.'
[Source:
Care Provision]
2.513 Task BundleWithin the context of an instance of an Organization, a Position is a named collection of Responsibilities (including Privileges).
A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be created/defined in
terms of the Qualifications (including various forms of Credentials that a Person much have to qualify for an Assignment to
that Position).
[Source:
Personnel Management]
2.514 Task BundleWithin the context of an instance of an Organization, a Position is a named collection of Responsibilities (including Privileges).
A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be created/defined in
terms of the Qualifications (including various forms of Credentials that a Person much have to qualify for an Assignment to
that Position).
[Source:
Personnel Management]
2.515 Task BundleWithin the context of an instance of an Organization, a Position is a named collection of Responsibilities (including Privileges).
A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be created/defined in
terms of the Qualifications (including various forms of Credentials that a Person much have to qualify for an Assignment to
that Position).
[Source:
Personnel Management]
2.516 Task BundleWithin the context of an instance of an Organization, a Position is a named collection of Responsibilities (including Privileges).
A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be created/defined in
terms of the Qualifications (including various forms of Credentials that a Person much have to qualify for an Assignment to
that Position).
[Source:
Personnel Management]
2.517 Task BundleWithin the context of an instance of an Organization, a Position is a named collection of Responsibilities (including Privileges).
A Position may exist without a Person in a Role being Assigned to that Position, i.e. a Position can be created/defined in
terms of the Qualifications (including various forms of Credentials that a Person much have to qualify for an Assignment to
that Position).
[Source:
Personnel Management]
2.518 TermInfoA project started by NASA and adopted by HL7 Vocabulary Committee to define how to use SNOMED in HL7 RIM record transfers.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.519
Terminology (model)a defined or limited vocabulary of terms or concepts, for example: ICD, SNOMED, LOINC.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.520 Termsa member of a terminology; a defined or limited vocabulary of terms or concepts, for example: ICD, SNOMED, LOINC.
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.521 tightly coupled
Tightly coupled
application roles assume that
common information about the
subject classes participating in a
message is available to
system components outside of the specific message.
[Source:
Core Glossary]
2.522 Time-based Criterion
[Source:
Personnel Management]
2.523 Time-based Criterion
[Source:
Personnel Management]
2.524 Time-based Criterion
[Source:
Personnel Management]
2.525 Time-based Criterion
[Source:
Personnel Management]
2.526 Time-based Criterion
[Source:
Personnel Management]
2.527 Tissue-TypingTissue Typing/HLA-typing: A blood test that helps evaluates how closely the tissues of the donor match those of the recipient.
[Source:
Clinical Genomics]
2.528 TissueTypingFacilityThe examination of human leukocyte antigens (HLA) in a patient. Tissue typing is done for all donors and recipients in organ
transplantation to help match the donor and recipient.
[Source:
Clinical Genomics]
2.529 transaction
A complete set of
messages for a
particular
trigger event,
e.g., a message and a response.
[Source:
Core Glossary]
2.530 transport wrapper
A
wrapper that contains
information needed by a sending
application or
message handling service to route
the
message payload to the
designated receiver. All HL7 Version 3 messages SHALL have an
appropriately configured transport wrapper.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.531 trigger event
An
event 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.
[Source:
Core Glossary]
2.532 Types of Annotation to Region RelationshipsThere are some annotation codes that can mean slightly different things depending on the context. For example, the annotation
"Atrial Fibrillation (AFib)" could mean two different things when related to a region: "The subject was in AFib here.", or
"The subject experienced an episode of AFib from here to there." There are 2 act relationships in HL7 to distinguish between
these two types of annotations. The "has support" relationship is the more general one to be used for "there is AFib here"
types of annotations. The "has bounded support" relationship can be used to declare the boundaries of the annotation, "there
is a (bounded) episode of AFib here."
[Source:
Regulated Studies]
2.533 UMLThe Unified Modelling Language specification is maintained by the Object Management Group. The specification can be found
at
http://www.uml.org
[Source:
XML Implementation Technology Specification, Release 2]
2.534 UML
See
Unified Modeling Language.
[Source:
Core Glossary]
2.535 uncertaintyCodeThe Act.uncertaintyCode is defined by HL7 as “A code indicating whether the Act statement as a whole, with its subordinate
components has been asserted to be uncertain in any way.”
[Source:
Using SNOMED CT in HL7 Version 3; Implementation Guide, Release 1.5]
2.536 Unified Modeling Language
A language for the creation of
domainmodels.
UML was created in order to
unify several well-known object-oriented modeling
methodologies,
including those of Booch, Rumbaugh, Jacobson, and others.
[Source:
Core Glossary]
2.537 union message
A
message type that contains
the elements of several
message
structures drawn from the same
Hierarchical Message Description. A union message
includes all the
message elements
that SHALL be sent from one
application role to all other application roles in
response to a
trigger event.
[Source:
Core Glossary]
2.538 universal CMETA CMET variant that includes all attributes and associations present in the R-MIM. Any of non-mandatory and non-required attributes
and/or associations may be present or absent, as permitted in the cardinality constraints.
[Source:
Common Model Element Types]
2.539 user
In the context of
conformance
claims, the organization that uses an
application. This is
frequently the buyer but in some cases the user and
sponsor organizations may be
parts of the same organization, or otherwise have a business
relationship other then vendor-buyer.
[Source:
Core Glossary]
2.540 Vaccination forecastThe vaccine administration recommendations, based on the previous history of vaccination, patient/client age, and patient/client
health conditions. These recommendations would be derived from the series selected in the schedule selected.
[Source:
Immunization]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.541 Vaccination historyThe collection of vaccine doses actually administered to a patient.
[Source:
Immunization]
2.542 VaccineThe product that composes an immunization.
[Source:
Immunization]
2.543 Vaccine group/vaccine familyThe set of vaccines that can be administered to meet the patient's goal of being protected against a particular infectious
disease or set of diseases.
[Source:
Immunization]
2.544 Valid DocumentA document which meets all of the validity constraints in the XML Specification
[Source:
Core Glossary]
2.545 Value DomainA ValueDomain is a set of accepted representations for the intended meanings of a DataElementConcept. A ValueDomain may act
as an indirect reference to a domain that is defined in another registry. If so, it will have no child EVDElements. The externally-defined
domain will be identified through the ValueDomain's Source* attributes.
If an application receives a refererence to an externally defined domain, it should treat it in this way (in examples, we'll
suppose that the domain is "Severity" as defined in LOINC)
SourceCodingSystem is the name of the coding system (or coding scheme) that contains the domain definition. An example would
be LOINC.
SourceCodingSystemGUID is the identifier of the coding system holding the domain definition (for LOINC, it would be the official
GUID by which LOINC as a whole is known).
SourceCodingSystemVersion supplies the version number of the coding system containing the domain of interest. If it is 3.0,
then the receiver should look for the domain definition in version 3.0 of the specified coding system.
SourceDomainId is the identifier of the domain of interest within the specified coding system. If the concept Severity has
the coded identifier 789 within LOINC, the value of SourceDomainId would be 789.
The attribute values pin down the concept that defines the domain.
Some externally-defined domains will have enumerated values. The set of enumerated values will be taken to be those concepts
that are the immediate children of the specified domain concept. The enumerated values must constitute a flat list. E.g.,
for Severity, LOINC might supply Mild, Moderate, Severe. This list is already flat (there are no grandchildren of Severity,
just children). This would be the set of EVD Elements. If there are grandchildren, the receiver should disregard them in constructing
the list of EVD Elements. For example, in SNOMED, the concept BodySite has a long list of children. One of these is Kidney.
Kidney is further subdivided into two grandchildren: Left Kidney and Right Kidney. The receiver of a reference to BodySite
would include Kidney in the list of enumerated elements, but leave out grandchildren such as Left Kidney and Right Kidney.
[Source:
Regulated Studies]
2.546 value set
A
vocabulary domain
that has been
constrained
to a particular
realm and
coding system.
[Source:
Core Glossary]
2.547 Version 3 Guide
A companion to the Version 3 Standard which contains the
methodological information
an HL7 member needs to understand the Version 3 standard.
[Source:
Core Glossary]
2.548 Virtual EncounterA patient encounter where the patient and the practitioner(s) are not in the same physical location. Examples include telephone
conference, email exchange, robotic surgery, and televideo conference.
[Source:
Patient Administration]
2.549 vocabulary
The set of valid values for a
coded attribute or field.
For more information refer to the
Vocabulary section of the Version 3 Guide.
[Source:
Core Glossary]
2.550 vocabulary domain
The set of all concepts that can be taken as valid values in an
instance of a
coded attribute or field; a
constraint applicable to code
values.
For more information refer to the
Vocabulary Domains section of the Version 3 Guide.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.551 vocabulary domain qualifier
Part of a
vocabulary domain specification. The two existing
qualifiers are
extensibility and
realm.
For more information refer to the
Vocabulary Domain Qualifiers section of the Version 3 Guide.
[Source:
Core Glossary]
2.552 vocabulary domain specification
A column in the
Hierarchical Message Description that specifies the
vocabulary domain
associated with a
coded attribute.
[Source:
Core Glossary]
2.553 W3CThe World Wide Web Consortium, an international industry consortium
[Source:
Core Glossary]
2.554 W3C SchemaThe three-part schema specification issued by the W3C
[Source:
Core Glossary]
2.555 Waveform EncodingThe rhythm waveforms are encoded as an Observation Series in HL7. The series contains one or more Correlated Observation
Sequences ("correlation" for short). Each correlation encodes the leads that were sampled together and correlated with the
same relative time points. If all 12 leads were sampled together (assuming a 12-lead ECG), only one correlation is required.
This correlation would contain a sequence for relative time and 12 sequences for the 12 different leads. If time was evenly
sampled (as it usually is), a GLIST<> is used for generating the sequence of time points from a few parameters. The lead
sequences would use the SLIST<> for encoding the voltages. The SLIST<> can factor out a common offset and scale factor (if
the raw integer A/D values encoded). The offset and scale factor can be used for converting the stored values to real physical
quantities. If a 12-lead ECG is recorded on a device that only samples 3 leads at a time, for example, the Observation Series
would contain 4 correlations. Each correlation would encode the leads that were sampled together. Each correlation would
contain one sequence for time relative to the beginning of the recording, and 3 sequences for the 3 leads sampled. If the
device has a few more channels and records one or more rhythm leads during the whole recording, the rhythm leads would appear
in each correlation as well.
[Source:
Regulated Studies]
2.556 Well-formed documentA document which meets all of the well-formedness constraints in the XML Specification
[Source:
Core Glossary]
2.557 WorkflowThe sequence of activities by an individual that is required to complete a specific business process.
[Source:
Care Provision]
2.558 wrapper
The control or envelope information in which the
message payload
resides. See
transport wrapper and
control event wrapper
.
[Source:
Core Glossary]
2.559 XHTMLXHTML 1.0. A Reformulation of HTML 4 in XML 1.0. W3C Recommendation 26-January-2000, revised 1 August 2002
[Source:
Core Glossary]
2.560 XML
See
Extensible
Markup Language.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X 2.561 XML DeclarationAn XML document consists of a prolog, root document element, and other objects. A data object is an XML document if it is
well-formed, as defined in the XML specification.
[Source:
Core Glossary]
2.562 XSLExtensible Style Language, a specification of the W3C An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed
into an XML document that uses the formatting vocabulary.
[Source:
Core Glossary]
2.563 XSLTXSL transformation language, a specification of the W3C
A language for transforming XML documents into other XML documents.
[Source:
Core Glossary]
Short-cut to glossary terms: A B C D E F G H I J L M N O P Q R S T U V W X