Pages

Tuesday, November 13, 2012

IHE mHealth Hackathon

Updated: Official IHE announcement of the mHealth Hackathon

The Mobile access to Health Documents (MHD) profile offers access to the Document Sharing environment from platforms that prefer to use more simple interface technologies. The MHD profile takes the approach of REpresentational State Transfer (REST), a resource centric view; and leverages the technologies readily found on Mobile Devices (HTTP, Atom, JSON). This new interface to the Document Sharing environments is expected to extend the reach to devices and workflows. This new interface is not a replacement for XDS, XDR, or XCA; but rather provides a new programming interface to these Document Sharing infrastructures.

Mobile access to Health Documents (MHD) profile defines a simple HTTP interface to an XDS like environment. It defines transactions to a) submit a new document and metadata from the mobile device to a document receiver, b) get the metadata for an identified document, c) find document entries containing metadata based on query parameters, and d) retrieve a copy of a specific document. These transactions leverage the document content and format agnostic metadata concepts from XDS, but simplify them for access by constrained environments such as mobile devices. The MHD profile does not replace XDS. It can be used to allow mobile devices constrained access to an XDS health information exchange.

The Hackathon to be held at the IHE Connectathon on Wednesday afternoon and evening will provide the attendees insight into this profile and provide an opportunity to play around with it. The Hackathon will bring together implementers of the profile and those that might be interested in using it. The goal is twofold: First to provide a social environment to share experiences with implementations of the profile, and Second to help improve the profile. The profile use of languages that are implemented broadly in many devices and toolkits should offer a chance to develop rapid prototypes of applications. The goal of the rapid prototyping is to play around with the MHD profile interface. The environment will be an extension of the normal IHE Connectathon atmosphere to encourage creativity and problem solving.

Agenda:
  • Presentation of MHD profile goal and content.
  • Presentation of mobile authentication profile development in 2013 IHE ITI Planning for 2013
  • Presentation of a few implementations of the server side of this profile
  • Presentation of a few implementations of mobile applications?
  • Examination of HL7 FHIR advancement of the concept of MHD
  • Hacking: given the programming tools of today we expect to see some quick prototyping of applications that could go onto mobile devices and leverage the MHD profile.
  • Discussion and Summary
An Implementation Guide is being maintained at mHealth Dossier Guide. We expect to continue to share practices using this wiki, and will publish the results of the hackathon as appropriate.


Updated: Official IHE announcement of the mHealth Hackathon

3 comments:

  1. John, another topic I was curious about was whether IHE considered CMIS before creating the MHD protocol.

    CMIS is described well at Wikipedia: http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services

    We've used CMIS in healthcare to some success but it's more prevalent use across sectors and has a decent amount of supporting software available.

    ReplyDelete
    Replies
    1. Yes we did consider CMIS, it is a nice system but quite complex. We were looking for the lowest technology that we could, CMIS is far more complex.

      You can see our analysis of all alternatives at ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr10-2012-2013/Technical_cmte/WorkItems/DocumentsForMobileHealthSupplement/MHD_alternatives_20120404.xlsx

      Delete