M00020609
New product
ISO FDIS 10781 2015 Edition, January 29, 2015 HEALTH INFORMATICS - HL7 ELECTRONIC HEALTH RECORDS-SYSTEM FUNCTIONAL MODEL, RELEASE 2 (EHR FM)
In stock
Warning: Last items in stock!
Availability date: 07/14/2021
Description / Abstract:
The HL7 EHR System Functional Model provides a reference list of
functions that may be present in an Electronic Health Record System
(EHR-S). The function list is described from a user perspective
with the intent to enable consistent expression of system
functionality. This EHR-S Functional Model, through the creation of
Functional Profiles for care settings and realms, enables a
standardized description and common understanding of functions
sought or available in a given setting (e.g. intensive care,
cardiology, office practice in one country or primary care in
another country).
The HL7 EHR-S Functional Model defines a standardized model of
the functions that may be present in EHR Systems. From the outset,
a clear distinction between the EHR as a singular entity and
systems that operate on the HER, i.e. EHR Systems, is critical.
Section 1.1.3 describes the basis and foundation for the HL7
definition of an EHR System. Notably, the EHR-S Functional Model
does not address whether the EHR-S is a system-of-systems or a
single system providing the functions required by the users. This
International Standard makes no distinction regarding
implementation; the EHR-S described in a Functional Profile may be
a single system or a system of systems. Within the normative
sections of the Functional Model, the term "system" is used
generically to cover the continuum of implementation options. This
includes "core" healthcare functionality, typically provided by
healthcare-specific applications that manage electronic healthcare
information. It also includes associated generic application-level
capabilities that are typically provided by middleware or other
infrastructure components. The latter includes interoperability and
integration capabilities such as location discovery and such areas
as cross application workflow. Interoperability is considered both
from semantic (clear, consistent and persistent communication of
meaning) and technical (format, syntax and physical connectivity)
viewpoints. Further, the functions make no statement about which
technology is used, or about the content of the electronic health
record. The specifics of ‘how' EHR systems are developed or
implemented is not considered to be within the scope of this model
now or in the future. This EHR-S Functional Model does not address
or endorse implementations or technology, nor does it include the
data content of the electronic health record.
Finally, the EHR-S Functional Model supports research needs by
ensuring that the data available to researchers follow the required
protocols for privacy, confidentiality, and security. The diversity
of research needs precludes the specific listing of functions that
are potentially useful for research.
This Functional Model is not:
— a messaging specification;
— an implementation specification;
— a conformance specification;
— an EHR specification;
— a conformance or conformance testing metric;
— an exercise in creating a definition for an EHR or EHR-S.
The EHR-S Functional Model is not sufficient to provide a
longitudinal health record; however, it will contribute to its
development. The information exchange enabled by the EHR-S supports
the population of clinical documents, event summaries, minimum data
sets, claims attachments, and in the future will enable a
longitudinal health record.
Additionally, it is important to note that the EHR-S Function
Model does not include a discussion of clinical processes or the
interaction of the healthcare actors. However, ISO 13940 is an
international standard that does outline key principles and
processes in the provision of healthcare. Users of the EHR-S FM can
refer to ISO 13940 for clinical processes that EHR systems
support.
This EHR-S Functional Model package includes both Reference and
Normative sections.
Each section within this document is clearly labelled
"Normative" if it is normative. For example, in Clause 7,
Conformance Clause, subclauses 7.2 and 7.4 are
normative.
In the external Annex A, Function List, the Function ID,
Function Name, Function Statement, and Conformance Criteria
components are Normative in this Functional Model