Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
CDS Hooks (FHIR)
-
1.0
-
Clinical Decision Support
-
(NA)
-
-
Dennis Patterson/Peter Muir: 23-0-0
-
Clarification
-
Non-substantive
Description
again there seems to be ambiguity here between the CDS Service client and the Oauth server. Creating a token is exclusively done by the Oauth server which is a separate entity from the CDS client --and if there is an assumption that the client and the OAuth server are the same entity it should be explicily clarified earlier on.
Existing Wording:
The CDS Client remains in control of creating an access token that is associated with the specific CDS Service, user, and context of the invocation.
Proposed Wording:
The CDS Client remains in control of obtaining an access token that is associated with the specific CDS Service, user, and context of the invocation\.
Attachments
Issue Links
- is duplicated by
-
FHIR-28787 Clarify ambiguity between CDS client and OAuth server
- Duplicate
- is voted on by
-
BALLOT-13420 Negative - Vannak Kann : 2020-Sep-HL7 XPARADIGM CDS HOOKS R1 STU
- Closed