64 PART II Prerequisites for an HCM
If the HCM system does not make data available via its own portal, it can also forward
data to other portals. There is always an intersection of suitable interfaces
between portals and HCM systems.
Incorporation of data
Clinical employees not only want to share the data of their own healthcare facility,
they also want to use »external« data from associations, cross-institutional files
or portals. All data that had an influence on clinical decisions should become
part of the data pool of the healthcare facility. The ways towards this can vary:
the download of such data can be started from other IT systems of the institution
or from external files. It is also conceivable, however, that users could initiate
a download directly during their work in the HCM system.
The interfaces for incorporating data are identical to those used for distribut‑
ing data.
The HCM system requires the following interfaces for communication with associations,
cross-institutional files, and portals (see Figure 6.6):
✔✔ IHE-XDS (Affinity Domains). In this case several institutions are involved
with communication. Many aspects of the internal use of IHE-XDS based
interfaces
which can be handled by cutting out the middle man now have to
be coordinated between institutions. Specifications, for example to exchange
access privileges or regarding the filing plan used, are made in the so-called
»Affinity Domains«. It is necessary that every system involved, including the
HCM system, offers a greater spectrum of technical capabilities in order to be
able to agree on a common approach within the affinity domain.
✔✔ vendor-specific interfaces
✔✔DICOM
Figure 6.6: Data streams and interfaces between HCM system/external facilities