Stream: implementers
Topic: Infection status mapping
Vijay Thangavelu (Aug 16 2017 at 15:48):
All,
We are trying map Infections to fhir resource and we found "Condition" as a an appropriate resource.
One of the use cases to complete or resolve an infection is to draw blood culture and review the results, due to that business decided to have one custom status for the Infection as "Culture reviewed".
Our clarification is, the Condition resource status attributes currently are not extensible (both clinicalStatus and verificationStatus).
I am not sure if its a valid request to make the condition's status extensible.
Is there any approach to handle this scenario?
We can document the culture results as Observation but Infection status is the only limitation here.
please help me if I am missing something here.
Thanks,
Vijay
Stefan Lang (Aug 16 2017 at 16:31):
Does Culture reviewing make the difference between a verificationStatus of "provisional" (before review) and "confirmed" or "refuted" (after the review)?
If not, in which part of the process would a status of "Culture reviewed" be valid and what is the difference to the standard codes defined for verificationStatus?
Lloyd McKenzie (Aug 16 2017 at 17:50):
Culture reviewed isn't really a status of the condition. It's more a status of the workflow associated with the order. So the typical place you'd see "culture reviewed" is in the Task.businessStatus of the Task that's tracking fulfillment of the order. The Condition would presumably be "provisional" or "differential" before the culture was reviewed and "confirmed" after.
Vijay Thangavelu (Aug 16 2017 at 17:53):
Thanks Stefan/Lloyd. It really helps.
Last updated: Apr 12 2022 at 19:14 UTC
