Pages

Wednesday, June 29, 2016

Apple makes a difference with targeted use of Differential Privacy

Amazing news this week from Apple on their use of Differential Privacy. They didn't invent Differential Privacy, they are not the first to use De-Identification, but they seem to have thought about this. We can't yet tell how well they thought about this, as the details are not clear. That is, they are still not being Transparent.

I am not an Apple fanboy, I think they get far too much credit and buzz. I don't think this is their fault, they are masters of marketing, and they never claim to have created something no-one else has. What they do very well is take technology that is just slightly behind bleeding edge, letting someone else get most of the cuts and blood, and the critical thing, they use it in a way that provides really good value. It is this that I am very much a fanboy for apple, they know how to pivot the work of others into a bigger value for their customers.

Differential Privacy is another case of this value-adding exceptional execution.   Specifically...

Wednesday, June 22, 2016

On-Behalf-Of - FHIR Signature datatype update

The Security workgroup is looking at the FHIR datatype for Signature, specifically the use-cases where the one signing is not the one that the agreement or contract is about. For example when a parent signs for an infant child, or a guardian signs for an individual, or where an individual signs for an organization.

We look to the Uniform Commercial Code (UCC) as one use-case for the use of On-Behalf-Of, as it is a long-standing and proven case where this is needed and has been used. ....


Tuesday, June 14, 2016

MHD - Why use of FHIR Contained?

I was asked why MHD has the requirements to contain a provider and patient in document reference. Why is that necessary?

The containment of Provider and Patient are ONLY for very specific reasons. Some are driven by XDS constraints; but even those constraints are driven by reasonable use-cases.

Friday, June 3, 2016

IHE #FHIR profiles - MHD, PDQm, and PIXm

The IHE IT Infrastructure committee has a few profiles on #FHIR. They just published new revisions  (see below) that have aligned on DSTU2, formerly on pre-DSTU2 versions. They have also just published for Public Comment a new set of supplements. All of these are aligned with DSTU2. When STU3 finishes ballot and publishes reconciled version, then IHE will adjust all of these to STU3.