SMART uses OAuth2, an open standard for
granting websites/apps access to information, for
authentication and integration. This is the same
technology used by Facebook, Google and others
to allow third-party apps/websites to authenticate
a new user’s identity using an existing prole, while
allowing the user to manage what the application/
website can do with that prole (e.g. logging into
Candy Crush with your Facebook prole and
allowing it to post your in-game achievements on
your Facebook wall).
SMART and FHIR both use Representational
State Transfer (RESTful) architecture, meaning all
necessary information needed to respond to a
query is contained within the query. Consequently,
any server can respond to such a query without
needing additional information, accelerating
the onboarding process for new data exchange
partners.
Why Apple Health is Dierent
In some ways, we’ve been here before. As we explored
in “Existing Solutions,” previous attempts at creating a
complete, patient-centric health record were ambitious
but ultimately failed to achieve widespread
adoption. Nevertheless these previous solutions,
along with current patient portals, were and
continue to be based on the laudable premise that
putting users in control of their own health data will
lead to stronger engagement and better outcomes,
especially when it comes to compliance with chronic
disease care plans.
Unlike previous eorts, however, Apple Health
benets from being very much in the right place at
the right time: oering a truly interoperable solution
based on the latest open standards and in full
control of a rich ecosystem and trusted platform
(the iPhone) that are deeply embedded in users’
lives. The iPhone, with its large and dedicated user
base, constitutes a great platform to scale the
adoption of the Apple health records feature.
The initial set up would involve searching for your
provider within the app, and then verifying your
identity by logging into the patient portal using
OAuth2.This establishes a trusted link between
your provider and the app, which can now securely
update your health record in the background and
send your phone notications when any changes
are made. After performing this set-up with all
providers, the app will aggregate dierent types of
health information like lab results, immunization
records, procedures, allergies and vitals from
multiple institutions on one screen on your iPhone.
Furthermore, as this set-up is ultimately mediated
by the user’s patient portal credentials, the Health
app can also help increase familiarity with provider
patient portals.
Where Smile Digital Health Fits In
Smile Digital Health, as the commercial
implementation for HAPI (the open source FHIR
API for Java), is the best choice for full FHIR stack
integration with Apple.
OAuth2, a prerequisite for SMART on FHIR, is
built into Smile Digital Health, leaving the door
open for future integration with any conformant
OAuth2 provider—not just Apple. It is OAuth2
(along with FHIR’s discrete date model) that enables
the granular user permissions mentioned in the
previous discussion of FHIR.
4. Optimal Solution: Smile Digital Health as an Integration Platform
for SMART on FHIR Data Sharing With Apple Health
continued
6
www.smiledigitalhealth.com