Technical report



Download 5.82 Mb.
Page43/50
Date26.04.2018
Size5.82 Mb.
#46821
1   ...   39   40   41   42   43   44   45   46   ...   50

A.3.1 e-Health Pilot


The healthcare pilot is a service-oriented architecture deployed at the data center of Dedalus SpA, a large enterprise operating in the field of e-Health applications development and one of the Healthcare software solutions and architectures leader of the Italian market. For the MIDAS Pilot, a dedicated virtual-lab has been configured and is accessible through the web. Users can access a set of implementations of standard service specifications provided in the context of HL7 – HSSP (Healthcare Service Specification Program) initiative0, that is a is an open, global community focused on improving health interoperability within and across organizations through the use of SOA and standard services.

These service specifications are:



  • RLUS for the storage of clinical documents such as clinical reports or prescriptions (HL7-CDA2), observations and clinical workflow tracking documents (IHE-XDW possibly restricted to the XTHM workflow definition)

  • XDW-API for facilitating the interaction with RLUS in case of complex operation sequences that occur when updating XDW documents.

  • IXS for the management of unique entity identities of patients, devices and/or operators.

  • CTS2 for the management of code systems and terminologies

In the context of MIDAS, a representative scenario has been selected which is the clinical treatment of patients with chronic diseases or inabilities. The scenario involves the use of RLUS, IXS and the XDW-API.

The patient is registered to a particular workflow for the diagnosis or management of long-term problems by a clinical manager who can be, for example, his/her family doctor. Then the patient undergoes a set of examinations, referrals, therapies, monitoring sessions and so on that altogether will last for a significant period. Every activity produces a dataset of clinical or administrative information that are stored into a central repository in the form of structured documents.

A workflow document is kept up to date into the repository and is continuously linked with the entire collection of information associated with the workflow itself.

All the client systems involved in the different phases of the workflow, need to interact with the IXS service interfaces for the identification of the patient at the beginning of any session and interact with the RLUS service interfaces for storing, retrieving and updating information structured as a well-formed document. The REST-based XDW-API mediates the complex updating operations on XDW documents.



The following figures depict the scenario in an informal way.




Download 5.82 Mb.

Share with your friends:
1   ...   39   40   41   42   43   44   45   46   ...   50




The database is protected by copyright ©ininet.org 2024
send message

    Main page