Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
US Da Vinci DTR (FHIR)
-
1.0.0 [deprecated]
-
Clinical Decision Support
-
Use Cases and Overview
-
-
Bob Dieterle / Jeff Brown : 12-0-2
-
Clarification
-
Non-substantive
Description
There are a whole bunch of actors here, but they're not well defined, they're not all system actors and they're not well defined.
There are only 4 system actors we care about in DTR:
- Light DTR EHRs - EHR systems which leverage a SMART app to manage data capture and rules execution, but which must be able to launch the SMART app, respond to app queries, and store the final documentation results
- Full DTR EHRs - EHR systems which manage DTR data capture and execution directly and also allow the rules to access other data and store final documentation results
- DTR Smart Apps - SMART on FHIR applications that take context from an EHR, retrieve questionnaires and rule sets from a DTR Payer server, render the Questionnaires and capture data, and store the results on payer and/or EHR systems
- DTR Payer Servers - respond to operations requesting Questionnaires, serve as a temporary repository for in-progress QuestionnaireResponses, and (optionally) help in the processing of adaptive questionnaires
We don't care about payers. We don't care about provider organizations. There are two different types of EHR systems and we need to distinguish them. Also, we need to describe the systems in terms of their behavior and functionality. This information also belongs more on the home page - which is where readers need to see "what types of systems need to care about this IG?" before they've needed to wade through a whole bunch of documentation.
Please refactor the list of actors as described and move it to the home page.
Attachments
Issue Links
- mentioned in
-
Page Loading...