Stream: implementers
Topic: ValueSet RemittanceOutcome in R4B
Lee Surprenant (Dec 08 2021 at 14:10):
In R4, this had 4 allowed values: https://hl7.org/fhir/valueset-remittance-outcome.html
In R4B, the queued code has been removed: https://build.fhir.org/branches/R4B/valueset-remittance-outcome.html
This valueset has a required binding from at least two resource types in the financial module:
- https://hl7.org/fhir/explanationofbenefit-definitions.html#ExplanationOfBenefit.outcome
- https://hl7.org/fhir/claimresponse-definitions.html#ClaimResponse.outcome
I consider that a breaking change because instances that were valid in R4 may not be in R4B.
Was this intentional?
Josh Mandel (Dec 08 2021 at 14:16):
Valid R4 resources should absolutely be valid R4B resources. I hope breaking this wasn't intentional.
Grahame Grieve (Dec 08 2021 at 18:04):
it's worse than that from my pov. Compare the generated code system https://build.fhir.org/branches/R4B/codesystem-remittance-outcome.xml.html with it's source at https://github.com/HL7/fhir/blob/R4B/source/claimresponse/codesystem-remittance-outcome.xml
Grahame Grieve (Dec 08 2021 at 18:27):
that's because there was a rogue definition of RemittanceOutcome hanging around.
Grahame Grieve (Dec 08 2021 at 18:27):
I
Grahame Grieve (Dec 08 2021 at 18:27):
I'll fix
Lee Surprenant (Dec 10 2021 at 22:36):
its sounds like this one is already being working, but just let me know if you'd like me to open a Jira tracker for it
Grahame Grieve (Dec 10 2021 at 23:03):
it's fixed in the source - now all I have to do is get the thing building again
Last updated: Apr 12 2022 at 19:14 UTC
