The e-portal for healthcare professionals is an intuitive user interface for professionals in the healthcare sector.
The e-portal primarily provides access to a patient’s data, images and documents that are relevant to treatment by healthcare professionals. Healthcare professionals can publish data, images and documents in patient records, making them available to other healthcare professionals or patients. Other services such as e-report transfer, e-image data management, e-transfer / e-referral or remote consultation can also be used via the e-portal. A wide range of configuration options are available to the portal user, including for example filter and sort settings or subscription to notifications.
All access to data and documents is controlled by the ACS (Access Control System), preventing unauthorized access. If the e-portal is accessed directly from a primary system, no additional login is required.
The e-portal for patients provides an intuitive user interface that allows patients to use all features on offer.
The e-portal primarily provides patients with access to their own data, images and documents that have been published by affiliated healthcare facilities, as well as full management of all access rights. Patients can upload their own data, images and documents to their personal electronic record, making them available to healthcare professionals. Additional future services such as remote monitoring or the integration of devices and apps can also be used via the e-portal. A wide range of configuration options are available to the patient, including for example filter and sort settings or subscription to notifications.
Patients can use access logs to view all access to their own data and documents.
Swiss Post’s web portal for patients meets the requirements of the EPDG (Federal Act on the Electronic Patient Record) in all respects.
The ACS is an access control system that checks participants’ access rights for each request. The access system is attribute-based, allowing flexible project-specific design of access policies. In cases of access, the system takes care of the authorization of participants. The ACS checks the request against a set of policies that explicitly allow or deny access, ensuring that participants can only see content intended for them.
In the context of access to patient data, this means that all requirements of the EPDG (Federal Act on the Electronic Patient Record) can be met. Patients and their representatives can configure the ACS with user-friendly user interfaces, as can healthcare professionals in the event of delegation.
The Audit Record Repository (ARR) is a storage location for records of all transactions within a (core) community.
This makes it possible to reconstruct the use of the system as a whole and detect unwanted processes at a later date. The ARR is used to provide transparency for patients and users on the one hand, and for system maintenance on the other. All processes on the Post E-Health platform are logged. This means that all interactions (e.g. assignment of rights, document publication, patient identification, document search) generate detailed log entries in the ARR. This applies equally to failed attempts, facilitating early detection and analysis of security-related events.
In addition to a range of technical information, records include for example the institution from which a user retrieved, adapted or published specific documents relating to a patient. This means that it is possible to find out at any time who accessed or changed data or documents and when. On the basis of the records, various evaluations of the use of the system as a whole are also possible.
The Cross Community Gateway (CCG) allows different (core) communities to exchange information with each other. The search for patients, documents or images in the other community or core community is specifically through this gateway.
The CCG is currently used only in the context of the EPDG (Federal Act on the Electronic Patient Record) and guarantees interoperability across community boundaries for the whole of Switzerland.
The CCG therefore allows all information for the optimum treatment of a patient to be made available.
With regard to targeted communication, the CCG cannot yet guarantee interoperability, as no nationwide standardization of processes or interfaces has yet been defined for it.
Service for finding and selecting healthcare professionals
The Healthcare Provider Directory (HPD) is a directory service for the collection and management of information about healthcare professionals and their healthcare organizations within a community or core community.
In conjunction with the EPR (electronic patient record), HPD entries are used for access control, allowing patients to find their healthcare professionals and healthcare organizations and grant or withdraw specific access rights. The HPD for a community or core community is matched with the national EPR-HPD service, so that patients can also search and find healthcare professionals and organizations from other communities or core communities.
With respect to targeted communication, HPD entries are used in the sense of a business partner database to select the correct document and data recipients. Various configurations allow for example the definition of preferred receipt channels for recipients.
Every IT system requires user administration for system access. In the Post E-Health platform, this function is handled by an identity and access management (IAM) component. All users of the platform are registered and managed in the IAM. Roles can be used to make various features of the platform available to specific user groups. For example, the functionality for making out prescriptions can be made available exclusively to a healthcare professional with the role of physician. This should not be confused with the Access Control System (ACS), which controls access to patient data.
The IAM ensures secure identification and authentication of users. Its implementation complies with the requirements of the Federal Act on the Electronic Patient Record (EPDG).
Patient information is stored by every healthcare organization. To ensure that each organization publishes the documents in the correct patient record, the organization’s patient data must be linked to the correct patient record.
The Master Patient Index (MPI) manages the various patient identities found on the IT systems in a community’s or core community’s healthcare facilities. This avoids mistaken patient identities and prevents incorrect assignment of patient data and documents.
Patient identification across systems is a prerequisite for virtually all Post E-Health platform services. This infrastructure service requires a standardized connection of all IT systems in a community or core community with patient identities.
The MPI provides user interfaces and process support for the clearing of patient identities and master data (patient clearing). The organization of patient clearing is the responsibility of each community or core community. While enhancement of the quality of master data is not a primary goal of the MPI within the meaning of the EPDG (Federal Act on the Electronic Patient Record), it can be deliberately pursued by relevant organizations within the core community and used for further process steps. Typically, each community or core community has only one MPI.
Communication with MPIs from other communities or core communities is possible using the Cross Community Gateway (CCG), creating a unique patient identity across community boundaries.
While the Document Repository (REP) is used to store documents and images physically, the Document Registry (REG), stores the metadata for the documents and images, for example patient name, document type etc. This metadata allows the correct documents and images to be searched for and found. The REG is thus a directory of all documents and images in a (core) community. This directory manages only the links or references to the stored documents and images in the REP. Each entry in the REG includes a predefined set of metadata that ensures interoperability with other (core) communities. However, interoperability is only guaranteed if there is agreement on the metadata codes and values among participants, for example in the EPR. Using this document metadata, users can formulate their search queries and filter and sort displays, or control their permissions. For example the Access Control System (ACS) can be used to allow or prevent access to laboratory findings using the document type or psychiatry as a specialist medical category. Most metadata is specified by the source system, some is assigned automatically, a good deal can be changed for access control.
Each (core) community has only one REG. Communication with REGs from other (core) communities is possible using the Cross Community Gateway (CCG), allowing access to data and documents across community boundaries.
Under the EPDG (Federal Act on the Electronic Patient Record), communities and core communities are required to provide a Document Repository (REP) as a physical storage location for documents and images. The links or references in the Document Registry (REG) point to the corresponding documents and images in the REP. The connected community or core community source systems (Document Source) use standardized protocols and interfaces to send the content to the REP, where it is stored. The REP then generates the links or references in the REG. To ensure interoperability, each source system must include the predefined set of metadata with each document. Ensuring this interoperability requires an agreement on the metadata codes and values among the participants.
Each community or core community must have at least one REP, but it can also have several. The Access Control System (ACS) ensures that both the REP and the REG allow access to a patient’s documents or images only when granted authorization.