The following questions can be answered by reading the text and analyzing the 3LGM2 figures of the CityCare Example 3.11.

(a) The EHRS and the VNA in CityCare are not linked with any function they sup port. Which function of the domain layer may (partly) be supported by these application systems? Which functions (as introduced in Sect. 3.3) that are sup ported by these application systems could be added at the domain layer?

(b) In Which database system shown in the logical tool layer (Fig.3.34) should the entity type “patient” be stored?

(c) The MPI should receive messages containing PINs (entity type “patient”) from all patient administration systems. Why is there no communication link between the MPI and the patient administration system of Ernst Jokl Hospital?

(d) According to the matrix view, which functions are supported redundantly in CityCare? Discuss pros and cons of the functional redundancies in this scenario. What redundancies would you resolve and how?

(e) Which functions in which health care facility cannot be performed anymore if “Application Server 1 Ernst Jokl Hospital” fails? Suggest a change to the physical tool layer that would minimize the risk of missing function support in case a single application server fails.

(f) For the CityCare network, would it make sense to implement further profiles from IHE? Explain your decision.

Transcribed Image Text:

00011441 ospital administration management The reference model for the domain layer of hospital information systems consists of the subset of functions and entity types described in Sects. 3.2.3 and 3.3 that are relevant for hospitals. The reference model focuses on the activities in patient care. Thus, the main enterprise function is patient care, and there are maintenance func- tions supporting patient care such as supply management, scheduling and resource allocation, hospital administration, hospital management, and research and teach- ing (Fig. 3.32). Furthermore, the enterprise functions in that reference model bear a relation to each other by entity types which they can update or interpret. To define entity types within the reference model of the domain layer, the HL7-RIM was used. The Reference Model for the Domain Layer of Hospital Information Systems is available as a 3LGM model and for this reason can be immediately used for mod- eling hospital information systems. Following the definition of reference models in Sect. 2.13, the Reference Model of the Domain Layer can be used as a model pat- tern for the domain layer of hospital information systems and, additionally, can help to compare hospital information systems by means of a uniform terminology used for the domain layer. This means that, for each enterprise function of the Reference Model of the Domain Layer, it is possible to determine the support by application components in different information systems.