Stream: cds hooks
Topic: docs / Issue #15 Can CDS service discovery flex based upo...
Github Notifications (May 07 2017 at 08:38):
seanmsmith23 commented on Issue #15
The idea of having some communication back and forth about the minimum FHIR resources required definitely has some appeal, but given the complications @kpshek outlines above (differing version support, what if you need specific fields on a specific resource, etc..) I'd say leaving this to an offline process feels right to me.
In practice (as a CDS-service), we would probably put some logic into our Discovery endpoint that can quickly enable/disable services for different clients. Then during our discussions with the client team about getting our CDS-service online we'd naturally be having a conversation about what FHIR resources they support - if the minimum requirements weren't met, we'd go in and disable the service for that client until a future time. That doesn't feel unduly arduous to me.
Maybe this can be revisited further down the line if it's causing big headaches, but in the interest of not making the standard more confusing or challenging to implement I'd vote for staying with a manual/offline process.
Last updated: Apr 12 2022 at 19:14 UTC
