Interoperability Profile Documents

The latest profile documents are available here. These represent the priority areas selected in consultation with all the dallas Communities in year 1 of dallas. These documents will continue to be developed and comments and suggestions are welcome:

  • simon.bramwell@ifocus-dallas.com
  • nigel.dallard@ifocus-dallas.com
  • phil.stradling@ifocus-dallas.com
  • huw.jones@ifocus-dallas.com

Reference Architecture

In order to give a meaningful framework for the development of the Interoperability Profiles, we are developing a Reference Architecture. At this stage there are no plans to implement this architecture as it stands, but its similarity to architectures within the dallas Communities means that discussions and decisions regarding Interoperability can take place using a common understanding. In particular:

  • it also allows key interfaces to be identified and defined
  • it allows user scenarios to be examined for feasibility
  • it allows important security, information governance, authentication topics to be considered for architectural completeness

When the architecture

5. Multi-sourcing of telecare and telehealth equipment

Today there is only limited interoperability between the telehealth and telecare systems of different manufacturers. This can result in service operators feeling “locked in” to a specific supplier, and unable to purchase equipment from a different supplier, even if it is cheaper, or provides facilities unavailable from the incumbent supplier. This work area is focussed around the development of a suitable interoperability framework that would  open-up the market to greater competition, driving innovation and reducing cost of ownership. It would likely be based around agreeing  open standards upon which interfaces could be provided at various points in the overall system

6. Telehealth system integration with GP systems

One of the perceived obstacles to the widespread deployment of telehealth systems is the lack of integration between the telehealth system and the clinical information system used by GPs (and hospital consultants). This work area is focussed around removing or minimising any such obstacle, be it real or perceived. In an ideal world, it would be as easy for a GP to refer a patient onto a telehealth programme as it is to refer him/her to a hospital for diagnosis. From within his existing records system, the GP should be able to select the telehealth service, and define the parameters

4. Shared services (shared calendar, messaging, etc)

Creating informal social care networks is a fundamental requirement for reducing health and social care costs in the future. These social care networks are facilitated by IT and communication services that help people interact and support elderly and needy relatives and friends.

Interoperability Initiatives

2. Streaming multimedia

This work area is focussed around the use of streamed multimedia content within applications. This could be simultaneous two-way multimedia streaming, as used for a video call, or it could be one-way on-demand or broadcast multimedia used for education / coaching, for example. Different qualities of service and levels of security are likely to be required for different applications. For example, a “consumer-grade” service such as Skype may be adequate for interactions between family members or informal carers, but a high fidelity, higher-security system might be required if a consultation with a health professional is necessary. Ideally, it would be

9. Personal Health Records and statutory systems

With increased emphasis being placed on self-management of health and well-being, it is important that a patient can import data from his/her statutory health record into his/her personal health record, and also for him/her to be able to share this data with health professionals if he/she so desires. This work area will focus on addressing the barriers to this interfacing between PHRs and statutory systems.

Interoperability Initiatives