Stream: implementers
Topic: CDSS
Nadine Adler (May 12 2020 at 07:16):
Hi folks :)
I'm not sure if this is the right place for my questions, but I'll ask them anyway.
1) Is a standardization for the communication between CDSS and other health software foreseeable?
2) Are basic profiles already available for communication between CDSS and other health software?
3) Which FHIR resources could be established for communication between CDSS and other health software?
Examples: GuidanceResponse, Parameters, CommunicationRequest
4) How can API-specific metadata or other non-FHIR data be exchanged? Can the "pure" FHIR object be embedded here as a JSON subobject?
Example:
{
"other": {...}
"fhir": {...}
}
5) How can a CDSS specify required/optional data (patient master data, diagnoses, laboratory values...) in a structured way so that a client knows pre-request which data is required?
Grateful for any help
Have a nice day! :pray:
Michele Mottini (May 12 2020 at 13:38):
What is CDSS?
Nadine Adler (May 12 2020 at 13:41):
Clinical Decision Support System. In FHIR it's defined as Clinical Decision Support Services
Mareike Przysucha (May 12 2020 at 13:41):
I'd presume "clinical decision support system(s)"
Michele Mottini (May 12 2020 at 13:43):
That's CDS Hooks you need to look at then
Vassil Peytchev (May 12 2020 at 13:44):
#cds hooks stream
CDS Hooks specification
Nadine Adler (May 12 2020 at 13:48):
Thank you guys, I will check it
Last updated: Apr 12 2022 at 19:14 UTC
