Stream: CARIN BB ExplanationOfBenefit
Topic: Inpatient productOrService data-absent-reason
Fred Harmon (Feb 08 2021 at 19:01):
I'm having a hard time trying to figure out the proper structure for data-absent-reason in the case when I don't have a code for the item:productOrService property. The notes of the IG do state that this can occur in an inpatient setting and that the appropriate thing to do is to include the data-absent-reason extension.
http://build.fhir.org/ig/HL7/carin-bb/StructureDefinition-C4BB-ExplanationOfBenefit-Inpatient-Institutional.html#notes-on-fields
"A CPT / HCPCS code may not be available on an inpatient institutional claim. The cardinality of the HL7 base EOB Resource for item.productOrService is 1..1 if .item is provided. Since .item.revenue is required it means that item.productOrService must be populated. Since the profile is not able to relax the cardinality of the resource, it is recommended payers provide a data absent reason when a CPT / HCPCS code is not available."
I am trying to add the following instead of "productOrService".
"_productOrService": {
"extension": [
{ "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
"valueCode":"unsupported" } ]
I get errors when validating (using https://inferno.healthit.gov/validator/) that "productOrService" is required. Should I not be putting the "_" in front of my property perhaps? Perhaps there is no way to do this without getting a validation error and I don't know that I should just be looking past that particular error in this case.
If we figure this out, I would love if the example in the IG (http://build.fhir.org/ig/HL7/carin-bb/ExplanationOfBenefit-InpatientEOBExample1.json.html) had at least one of the line items updated to show how this is done as it is likely a common scenario for others.
Fred Harmon (Feb 08 2021 at 19:59):
I've found another random example of data-absent-reason someone was using on a Observation resource but it led me to the following solution. This also throw errors in the Inferno validator but I'm beginning to believe the validators don't know how to handle data-absent-reason perhaps.
Here I am adding the extension to the code itself instead of the productOrService which seems more accurate. I'm thinking this seems way more accurate as I'm representing that I don't know the code. Now the validator throws an error about "No code provided" but this is why I'm thinking it won't ever really be able to handle this.
"productOrService": {
"coding": [{
"code": {
"extension": [
{ "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
"valueCode":"unsupported"
} ]
}
}]
}
Last updated: Apr 12 2022 at 19:14 UTC
