The Brusafe+ environment uses IHE XDS compliant components. Each component has a specific rol within the environment that is described on this page. More information about the transactions and how to connect to the Brusafe+environment can be found in the Connect to Brusafe+ section of this site.
Description of the Brusafe+ Components
Audit Record Repository
All systems within a IHE XDS environment need to send audit messages to a central Audit Record Repository. The audit messages are based upon the IHE ATNA profile specifications (see Audit transactions). The Audit Record Repository will store these messages, so that they can be used to track the actions of each system/application/user for tracebillity purposes.
The information is accessable and exportable by security officers so they can see who accessed what information.
Master Patiënt Index (MPI)
The Master Patient Index is a component that stores the patient ID's and other demographic information about the patients of whom information is stored in the Brusafe+ environment. This information can be requested using HL7v2 PIX and PDQ transactions. This component is only used internally and is currently not available for developers.
Document Repository
The Document Repository is responsible for storing the medical information supplied by a Document Source. These documents can be requested by Document Consumers, see Retrieve documents for more information. The Document Repository is also responsible for forwarding the metadata to the Document Registry when storing a new or updated document, see Provide documents for more information.
XDS is a content agnostic solution, meaning that it will store any type of document (i.e. PDF, HL7v3 CDA, plain text, etc.) that can be used within an XDS-document. From an interoperability point of view and the fact that systems need to be able to interpet the information, documents should (if possible) be send as a HL7v3 CDA or DICOM for images format.
Document Registry
The Document Registry keeps an index of all XDS-Documents that are available in the Repository.
Besides keeping the index, the Registry is also responsible for the validation of the metadata used. To guarantee interoperability a common set of metadata must be used when supplying a new or updated document. See Metadata for more information.
Documents in the Brusafe+ environment cannot be exchanged with healtcare professionals that do not have a patient-user relationship. The Registry uses a Access Control layer to make sure that the document is allowed to be exchanged, the decission is made based upon the metadata from the documents requested, the user information in the XUA profile (see XUA / SAML) of the person requesting the information and the registered patient consent.
If the requirements for access are not met, no information will be returned by the Brusafe+ environment.
Document Metadata Notification Broker
The Document Metadata Notification Broker is a component that systems can subscribe to. By subscribing to this component the system will recieve updates send by the Notification Broker. The Notification broker will send updates when new documents are available or certain documents are updated. The message send contains metadata about the document and the unique document ID.
Initiating- and Responding Gateway
Information between different XDS environments is exchanged using an XCA-i Gateway. This exchange is handled by the environment and Document Consumers do not need to alter their transactions to access this information. The information is subject to the given patient consent.
Integration module
The integration module offers different transactions and protocols to handle translations between non documents and XDS Documents. Using the integration module it is possible to connect non-XDS compliant Document Sources to the Brusafe+e environment. The integration module can translate HL7v2 messages to HL7v3 CDA documents and provide these to the Brusafe+environment. The module can also receive DICOM studies from a non-XDS compliant VNA or PACS (or request the study based upon a HL7v2 message). The module will convert this DICOM study to a KOS object that can be provided to the Brusafe+ environment.
HL7v3 CDA documents can also be send to this module. They can then be registered directly into the Brusafe+ environment. The module will also handle the communication between the Brusafe+ environment and the BGN based upon KMEHR standard.
MHD Document Recipient
The Document Recipient is currently being developed. This component will use the MHD profile as described by IHE. The MHD recipient can recieve a document from the Document Source and store this in the XDS Repository. More information about the Document Recipient and its transactions will become available soon.
MHD Document Responder
The Document Responder is currently being developed. This component will use the MHD profile as described by IHE. The MHD resonder can be used by the Document Consumer to query the XDS Registry for documents and to retrieve the document from the XDS Repository. More information about the Document Responder and its transactions will become available soon.
