FHIR Chat · docs / Issue #335 May 2018 Ballot Comment 129 · cds hooks/github

Stream: cds hooks/github

Topic: docs / Issue #335 May 2018 Ballot Comment 129


view this post on Zulip Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot opened Issue #335

## May 2018 Ballot Comment 129

Submitted by @kensaku-kawamoto on behalf of @gdelfiol from University of Utah

Chapter:
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

Hook creators MAY choose to name their hook with a URI (e.g. https://example.org/hooks/patient-transmogrify) if the hook is specific to an organization.

Proposed Wording:

Hook creators SHALL choose to name their hook with a URI (e.g. https://example.org/hooks/patient-transmogrify) if the hook is specific to an organization.

Comment:
There needs to be a mechanism to ensure that Hook names are globally unique.

## :de: Köln May 2018 Working Group Vote

@bvdh moved the following disposition, seconded by @isaacvetter.

Disposition: Persuasive with Mod
Disposition Comment:
We agree in making this a SHALL and also switching from URIs to reverse domain notation. For example: com.example.patient-transmogrify instead of https://example.org/hooks/patient-transmogrify

We will clarify that this does not apply to hooks in a future standard hook catalog

:+1: For: 10
:expressionless: Abstain: 1
:-1: Against: 0

:tada: The motion passed! :tada:


_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._

view this post on Zulip Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot milestoned Issue #335

view this post on Zulip Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot labeled Issue #335

view this post on Zulip Github Notifications (May 16 2018 at 23:03):

cds-hooks-bot edited Issue #335

## May 2018 Ballot Comment 129

Submitted by @kensaku-kawamoto on behalf of @gdelfiol from University of Utah

Chapter:
Section: https://cds-hooks.org/hooks/
Type: NEG :exclamation:
In Person Requested? Yes :bust_in_silhouette:

Existing Wording:

Hook creators MAY choose to name their hook with a URI (e.g. https://example.org/hooks/patient-transmogrify) if the hook is specific to an organization.

Proposed Wording:

Hook creators SHALL choose to name their hook with a URI (e.g. https://example.org/hooks/patient-transmogrify) if the hook is specific to an organization.

Comment:
There needs to be a mechanism to ensure that Hook names are globally unique.

## :de: Köln May 2018 Working Group Vote

@bvdh moved the following disposition, seconded by @isaacvetter.

Disposition: Persuasive with Mod
Disposition Comment:
We agree in making this a SHALL and also switching from URIs to reverse domain notation. For example: com.example.patient-transmogrify instead of https://example.org/hooks/patient-transmogrify

We will clarify that this does not apply to hooks in a future standard hook catalog

:+1: For: 10
:expressionless: Abstain: 1
:-1: Against: 0

:tada: The motion passed! :tada:


_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._

view this post on Zulip Github Notifications (Jun 14 2018 at 13:44):

cds-hooks-bot assigned Issue #335

view this post on Zulip Github Notifications (Jul 30 2018 at 17:47):

isaacvetter labeled Issue #335

view this post on Zulip Github Notifications (Aug 01 2018 at 21:47):

kpshek closed Issue #335


Last updated: Apr 12 2022 at 19:14 UTC