[Openid-specs-heart] Current Medications on FHIR

[Adrian Gropper]

I think Grahame and I are saying exactly the same thing. My point is that
HEART is in the middle of this and HIE of One is demonstrating the only
standards-based solution so far.

The deeper question is the role of "software statements" in Grahame's
"drowning in options" future. Some of the options will rely on software
statements and others will rely on individual credentials. The governance
for individual physician credentials is mostly in place. The infrastructure
for software statements and other federation-dependent systems has eluded
us for a decade. HEART should not wait for software statements to enable
this patient-centered space.

Adrian

On Wed, Dec 14, 2016 at 4:55 PM, Grahame Grieve <
grahame at healthintersections.com.au> wrote:

> Most institutional EHRs are very reluctant to open their FHIR API to write
>> for obvious and justifiable reasons
>>
>
> actually, many institutions would like to, as would their vendors, but
> it's simply a magnitude question. Just such a lot of work to do.
> There will be some announcements in the near future about this, but it's
> too early for me to say anything more.
>
>
>> How then do we create a curated longitudinal health record?
>>
>
> well, there's no point looking to the institutional EMR vendors to provide
> a curated longitudinal health record as part of their EMR - those are
> different things. But there's plenty of work in the patient health record
> space, and this is an area with lots of energy. Including start ups, open
> source, and large vendors (very large vendors!)
> in a year's time you'll be drowning in options ;-)
>
> Grahame
>
>


-- 

Adrian Gropper MD

PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
DONATE: http://patientprivacyrights.org/donate-2/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161214/caee2f69/attachment.html>