mHealth Plugathon

The 2019 IHE-Europe mHealth Plugathon will be held in Rennes on 10 and 11 April 2019

mHealth Plug-a-thon Rennes April 10-11, 2019

The goal of the mHealth Plug-a-thon is to provide vendors/startups developing Healthcare devices and/or Apps with a 2 days educational approach on interoperability issues to help them make their products interoperate with other systems in order to increase the value of their products in the market.

The main benefits that the participants can expect:

• Learn more about eHealth interoperability, the challenges and the implementation;
• Meet their peers and have opportunities to initiate future collaboration;
• To be part of the eHealth interoperability community and meet experts and users;
• To access this complex world by using existing assets (framework, testing tools, etc.)

The plug-a-thon is organized over two days and will include refresher sessions on the profiles & standards that will be used/illustrated during hands-on sessions.

Scope

The following themes will be covered during the two days focused on the main challenges in eHealth:

1. Management of identities and especially patient identity (local and cross-enterprise);
2. Finding relevant medical data for completing data produced by my equipment, in order to perform a diagnosis or a treatment;
3. Sharing medical data with repositories;
4. Considering security issues (patient safety, privacy, compliance with regulations).
During the two days participants are proposed with a combination of presentations and hands-on sessions.

Registration

The number of participants is limited to 25 persons. Registration fees: 750 € + VAT (20%)

Registration is OPEN

Organization

• Integrating the Health Enterprise (IHE) Europe: www.ihe-europe.net
• INRIA, French national research institute for the digital sciences: www.infria.fr
• b<>com: https://b-com.com/en/innovation-fields/connected-healthcare
• European Institute of Innovation and Technology: eit.europa.eu/eit-community/eit-health

Pre-requisite

Participants want to bring their own PC. They will need to run docker on their own machine in order to perform the exercises. Docker image configured for the exercise to be run by the participants on their machines. Docker image for the organizer with the servers reached by the participants.

IHE mHealth Plug-a-thon Program - Rennes April 10-11

Agenda

April 10th:

• 9:00-9:30: Introduction – Round table – Organization of the two days
• 9:30-12:00: Management of identities and especially patient identity;
• 13:30-16:30: Finding data relevant for completing my equipment own data in order to perform a diagnosis or a treatment;
• 16:30-17:00: VIP Tours to the IHE Connectathon

April 11th:
• 9:00-12:00: Sharing data with repositories;
• 13:30-16:30: Considering security issues;
• 16:30-17:30: Exchange among the participants / Networking followed by social event.
• 17:30-18:00: Conclusion

Management of identities and especially patient identity (local and cross-enterprise)

Coverage:
• PIX, PDQ, PIXv3, PDQv3, PIXm, PDQm;
• HPD, PWP;
• SVS.

Use cases

In order to share or find information about the patient, one needs to know the identity of the patient. The purpose of that session is present how to access the identity and how to use it.
Case 1 (local): Patient demographic is known, or patient visit, query for the identity
Use PDQ, PDQv3 or PDQm in order to find out the patient ID. Following a refresher course on the 3 profiles, the participants will be able to exercise various queries using HL7v2, HL7v3 and FHIR queries to simulators.

Case 2 (cross-enterprise): Patient ID know in local domain, querying for Patient ID in another domain
Equipment knows the patient with an ID and would like to access or share data from an equipment that knows the patient but with a different ID. Following a refresher course on PIX, PIXv3 and PIXm, the participants will be able to exercise various PIX queries using HL7v2, HL7v3 and FHIR. Simulators will be used for the exercises.

Case 3: Find professionals available in the context of my device activities
Equipment may need to propose a list of healthcare professionals in the GUI, either as a participant to an act or as a recipient of a document. Following a refresher course on PWP and HPD the participants will be able to exercise queries to the personal white pages (PWP) as well as queries to the Healthcare professional directory (HPD). LDAP is used for these queries.

Case 4: Find out if a repository contains data for a patient
An equipment may need to access data for a patient that are located in different repositories. The profile XCPD (Cross Community Patient Discovery) allows a device to query a gateway in order to find out if it knows about the patient ID. Following a refresher course on XCPD the participants will be able to exercise some XCPD queries to a simulator. Queries are using the HL7v3 protocol.

Case 5: Find out what are the code to be used
When sharing data across equipment, processing of the data is simplified if equipment share codes. SVS or Sharing Value Set is a protocol used to share coded data among various equipment. Following a refresher course on SVS the participants will be able to exercise some SVS queries. Queries are using SOAP and REST protocol.

Finding data relevant for completing data produced by my equipment in order to perform a diagnosis or a treatment.
Coverage:
• XDS.b, XDS-I.b, XDM, XDR, MHD, XCA, XCA-I, DICOMweb™.

Use cases:

How to access data concerning a specific patient and that is shared in different repository. The use case will exercise the access to the data. In the previous use case the participants have exercised the access to the Identity of the patient. Using that identifiers, the participants will now exercise how to query and retrieve data from the various repositories.

Sharing data with repositories

Coverage:
• XDS.b, XDS-I.b, XDM, XDR, XCA, XCA-I;
• CDA Content profiles, DICOM Images, DICOM SR , DICOMweb™.
• Trillium2 HL7 FHIR resources to share patient summary (consumer et creator)

Use cases:

How to share data gathered or computed by my device. In the previous use cases we have seen how to find and to use identifiers in order to retrieve data. This use case exercises how to share the added value from the device. What ever added value is brought by the device in that use case, we will exercise how to share it. What format to use in order to share it and what protocol to use to share it with existing repositories of data so that other Health Professional involved in the care of the patient may retrieve it, access it and understand it.

Considering security issues
Coverage:
• ATNA, CT, XUA BPPC;
• DICOM Part 15 (de-identification / re-identification);

Use cases:

Sharing and access patient data is only possible if security of shared data is ensured. Security of the data is a broad problem and IHE addresses it using a variety of profiles in order to answer the different aspects of the problem. The exercises will only show a subset of all the aspects.

The goal of the exercise is to show the different layer in securing a message.

Use case 1: Securing the communication

1. Use of TLS to secure the communication between two nodes. Both nodes use a certificate, mutual authentication of the node is performed before establishing the communication
a. Example with trusted node;
b. Example with untrusted node;
2. Audit trail. Monitoring of the access. Who, when, what;
3. Authentication of the user through SAML assertion;
4. Management of the patient consent.

Outcome:

Experience exchanging messages using standards promoted by IHE profiles. Be aware of their existence and have experienced using them. Reduce apprehension of using standard and encourage adoption. Then, products brought to the market should be more integrated in the ecosystem, providing participants a competitive advantage.