BY: MURTAZA ALI NOOR HUSSAIN

HELI MEHTA RESHMA PRASHAD

Dossia and Records for LivingPersonal Health Records

Dossia’s interface

What is Dossia?

A video explaining what is Dossia

http://www.dossia.org/about-dossia/an-introductionto-dossia

Background

The CEO of Dossia, Colin Evans was interviewed for this project

Started in 2006 in Boston, MA

Dossia is an employer-led, not-for-profit consortium of corporations, healthcare providers, and personal health applications developers

It provides a web-based PHR targeted mainly to employees and patients within this membership

Its services are geared primarily to the U.S. healthcare market, with no plans to expand into Canada

Architecture

Indivo's architecture for PHRs is using open standards, such as XML and JAVA

Web based interface and independent operating system platform

A three-tier system (data storage tier, a business logic tier, and a user interface tier)

Utilizes standards such as: ICD, CPT, CDT, CMS, HL7, NDC, LOINC, RxNorm, and SNOMEDCT, CCR

Uses SysTrust Certification for security

Architecture visually

Intended audience

Intended for employees in companies that have joined its alliance as a paying member

Wal-Mart has been one of their earliest adopters, and now 1.4 million employees have access to this service

Employees have their own access, they are the ones who decide to whom access is granted

Employers and insurance companies do not have access to employee records within Dossia

Business Model

Dossia was initially a non-profit group, but U.S. privacy and trade legislation prevented it so they added a for-profit service arm

Dossia markets its services at large corporations, (Fortune 500 level)

Employer-led and employer-financed

Provide SAS to avoid any installation or maintenance issues or demands on the end user.

Business Model visually

Major features

Applications can be customized for employer and consumer-based needs and service options.

Premium applications such as matching consumers to clinical trials in their local area, through a company called Trialx

Aggregated healthcare data from medications, allergies, immunizations, encounters, procedures, conditions, test results

Access to a World Health Wiki, WebMD, MediKeeper, and records from medical devices

Consumer control over access, exporting, adding and sharing of records

Background

Privately held company-US based. Incorporated in 2004 Mission:

“empowering consumers to leverage technology and the advance of scientific development towards the

improvement of their health and lives” 2005: HealthFrame 1.0 Evaluation version released 2006: HealthFrame 2.0 Live version released ($39.95) HealthFrame Lite version is available free of cost Two major applications

HealthFrame Explorer HealthFrame Viewer

HealthFrame Explorer

HealthFrame Viewer

Architecture

Computer based application, which was company developed Data stored on user’s computer

Can save reports on USB key or emergency medical card Newer version will have 2 layers:

1. Web service layer2. User interface layer

HF is standards-based Some of the data and coding standards considered are CCS codes,

DRG codes, ICD9, RxNorm, SNOMED, UMLS, ASTM CCR, CCD, HL7/CDA, RSA encryption and SSL.

Where existing standards are lacking, HF introduced open specifications or used existing open specifications such as CXP, OpenHealth Services, and Open PHR Schemas (XML schemas).

HF have also created SDK for clients to develop applications that can sync with HF

Intended Audience

Intended for any kind of consumers Patients Employers Health Care Facility Family/Friends

Users are the sole controller of the recordRFL have no access to the records

Business Model

RFL is privately ownedFairly small and new company with budget

constraintsEnd-user is responsible for updating recordsLow adoption due to consumer indifferences and not

related to security, privacy, standards, or HC complexity

RFL is responsible for providing necessary customer support

Major Features Part 1

HealthFrameWorks services: Business components, which can accelerate the

process of developing client or server-based applications

o HealthFrameWorks Server, which is the core of a service-oriented (SOA) web-service framework for building health and medical applications allowing easy integration

Co-branding allows organizations to customize HF w Re-branding allows organization complete control

over HF and recreate it fully.

Major Feature Part 2

Calendar Charts CCR Expense tracking Forms and reports Personal journals Library Medical history Related links Sync with iPod

Major Features Part 3

HealthFrame 2.0 HealthFrame 2.1 Popular

Continuity of Care Sync with iPod Calendar

Expense Tracking OHS Framework: Open Health Service framework

extends HealthFrame's reporting and web services-enabled capabilities using plug-ins

ASTM (CCR) standard: allows to share electronic medical

records with your doctors.

Related links to news, informations

Office Documents: import CCR data to and from Office

Open XML documents

Graphical Charts: provide visual feedback medical records:

tests, treatments, visits

Forums

Access to Journals and Libraries

Comparison

Features Dossia Records for Living HealthFrame

Business type Non-for profit/profit Private company Service orientation Web-based platform Computer application Data Control user controlled user controlled Audience Employees of participating

organizations Consumers, anyone and everyone

Storage Cloud storage On computer storage Use of standards Yes Yes Interoperability availability

Yes Yes (for certain formats)

Cost Free for employees, fee for employer Free for a light version, fee for the full version

Information gathered by

Mainly Dossia Mainly consumer

Questions