core_components.ehr_patientsummary_0.99.xsd Maven / Gradle / Ivy
--------------- original copyright -------------------------
XML Schema equivalent representation of the CEN/ISO 13606
part 1 model for Electronic Healthcare Record Exchange.
This version of the schema emphasises (1) fidelity to the
13606-1 standard (even where this leads to sub-optimal XML
representation) and (2) maximum use of W3C XML Schema
features (even where this increases parser complexity). This
Schema definition conforms to the 13606-1 version published
February 2007.
(c) 2008 CHIME, University College London.
Created by Taher Hassan.
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
Modified by Brainpool-Mawell to use ISO datatypes, split
into separate schemas, corrected and simplified.
Rodolfo Garcia
Kristin Schoug
Torbjorn Dahlin
-----------------------------------------------------------------------------
v1.1 2008-10-29. Modified by Andreas Ostberg - Arkitekturledningens T-grupp
Modification of LINK-type. Additional optional attribute target_type. Holds a
code about the type of content of the target(s). There can only be 0-1
target_type in LINK, therefore it is not possible to use target_type if LINK
is referring to several different types of targets. If it is still necessary to set
target_type use one LINK for each type of target.
v1.2 2009-02-03: Modified by Kristin Schoug Bertilsson. The attribute
elementFormDefault="qualified" was added because of problems with the
nameSpace validation.
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
2012-06-18 Hjalmar Jacobson (Tieto) har skapat detta schema. Innehållet i
detta schema kommer från schemafilerna ”SE13606-1.xsd” och ”SE13606-1_demographics.xsd”
-----------------------------------------------------------------------------
The root node of an EHR Extract.
Restrictions or filters on the creation of the EHR Extract.
The time_period should be a restriction on the data types
of low and high to make them TS, but this restriction is
not permissible in XML Schema and thus the IVL properties
are simply copied here with the appropriate types.
Superclass of all concrete aggregator classes in the EHR
hierarchy.
Organises and groups Compositions within an EHR Extract.
Key aggregation class representing the set of Record
Components authored and committed during a single clinical
encounter. Note the values for territory will indicate
the legal framework under which the data was committed.
The session_time should be a restriction on the data types
of low and high to make them TS, but this restriction is
not permissible in XML Schema and thus the IVL properties
are simply copied here with the appropriate types.
Superclass of Section and Entry that enables the former to
include instances of itself.
Represents a heading in the record under which further
Entry instances might be found.
Represents the information acquired for a single clinical
activity or recording. The Entry may be nilled if it
corrects a previous erroneous version.
Superclass of Cluster and Element that enables the former
to include instances of itself. The obs_time should be a
restriction on the data types of low and high to make them
TS, but this restriction is not permissible in XML Schema
and thus the IVL properties are simply copied here with the
appropriate types.
Represents hierarchical organisation of data values.
The Data Value holder in the aggregation structure.
The committal and revision data for a Record Component.
Note that the invariant is incorrectly stated as
constraining "attribute_version_status.coding_scheme_name"
in the printed standard.
Any attestations for a Record Component. The proof field
should be a cryptographic hash of the RECORD_COMPONENT it
attests, but it is recognised that in many implementations
the components will change to point to new components that
revise them. In that case, the proof should sign the
unchanging parts of the component only.
The participation of an entity in the EHR.
Identifies the relationship of a person to the subject of
care. Specifically used in Entry.subject_of_information.
Creates a relationship between two Record Components that
is orthogonal to the common one of containment. Note that
if a recipient is not permitted to see the component linked
to, even revealing the link constitutes an inappropriate
disclosure. Role is of type CD so that the displayName
property of that class can be used in place of any specific
coding scheme.
Superclass of all identified parties to the record. Note
that the type of id is not given in the printed class
description but is included in the class diagram on page
47 of the standard.
A piece of equipment or a device.
An organisation corresponding to GPIC 2.008 (2008 in the
printed standard).
General demographic information about a person
corresponding to GPIC 2.006.
Reference to an identified healthcare professional, derived
from GPIC 2.034.
Describes the role of a healthcare professional in the
record, based on the GPICS class of the same name. Note
that the id instances should refer to the same identified
individual, but might be needed to establish that
individual's identity in different working environments.
Identification information about a person corresponding to
GPIC 2.015.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy