Granularity of DecisionSupportServiceModule - 2016-09 cqf #156

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Quality Information Framework (CQIF) [deprecated] (FHIR)
    • DSTU2
    • Clinical Decision Support
    • Clinical Reasoning Module [deprecated]
    • 14.0.5
    • Hide

      Agreed, we have defined a ServiceDefinition resource to provide better support for the separation between the module content and the module invocation syntax.

      Show
      Agreed, we have defined a ServiceDefinition resource to provide better support for the separation between the module content and the module invocation syntax.
    • Bryn Rhodes/Howard Strasberg: 6-0-0
    • Enhancement
    • Non-compatible

      Existing Wording: The use of FHIR operations as the protocol for defining artifact evaluation requests and responses. In particular, the ability to bundle multiple requests into a single operation, as well as the use of a generic FHIR operation for any service module evaluation, versus defining an evaluation specific to a given knowledge artifact.

      Comment:

      I think the rule of thumb should be that we should perhaps have at most dozens or hundreds of operations to cover 90-95% of CDS use cases, vs. thousands or tens of thousands. This would imply that the re-use of operational structures should happen to at least some extent. Also, the ability to minimize processing time, such as through bundling, is critically important and must be a priority for the specification to support. In any case, we should make sure the proposed way forward is feasible for scalable, high-performance use.

      Summary:

      Granularity of DecisionSupportServiceModule

            Assignee:
            Unassigned
            Reporter:
            Kensaku Kawamoto
            Kensaku Kawamoto
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: