Stream: CARIN IG for Blue Button®
Topic: can EoB.supportingInfo be better defined in the IG?
Isaac Vetter (Feb 06 2020 at 23:28):
Hi!
EoB.supportingInfo is a very flexible element. I believe that this IG doesn't provide guidance to implementers on how to limit and use this element. I think that this element needs to be profiled to make it implementable. (related to FHIR-25444 and @Lisa Nelson ).
Further, it looks like CMS BlueButton2 doesn't use this element.
Why should this element be in the HL7 IG? What am I missing?
Josh Mandel (Feb 06 2020 at 23:35):
I agree strongly with this sentiment, and I've raised here in the past as well. I think there are a number of places where we should simply be defining extensions rather than trying to cram information in to be "supporting information" structure.
Isaac Vetter (Feb 06 2020 at 23:43):
Josh - you might be interested in reading my comment on https://jira.hl7.org/browse/FHIR-25444, as well, then. (I'm sure that FM would appreciate your guidance and input).
Josh Mandel (Feb 07 2020 at 16:52):
Thanks, indeed! Just commented on J#25444, in agreement.
Karl M. Davis (Feb 19 2020 at 01:32):
Further, it looks like CMS BlueButton2 doesn't use this element.
I don't have my work laptop handy at the moment, but this sounds untrue. Hmmm...
Karl M. Davis (Feb 19 2020 at 01:40):
Well, GitHub search isn't finding any uses, though I don't really trust it: https://github.com/CMSgov/beneficiary-fhir-data/search?q=*SupportingInfo&unscoped_q=*SupportingInfo
Karl M. Davis (Feb 19 2020 at 01:41):
All that aside, I completely agree: this field always felt like a somewhat silly attempt to meet an imaginary goal of "use less extensions".
Jason Teeple (Jul 30 2020 at 15:56):
@Ryan Howells has the above conversation been taken into consideration? Teams are mapping the EOB profile and supportingInfo is quite vague. Not to mention the definition and requires are identical for each supportingInfo, which is unhelpful for implementation purposes.
Last updated: Apr 12 2022 at 19:14 UTC
