Stream: implementers
Topic: AllergyIntolerance.verificationStatus is failing Rule ait-2
Sridhar Vellore (Jul 17 2019 at 10:35):
I was validating an R4 Fhir JSON listed below and the validation is failing with the following error.
"clinicalStatus": { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical", "code": "active", "display": "Active" }] }, "verificationStatus": { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification", "code": "confirmed", "display": "Confirmed" }] },
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "[error] in /*:AllergyIntolerance[namespace-uri()='http://hl7.org/fhir'][1] @ AllergyIntolerance ait-2: AllergyIntolerance.clinicalStatus SHALL NOT be present if verification Status is entered-in-error Test=f:verificationStatus/@value!='entered-in-error' or not(exists(f:clinicalStatus))",
"location": [
"AllergyIntolerance"
]
},
I have tried changing code of verification status to all other possible values but still it keeps giving the above error, How can I address this issue?
Lloyd McKenzie (Jul 17 2019 at 13:58):
Looks like the invariants on Condition and AllergyIntolerance are broken since they were changed to CodeableConcept. Can you please submit a change request?
Sridhar Vellore (Jul 23 2019 at 11:33):
Where can I submit the change request?
Lloyd McKenzie (Jul 23 2019 at 13:12):
At the bottom of any page in the specification there's a "propose a change" link. There's a one-time registration process, after which you can submit proposed changes at will. (@Grahame Grieve for your attention as a potential R4 patch issue)
Eric Haas (Jul 23 2019 at 16:04):
I already beat you to it. Is on the agenda for Thursday
Grahame Grieve (Jul 26 2019 at 11:00):
is there a task labelled for R4? @Lloyd McKenzie we can't just tag me here as a way for tracking R4 issues.
Lloyd McKenzie (Jul 26 2019 at 14:46):
I was tagging you because it was new, there wasn't yet a Task and I thought you'd care. The OP doesn't look like they're going to submit the issue, so I have (and auto-approved it as a typo). GF#23008
Michelle (Moseman) Miller (Aug 05 2019 at 19:42):
@Lloyd McKenzie How is your new tracker (GF#23008) different from the trackers that Eric already logged (GF#22986 and GF#22985)? I had the other two trackers logged with the target release = R4.
Sridhar Vellore (Oct 03 2019 at 13:53):
Anybody knows if this is fixed, if yes which version?
Lloyd McKenzie (Oct 03 2019 at 14:26):
This fix is part of the draft technical correction of R4. It should be published by end of month
Last updated: Apr 12 2022 at 19:14 UTC