FHIR Chat · IPS and IPA (not the beer ;-) ) · IPS

Stream: IPS

Topic: IPS and IPA (not the beer ;-) )


view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 16:13):

In the IPS call @Ken Sinn has made the team aware about the presence of an IPA (International Patient Access https://build.fhir.org/ig/grahamegrieve/ipa-candidate/index.html) IG.

@Grahame Grieve is this a draft work ? is this an example IG ? is this something else ?

view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 16:18):

This seems to go in the direction of a more generic "IPS library" also discussed in the last IPS meeting in Atlanta

view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 16:18):

pasted image

view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 16:20):

The IPS "core" profiles mentioned in that slide (from the last WGM IPS meeting Wed Q2)

view this post on Zulip Grahame Grieve (Oct 02 2019 at 19:04):

IPA is very draft, but it's also serious; it's a description of a single simple API that can be adopted anywhere in the world. It's like the least common denominator - compatible with Argonaut / US Core and also with IPS, though it does something different to IPS. Did you read the page about the relationship betwene IPA and IPS?

view this post on Zulip Rob Hausam (Oct 02 2019 at 19:08):

I think the relationship page does spell it out pretty clearly - ideally they are complementary specifications.

view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 19:28):

IPA is very draft, but it's also serious;

so if my understanding is correct it is a sort of proof of concept intended to become a project in HL7...

view this post on Zulip Grahame Grieve (Oct 02 2019 at 19:30):

yes. I will be bringing it forward atSydney

view this post on Zulip Giorgio Cangioli (Oct 02 2019 at 19:53):

though it does something different to IPS. Did you read the page about the relationship betwene IPA and IPS?

Yes I read it , and i agree that they are doing different jobs; but both seems to respond to the same need, that of defining a set of common minimal data blocks globally usable.
In one case accessible singularly (the IPA) in the other as a "packaged" summary (the IPS).

Probably this may resolve also some ambiguity that in my opinion still we have in the IPS between the IPS as a document and the IPS as a library (see also https://chat.fhir.org/#narrow/stream/207835-IPS/topic/IPS.3A.20Document.20Vs.20Library).

I like the name that reminds the IPS, so we can say that the "IPS" is evolving to the "IP*" :-)

view this post on Zulip Grahame Grieve (Oct 02 2019 at 20:00):

Name choice was deliberate. IPA is one way of accessing IPA. But, of course, you can access non-IPS comformant content was well using IPA


Last updated: Apr 12 2022 at 19:14 UTC