XDS for Mobile HealthXDS for Mobile Health

Brief Profile Proposal for 2009/10Brief Profile Proposal for 2009/10presented to thepresented to the

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Keith W. BooneKeith W. BooneSeptember 22, 2011September 22, 2011

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

The Problem

Support for XDS in mHealth EvironmentSupport for XDS in mHealth Evironment•mHealth platforms are resource constrainedmHealth platforms are resource constrained

– SOAP Stack missing or buggy (e.g., WSDL support for Objective C)SOAP Stack missing or buggy (e.g., WSDL support for Objective C)– Bandwidth constrained (10Kbps to 10Mbps)Bandwidth constrained (10Kbps to 10Mbps)– Limited resources (e.g., memory), often no “back-end” serverLimited resources (e.g., memory), often no “back-end” server

•Increasing proliferation of unconnected appsIncreasing proliferation of unconnected apps– ~9,000 consumer health apps~9,000 consumer health apps11 in Apple’s App store in Apple’s App store– ~13,000 by 2012~13,000 by 2012

•mHealth is an emerging market, failure to support this space mHealth is an emerging market, failure to support this space could reduce relevance of IHEcould reduce relevance of IHE•Difficult to use XMLHttpRequest for browser based, Difficult to use XMLHttpRequest for browser based, multiplatform mHealth apps.multiplatform mHealth apps.11Source: MobiHealthNews http://shar.es/HMlffSource: MobiHealthNews http://shar.es/HMlff

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Use Case

• Patient sees a specialist for a particular condition.• The specialist asks for detailed information from the

patient.• The patient, not remembering their list of medications, pulls

out their mobile device and activates an application.• The application queries the HIE and retrieves a list of

clinical summaries in date order, from most to least recent (or on-demand medication list document).

• They select the most relevant document, and it is downloaded to the device. The application extracts and displays their medication list.

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Proposed Standards & Systems

• StandardsStandards– XMLXML– XDS MetadataXDS Metadata– ebXMLebXML– XSLTXSLT– JSON, JSON SchemaJSON, JSON Schema– XmlHttpRequestXmlHttpRequest– OHT Restful APIOHT Restful API

• SystemsSystems– EHR, PHR, Patient Portal, HIE, Mobile devicesEHR, PHR, Patient Portal, HIE, Mobile devices

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Discussion

• There has been substantial work already in simplifying the There has been substantial work already in simplifying the XML in OHT, that could be used as one basis for the effort.XML in OHT, that could be used as one basis for the effort.

• Metadata could be transformed from a simplified Metadata could be transformed from a simplified representation to ebXML representation using XSLT.representation to ebXML representation using XSLT.

• Transactions could be optimized to use W3C standard Transactions could be optimized to use W3C standard XMLHttpRequest object. object.

Mobile Document

Source

Mobile Document Consumer

Document Repository

Proxy

Document Registry

Proxy

[ITI-17] Retrieve

Document?

[ITI-XX] Provide and Register

Document.m

[ITI-YY] Stored Query.m