scenarioCore Glossary:
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.
schemaCore Glossary:
1. A diagrammatic presentation, a structured framework, or a plan.
Core Glossary:
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.
schema viewCore Glossary:
A link to the
schema used to
validate XML messages that conform to a particular
message type.
scopeCore Glossary:
1. A definition of the range or extent of a project undertaken
by a Technical Committee.
Core Glossary:
2. A means of
constraining a
role
(ie. a role is “scoped by” an entity).
sectionCore Glossary:
In the HL7 V3 Guide, a method of grouping related information
into
domains.
These domains include Infrastructure Management,
Administrative Management, and Health & Clinical Management.
SemanticCore Glossary: In 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.
sequence diagramCore Glossary:
See
interaction diagram
.
setCore Glossary:
A form of
collection which
contains an unordered
list of
unique elements of a single type.
SGMLCore Glossary: Standard Generalized Markup Language, ISO 8879:1986(E) as amended and corrected
SNOMEDCore Glossary: Systematized Nomenclature of MedicinespecializationCore Glossary:
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.
specificationCore Glossary:
A detailed description of the required characteristics of a product.
sponsor (of an application)Core Glossary:
In the context of
conformance claims
, the vendor, in-house developer, or provider of
public domain software for a healthcare information system.
stateCore Glossary:
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 V3 Guide.
state attributeCore Glossary:
An
attribute describing the
current
state of an
object.
For more information refer to the
Attributes section of the V3 Guide.
state diagramCore Glossary:
A graphical representation of a
state transition model showing
states
as vertices (nodes) and
state transitions as directed arcs (arrows) between the nodes.
state flagCore Glossary:
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.
state machineCore Glossary:
A description of the life cycle for
instances
of a
class, defined by a
state transition model.
state transitionCore Glossary:
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 V3 Guide.
state transition modelCore Glossary:
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.
steward committeeCore Glossary:
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.
stewardship representativeCore Glossary:
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.
storyboardCore Glossary:
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.
storyboard diagramCore Glossary:
See
interaction diagram.
structural attributeCore Glossary:
An
attribute whose coded
values are needed to fully interpret the
class with which it is
associated.
stylesheetCore Glossary: A file that describes how to display an XML document of a given type
sub-sectionCore Glossary:
In the HL7 V3 Guide, a
section
within a major section.
sub-stateCore Glossary:
An identifiable
state of a
class that has a more specific
definition than, and is entirely encompassed within the scope
of, its
super-state.
subclassCore Glossary:
A
class that is the
specialization of
another class (
superclass).
subject areaCore Glossary:
A convenient aggregation of
modelclasses used to partition large
models into manageable subsets.
subject classCore Glossary:
A
class that a Technical
Committee designates as the central focus of a
collection of
messages.
super-stateCore Glossary:
A
state of a
class that encompasses two or more independent
sub-states.
superclassCore Glossary:
A
class that is the
generalization of one or more
other classes (
subclasses).
surface form (of a concept)Core Glossary:
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.
systemCore Glossary:
1. An end user application.
Core Glossary:
2. In HL7, a group of
messages
that work together.
(Return to glossary index)