Stream: cds hooks/github
Topic: docs / Issue #268 May 2018 Ballot Comment 62
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot opened Issue #268
## May 2018 Ballot Comment 62
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Security and Safety
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
The EHR’s authorization server is responsible for enforcing restrictions on the CDS Services that may be called and the scope of the FHIR resources that may be prefetched or retrieved from the FHIR server. Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR. Pre-registration MUST include registering a CDS client identifier, and agreeing upon the scope of FHIR access that is minimally necessary to provide the clinical decision support required.
Comment:
The registration is out-of-scope, why add a mandatory requirement.## Triage Information
Triage Notes:
Reviewed with BasProposed Disposition: Persuasive
Proposed Disposition Comment:
Change MUST and MUST BE to lowercase (or reword) as this is not a requirement by the spec but just a statement of reality.
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot milestoned Issue #268
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot labeled Issue #268
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot edited Issue #268
## May 2018 Ballot Comment 62
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Security and Safety
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
The EHR’s authorization server is responsible for enforcing restrictions on the CDS Services that may be called and the scope of the FHIR resources that may be prefetched or retrieved from the FHIR server. Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR. Pre-registration MUST include registering a CDS client identifier, and agreeing upon the scope of FHIR access that is minimally necessary to provide the clinical decision support required.
Comment:
The registration is out-of-scope, why add a mandatory requirement.## Triage Information
Triage Notes:
Reviewed with BasProposed Disposition: Persuasive
Proposed Disposition Comment:
Change MUST and MUST BE to lowercase (or reword) as this is not a requirement by the spec but just a statement of reality.
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Github Notifications (May 18 2018 at 09:23):
cds-hooks-bot commented on Issue #268
Proposed Disposition: Persuasive
Proposed Disposition Comment:
Change MUST and MUST BE to lowercase (or reword) as this is not a requirement by the spec but just a statement of reality.
Github Notifications (May 18 2018 at 09:44):
cds-hooks-bot labeled Issue #268
Github Notifications (May 30 2018 at 22:21):
cds-hooks-bot commented on Issue #268
## :telephone_receiver: CDS Working Group Block Vote (5-30-2018)
Meeting notes: http://wiki.hl7.org/index.php?title=File:2018-05-30_CDS_WG_Call_Minutes.docx
Julia Skapik moved the following disposition, seconded by @brynrhodes.
Disposition: Persuasive
Disposition Comment:
Change MUST and MUST BE to lowercase (or reword) as this is not a requirement by the spec but just a statement of reality.:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (Jun 14 2018 at 13:39):
cds-hooks-bot assigned Issue #268
Github Notifications (Aug 09 2018 at 14:22):
kpshek closed Issue #268
Last updated: Apr 12 2022 at 19:14 UTC
