FHIR Chat · RiskAssessment Resource · cds hooks

Stream: cds hooks

Topic: RiskAssessment Resource


view this post on Zulip Asim (Mar 14 2019 at 14:54):

All, WOuld be great to get a bit of clarity on the use of the RiskAssessment Resource. Would it be OK to use this for the outcome of Early Warning Score (EWS) algorithms or cart-cardiac-arrest-risk-triage-score? How about using it for Apgar score?

view this post on Zulip Bryn Rhodes (Mar 14 2019 at 18:26):

Yes, I think those would both be reasonable uses of the RiskAssessment resource. One of the examples in the spec is a Cardiac Risk score: http://build.fhir.org/riskassessment-example-cardiac.html

view this post on Zulip Asim (Mar 18 2019 at 15:51):

Thanks Bryn, so do you see the output of these algorithms as "risk" or "score"? in the later case the "score" needs to be mapped to the assoicated "risk", thoughts?

view this post on Zulip Bryn Rhodes (Mar 18 2019 at 16:00):

The score can be represented as an Observation that the RiskAssessment.basis references

view this post on Zulip Asim (Mar 18 2019 at 16:07):

OK so if "score" then it is an observation, however when interpretted and mapped to "risk" then the appropriate resource to use would be "RiskAssessment"

view this post on Zulip Chris Moesel (Mar 19 2019 at 17:44):

This discussion is right on, but you should also consider how and where this is going to be used. RiskAssessment is at maturity level 1, and as far as I'm aware, is not supported (yet) by any of the major EHR vendors. So... if you design a solution around RiskAssessment, and you need to exchange it with another FHIR server -- you might want to make sure that server supports it before fully investing in that solution.

view this post on Zulip Chris Moesel (Mar 19 2019 at 17:46):

That said, my experience is that some of the major EHR vendors won't support the score in an Observation either -- as they might only support the Argonaut/USCore categories of Observations -- for lab results, vitals, and smoking history.

view this post on Zulip Asim (Mar 20 2019 at 08:23):

Thanks Chris, those are indeed very important items to take into considerations but this also points to the need for further clarity on the use of such resources. let's hope the EHR vendors would use what is right per standard!!!


Last updated: Apr 12 2022 at 19:14 UTC