FHIR Chat · Issue with EligibilityResponse · committers

Stream: committers

Topic: Issue with EligibilityResponse


view this post on Zulip Grahame Grieve (Dec 12 2016 at 12:34):

@Paul Knapp : The EligibilityResponse resource as of FHIR 1.8.0 (i.e. http://hl7.org/fhir/2017Jan/eligibilityresponse.html) still has this problem in the .benefit[x] and .benefitUsed[x] properties. That cmbination is not allowed. I don't know why the build tool doesn't pick it up

view this post on Zulip Paul Knapp (Dec 12 2016 at 12:35):

What is the problem? It isn't a problem when the same appears in the EOB?

view this post on Zulip Grahame Grieve (Dec 12 2016 at 12:41):

it's to make it easier to parse etc - if a field starts with yyyy[x], then nothing else can start with yyyy

view this post on Zulip Grahame Grieve (Dec 12 2016 at 12:42):

so if you see somthing starting with yyyy, it is that field, not maybe another

view this post on Zulip Paul Knapp (Dec 12 2016 at 13:10):

OK then I will need to redo the naming of that structure in the two places it exists (and the examples and the code). Ok, I'll change the first to benefitAllowed[x].

view this post on Zulip Grahame Grieve (Dec 12 2016 at 13:10):

ok. let me know, and I'll fix the build tool to disallow that.

view this post on Zulip Paul Knapp (Dec 12 2016 at 13:11):

or change first to allowed and second to used

view this post on Zulip Paul Knapp (Dec 12 2016 at 13:12):

I only have about an hour tonight, I'll try but may not be complete until tomorrow (which is the middle of most peoples night)

view this post on Zulip Grahame Grieve (Dec 12 2016 at 13:30):

no hurry. it's in the build, which is quiet at the moment

view this post on Zulip Paul Knapp (Dec 12 2016 at 13:47):

I have made all the changes, modified the code and re-deployed the test server, committed the changes. I'll check back in 15 to see that all is good in the build.


Last updated: Apr 12 2022 at 19:14 UTC