Stream: cds hooks/github
Topic: docs / Issue #266 May 2018 Ballot Comment 60
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot opened Issue #266
## May 2018 Ballot Comment 60
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Security and Safety
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Comment:
This section makes a security infrastructure mandatory. In the other parts of the specification this optional. I think it is not up to HL7 to require security as other deployments can also be supported.
I recommend to specify the security similar as indicated in this section, and labeling each section as a SHOULD requirement.## Triage Information
Triage Notes:
Reviewed with BasProposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
This line:"Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR"
We need to clarify that this is only the case if the fhirAuthorization object is present in the request. CDS Services that do not call the FHIR server do not need to be pre-registered with the AS.
_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 #266
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot labeled Issue #266
Github Notifications (May 16 2018 at 22:59):
cds-hooks-bot edited Issue #266
## May 2018 Ballot Comment 60
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Security and Safety
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:Comment:
This section makes a security infrastructure mandatory. In the other parts of the specification this optional. I think it is not up to HL7 to require security as other deployments can also be supported.
I recommend to specify the security similar as indicated in this section, and labeling each section as a SHOULD requirement.## Triage Information
Triage Notes:
Reviewed with BasProposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
This line:"Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR"
We need to clarify that this is only the case if the fhirAuthorization object is present in the request. CDS Services that do not call the FHIR server do not need to be pre-registered with the AS.
_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 #266
Proposed Disposition: Persuasive with Mod
Proposed Disposition Comment:
This line:"Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR"
We need to clarify that this is only the case if the fhirAuthorization object is present in the request. CDS Services that do not call the FHIR server do not need to be pre-registered with the AS.
Github Notifications (May 18 2018 at 09:44):
cds-hooks-bot labeled Issue #266
Github Notifications (May 30 2018 at 22:21):
cds-hooks-bot commented on Issue #266
## :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 with Mod
Disposition Comment:
This line:"Therefore, all CDS Services to be called from within an EHR system MUST BE pre-registered with the authorization server of that EHR"
We need to clarify that this is only the case if the fhirAuthorization object is present in the request. CDS Services that do not call the FHIR server do not need to be pre-registered with the AS.
:+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 #266
Github Notifications (Dec 10 2018 at 17:22):
kpshek closed Issue #266
Last updated: Apr 12 2022 at 19:14 UTC