Stream: implementers
Topic: none human condition.asserter
Jim Kreth (Jan 24 2017 at 22:07):
We're implementing the Condition service. We will have an expert system of sorts that we want to be able to create a Condition for a given patient (base on analysis of medical record, test results, lab results, etc.). Has anyone dealt with AI or expert system references as the "Condition.asserter"? This is not a diagnosis, just a problem added as a problem-list-item. We'll place the rule-id from our rule engine in the Condition.evidence.This is DSTU2. Recommendations more than welcome.
Ewout Kramer (Jan 30 2017 at 15:01):
@Bryn Rhodes ?
Bryn Rhodes (Jan 30 2017 at 16:55):
The asserter element in Condition (for DSTU2 and STU3) references a Patient or Practitioner (or RelatedPerson in STU3), so would not provide a way to communicate that a device asserted the condition. Within GuidanceResponse in STU3, we have a performer element that is a reference to a Device, which provides a way to capture the system returning the guidance. So one way to capture that resulting information would be to use a Provenance resource referencing the Condition and capture the device that way using the agent element with role set to performer and the whoReference set to the Device resource.
Bryn Rhodes (Jan 30 2017 at 16:56):
(actor element in the DSTU2 Provenance resource).
Jim Kreth (Jan 31 2017 at 19:08):
@Bryn Rhodes Thanks, that gives me some guidance and a thread to research some more.
Last updated: Apr 12 2022 at 19:14 UTC
