FHIR Chat · EOB.diagnosis · CARIN IG for Blue Button®

Stream: CARIN IG for Blue Button®

Topic: EOB.diagnosis


view this post on Zulip Daniel Venton (Dec 03 2020 at 14:18):

The IG for inpatient/outpatient/professional are all similar to this:
... diagnosis S 1..* BackboneElement Pertinent diagnosis information
.... diagnosis[x] S 1..1 CodeableConcept Nature of illness or problem
Binding: Diagnosis Codes - International Classification of Diseases, Clinical Modification (ICD-9-CM, ICD-10-CM) (required)
.... type S 1..1 CodeableConcept Timing or nature of the diagnosis
Binding: C4BB Claim Professional And Non Clinician Diagnosis Type (required)

Of interest is the .diagnosis[x] defined as a CodeableConcept, does that mean that property name is just .diagnosis or is it supposed to be .diagnosisCodeableConcept? It appears that the base EOB says:
... diagnosis[x] 1..1 Nature of illness or problem
Binding: ICD-10Codes (example): ICD10 Diagnostic codes.

..... diagnosisCodeableConcept CodeableConcept
..... diagnosisReference Reference(Condition)

thus .diagnosisCodeableConcept wins, but since the specific cases narrow to only one possibility, they should state the singular possiblity instead of the [x].

view this post on Zulip Josh Lamb (Dec 03 2020 at 18:11):

The propertyName will contain the datatype in addition to the element name. So in your case, if you are expressing a diagnosis[typeof(x)] where the type is codableconcept you would express this as diagnosisCodeableConcept. The examples section of the IG includes an example of this.

"diagnosisCodeableConcept": {
"coding": [
{
"system": "http://hl7.org/fhir/sid/icd-10-cm",
"code": "somecode"
}
]
},

view this post on Zulip Daniel Venton (Dec 03 2020 at 20:35):

I understand that, but if the profile constrains the [x] down to a single concrete, shouldn't profile state the concrete (CodeableConcept) instead of [x]?


Last updated: Apr 12 2022 at 19:14 UTC