proposed new IHE QRPH work item

Hi all.

Carl Leitner has suggested a new work item be proposed for the upcoming IHE QRPH work cycle. Information about this proposal can be found, here:

https://www.dropbox.com/s/hprrdxopxz8ybf0/ADX_on_JSON_IHE_Profile_Proposal_Template-Brief.docx?dl=0

The proposal is to develop a FHIR-based profile for doing aggregate data exchange based on the Measure (https://www.hl7.org/fhir/measure.html) and MeasureReport (https://www.hl7.org/fhir/measurereport.html) resources. Such an approach was prototyped during the OpenHIE HacKonnectathon in Arusha, TZ last month.

The deadline for submissions is only a few weeks away (Sep 21). Please – can we have a discussion (on this thread) regarding this proposal? Also… if there is support for it… are folks who would like to participate on the authoring team?

Thanks and warmest regards,

Derek

Hi

We were scheduled to have a call this past Tuesday but, as you may
know, Simon has left us so there has been no one convening the calls.
Otherwise this would have been a good opportunity to discuss the
proposal.

It is really unfortunate I was not at the openHIE meetup in Arusha
where some of this was discussed, but some of you know I have some
misgivings. Besides putting ADX on FHIR (a prospect we discussed back
in Naples last year) as an end in itself I am not convinced what new
problem it is really solving. The adx data format is quite usable as
is. Many (including me) find the sdmx aspect a little grotesque, but
it can also be safely ignored. The data format is fit for purpose and
there are many more sensible ways of exchanging metatadata if need be,
including via CSD/facility-registry and terminology services.

It was always our intention we would do a json ADX flavour eventually,
which to my mind would be a more straightforward literal translation
along the lines of

{
  "dataSet": "MALARIA",
  "period": "2017-10-01/P1M",
  "orgUnit": "TheClinic",
  "dataValues": [
    {
      "dataElement": "MALARIA_CASES",
      "SEX": "Male",
      "AGE_GROUP": "P5Y--P10Y",
      "value": "8"
    },
    {
      "dataElement": "MALARIA_CASES",
      "SEX": "Female",
      "AGE_GROUP": "P5Y--P10Y",
      "value": "12"
    }
  ]
}

That looks much more pleasing to my eye than a MeasureReport. I think
we should leave open the possibility of this simple representation.
ie. not call the new proposal "Json representation of an ADX message"
but something else maybe more explicitly FHIR.

There are some aspects to the preamble of the new proposal which I
would disagree with. First there is a suggestion that a json version
would depend on the existence of a "SDMX-JSON". I think this is not
true - the adx data format is not in fact SDMX, nor would be its json
equivalent. It in fact has more DNA to be discerned from the widely
used but dhis2-internal dxf2 format.

So I need a little persuading to actively support this proposal though
I wouldn't stand in the way of people who want to do it. I would
suggest we do an openHMIS call next Tuesday to discuss but I know
Derek is in Banff. Lets earmark Tuesday 18th. I can modify the wiki
to shift our September call to then.

Cheers
Bob

···

On 4 September 2018 at 13:17, Derek Ritz <derek.ritz@gmail.com> wrote:

Hi all.

Carl Leitner has suggested a new work item be proposed for the upcoming IHE
QRPH work cycle. Information about this proposal can be found, here:
https://www.dropbox.com/s/hprrdxopxz8ybf0/ADX_on_JSON_IHE_Profile_Proposal_Template-Brief.docx?dl=0

The proposal is to develop a FHIR-based profile for doing aggregate data
exchange based on the Measure (https://www.hl7.org/fhir/measure.html) and
MeasureReport (https://www.hl7.org/fhir/measurereport.html) resources. Such
an approach was prototyped during the OpenHIE HacKonnectathon in Arusha, TZ
last month.

The deadline for submissions is only a few weeks away (Sep 21). Please --
can we have a discussion (on this thread) regarding this proposal? Also...
if there is support for it... are folks who would like to participate on the
authoring team?

Thanks and warmest regards,
Derek

--
You received this message because you are subscribed to the Google Groups
"Open HMIS" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to open-hmis+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Bob,

Sounds good for the 18th - note, I’ll be in Seattle, but could do a relative early morning call on my side at 7am Pacific, 10am Eastern. Otherwise I am in an all day work planning meetings.

Also sorry that I had misunderstood the adherence/proximity of ADX to SDMX, and had thought that a SDMX-JSON version would be trivial.

Cheers,
-carl

···

On Sep 7, 2018, at 6:08 AM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:

Hi

We were scheduled to have a call this past Tuesday but, as you may
know, Simon has left us so there has been no one convening the calls.
Otherwise this would have been a good opportunity to discuss the
proposal.

It is really unfortunate I was not at the openHIE meetup in Arusha
where some of this was discussed, but some of you know I have some
misgivings. Besides putting ADX on FHIR (a prospect we discussed back
in Naples last year) as an end in itself I am not convinced what new
problem it is really solving. The adx data format is quite usable as
is. Many (including me) find the sdmx aspect a little grotesque, but
it can also be safely ignored. The data format is fit for purpose and
there are many more sensible ways of exchanging metatadata if need be,
including via CSD/facility-registry and terminology services.

It was always our intention we would do a json ADX flavour eventually,
which to my mind would be a more straightforward literal translation
along the lines of

{
"dataSet": "MALARIA",
"period": "2017-10-01/P1M",
"orgUnit": "TheClinic",
"dataValues": [
   {
     "dataElement": "MALARIA_CASES",
     "SEX": "Male",
     "AGE_GROUP": "P5Y--P10Y",
     "value": "8"
   },
   {
     "dataElement": "MALARIA_CASES",
     "SEX": "Female",
     "AGE_GROUP": "P5Y--P10Y",
     "value": "12"
   }
]
}

That looks much more pleasing to my eye than a MeasureReport. I think
we should leave open the possibility of this simple representation.
ie. not call the new proposal "Json representation of an ADX message"
but something else maybe more explicitly FHIR.

There are some aspects to the preamble of the new proposal which I
would disagree with. First there is a suggestion that a json version
would depend on the existence of a "SDMX-JSON". I think this is not
true - the adx data format is not in fact SDMX, nor would be its json
equivalent. It in fact has more DNA to be discerned from the widely
used but dhis2-internal dxf2 format.

So I need a little persuading to actively support this proposal though
I wouldn't stand in the way of people who want to do it. I would
suggest we do an openHMIS call next Tuesday to discuss but I know
Derek is in Banff. Lets earmark Tuesday 18th. I can modify the wiki
to shift our September call to then.

Cheers
Bob

On 4 September 2018 at 13:17, Derek Ritz <derek.ritz@gmail.com> wrote:

Hi all.

Carl Leitner has suggested a new work item be proposed for the upcoming IHE
QRPH work cycle. Information about this proposal can be found, here:
https://www.dropbox.com/s/hprrdxopxz8ybf0/ADX_on_JSON_IHE_Profile_Proposal_Template-Brief.docx?dl=0

The proposal is to develop a FHIR-based profile for doing aggregate data
exchange based on the Measure (https://www.hl7.org/fhir/measure.html) and
MeasureReport (https://www.hl7.org/fhir/measurereport.html) resources. Such
an approach was prototyped during the OpenHIE HacKonnectathon in Arusha, TZ
last month.

The deadline for submissions is only a few weeks away (Sep 21). Please --
can we have a discussion (on this thread) regarding this proposal? Also...
if there is support for it... are folks who would like to participate on the
authoring team?

Thanks and warmest regards,
Derek

--
You received this message because you are subscribed to the Google Groups
"Open HMIS" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to open-hmis+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Open HMIS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-hmis+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bob,

Let me know if you would like any support for a call on Tuesday, Septemeber 18 @7am Pacific, 10am EDT, 3pm IST and I would be happy to help.

-Jamie

    Hi Bob,
    
    Sounds good for the 18th - note, I’ll be in Seattle, but could do a relative early morning call on my side at 7am Pacific, 10am Eastern. Otherwise I am in an all day work planning meetings.
    
    Also sorry that I had misunderstood the adherence/proximity of ADX to SDMX, and had thought that a SDMX-JSON version would be trivial.
    
    Cheers,
    -carl

···

On 9/7/18, 9:06 AM, "open-hmis@googlegroups.com on behalf of Carl Leitner" <open-hmis@googlegroups.com on behalf of litlfred@gmail.com> wrote:
    
    > On Sep 7, 2018, at 6:08 AM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
    >
    > Hi
    >
    > We were scheduled to have a call this past Tuesday but, as you may
    > know, Simon has left us so there has been no one convening the calls.
    > Otherwise this would have been a good opportunity to discuss the
    > proposal.
    >
    > It is really unfortunate I was not at the openHIE meetup in Arusha
    > where some of this was discussed, but some of you know I have some
    > misgivings. Besides putting ADX on FHIR (a prospect we discussed back
    > in Naples last year) as an end in itself I am not convinced what new
    > problem it is really solving. The adx data format is quite usable as
    > is. Many (including me) find the sdmx aspect a little grotesque, but
    > it can also be safely ignored. The data format is fit for purpose and
    > there are many more sensible ways of exchanging metatadata if need be,
    > including via CSD/facility-registry and terminology services.
    >
    > It was always our intention we would do a json ADX flavour eventually,
    > which to my mind would be a more straightforward literal translation
    > along the lines of
    >
    > {
    > "dataSet": "MALARIA",
    > "period": "2017-10-01/P1M",
    > "orgUnit": "TheClinic",
    > "dataValues": [
    > {
    > "dataElement": "MALARIA_CASES",
    > "SEX": "Male",
    > "AGE_GROUP": "P5Y--P10Y",
    > "value": "8"
    > },
    > {
    > "dataElement": "MALARIA_CASES",
    > "SEX": "Female",
    > "AGE_GROUP": "P5Y--P10Y",
    > "value": "12"
    > }
    > ]
    > }
    >
    > That looks much more pleasing to my eye than a MeasureReport. I think
    > we should leave open the possibility of this simple representation.
    > ie. not call the new proposal "Json representation of an ADX message"
    > but something else maybe more explicitly FHIR.
    >
    > There are some aspects to the preamble of the new proposal which I
    > would disagree with. First there is a suggestion that a json version
    > would depend on the existence of a "SDMX-JSON". I think this is not
    > true - the adx data format is not in fact SDMX, nor would be its json
    > equivalent. It in fact has more DNA to be discerned from the widely
    > used but dhis2-internal dxf2 format.
    >
    > So I need a little persuading to actively support this proposal though
    > I wouldn't stand in the way of people who want to do it. I would
    > suggest we do an openHMIS call next Tuesday to discuss but I know
    > Derek is in Banff. Lets earmark Tuesday 18th. I can modify the wiki
    > to shift our September call to then.
    >
    > Cheers
    > Bob
    >
    >
    >
    > On 4 September 2018 at 13:17, Derek Ritz <derek.ritz@gmail.com> wrote:
    >> Hi all.
    >>
    >> Carl Leitner has suggested a new work item be proposed for the upcoming IHE
    >> QRPH work cycle. Information about this proposal can be found, here:
    >> https://www.dropbox.com/s/hprrdxopxz8ybf0/ADX_on_JSON_IHE_Profile_Proposal_Template-Brief.docx?dl=0
    >>
    >> The proposal is to develop a FHIR-based profile for doing aggregate data
    >> exchange based on the Measure (https://www.hl7.org/fhir/measure.html) and
    >> MeasureReport (https://www.hl7.org/fhir/measurereport.html) resources. Such
    >> an approach was prototyped during the OpenHIE HacKonnectathon in Arusha, TZ
    >> last month.
    >>
    >> The deadline for submissions is only a few weeks away (Sep 21). Please --
    >> can we have a discussion (on this thread) regarding this proposal? Also...
    >> if there is support for it... are folks who would like to participate on the
    >> authoring team?
    >>
    >> Thanks and warmest regards,
    >> Derek
    >>
    >> --
    >> You received this message because you are subscribed to the Google Groups
    >> "Open HMIS" group.
    >> To unsubscribe from this group and stop receiving emails from it, send an
    >> email to open-hmis+unsubscribe@googlegroups.com.
    >> For more options, visit https://groups.google.com/d/optout.
    >
    > --
    > You received this message because you are subscribed to the Google Groups "Open HMIS" group.
    > To unsubscribe from this group and stop receiving emails from it, send an email to open-hmis+unsubscribe@googlegroups.com.
    > For more options, visit https://groups.google.com/d/optout.
    
    --
    You received this message because you are subscribed to the Google Groups "Open HMIS" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to open-hmis+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.