FHIR Chat · c4bb implementation validation · implementers

Stream: implementers

Topic: c4bb implementation validation


view this post on Zulip shaifali (Jun 10 2021 at 11:27):

Hello! We are implementing CARIN's profiles and are creating c4bb EOB resources (Inpatient so far) based on this structure definition > http://hl7.org/fhir/us/carin-bb/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html .
Basically, it's a webservice that responds with this EOB inpatient resource on a get.
We are trying to find a validator for this resource. We have tried the fhir's java validator but it throws errors on the system urls because most of the terminology urls are c4bb and not hl7. We also created our own terminology pages on our server and will be utilizing those but it's the same thing - errors like 'Unknown code' or 'None of the codings match'.
I read about AEGIS Touchstone on one of the topics here and will explore that. Any help or pointers on this is appreciated. Thank you!

view this post on Zulip Lloyd McKenzie (Jun 10 2021 at 14:56):

The validator should be happy so long as you pass in the IG with the -ig parameter.

view this post on Zulip shaifali (Jun 11 2021 at 11:59):

We have the profile in meta/profile. Not many structure-based errors except adjudication but it's angry about most of the system urls. I tested the c4bb's example as well with the validator and it does complain there too, eg. the c4bb's revenue terminology url.

view this post on Zulip Lloyd McKenzie (Jun 11 2021 at 14:34):

Listing the profile isn't enough. You also have to pass the ig to the validator. By default, the validator doesn't know about any implementation guides, only the core spec.

view this post on Zulip shaifali (Jun 15 2021 at 19:12):

@Lloyd McKenzie sorry but what should the ig be for this profile?

view this post on Zulip David Pyke (Jun 15 2021 at 19:34):

http://hl7.org/fhir/us/carin-bb

view this post on Zulip David Pyke (Jun 15 2021 at 19:35):

The IG's id is hl7.fhir.us.carin-bb you can pass that ID through and it should pick up the required dependencies

view this post on Zulip shaifali (Jun 15 2021 at 19:48):

@David Pyke I tried this but it still gives error with terminologies like the subtype, revenue.

I have another question please, should we be making our own IG if we want to use our terminology urls?

view this post on Zulip David Pyke (Jun 15 2021 at 19:55):

It depends on the bindings. For subtype, you can use your own valueset as the binding is Example. item.revenue is a Required binding so you have to use the NUBC codes. Creating your own profile is possible but it won't be compatible with the CARIN IG and you would have to discuss with the receivers of your data that it is your own profile

view this post on Zulip David Pyke (Jun 15 2021 at 19:56):

So your own IG for your own use case is a good idea if you want to handle data your way. If you're trying to follow the CARIN or Blue Button requirements, that won't work

view this post on Zulip shaifali (Jun 15 2021 at 20:01):

David Pyke said:

So your own IG for your own use case is a good idea if you want to handle data your way. If you're trying to follow the CARIN or Blue Button requirements, that won't work

This helps! Thanks a lot!

On the validator side, how can I get it to accept CARIN's terminology bindings?

view this post on Zulip David Pyke (Jun 15 2021 at 20:03):

IF you declare your example to be dependent on the CARIN profile, it should inherit them automatically when you tell the validator to refer to the IG. What is the command line that you're using?

view this post on Zulip shaifali (Jun 15 2021 at 20:19):

java -jar validator_cli.jar c4bbEOBin.json -ig hl7.fhir.us.carin-bb

view this post on Zulip David Pyke (Jun 15 2021 at 20:47):

Is it possible for you to send me the json so I can see what's going on?

view this post on Zulip shaifali (Jun 15 2021 at 20:54):

Yes! Can I send it to you by tomorrow in a private message please?

view this post on Zulip David Pyke (Jun 15 2021 at 20:54):

Yep, no problem


Last updated: Apr 12 2022 at 19:14 UTC