May 2018 Ballot Comment 63 #269
Description
May 2018 Ballot Comment 63
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: Extensions
Type: NEG ❗
In Person Requested? Yes 👤
Existing Wording:
The specification is not prescriptive about support for extensions. However, to support extensions, the specification reserves the name extension and will never define an element with that name
Comment:
I recommend to define extension, making the content optional except for one field: sourceId: URI. This would allow support of extensions from multiple sources. The URL would hold a DNS based identifier for the extension type.
Triage Information
Triage Notes:
Reviewed with Bas
Proposed Disposition: Not Persuasive
Proposed Disposition Comment:
We disagree. See this discussion for our thinking and design thoughts on extensinos: #76.
Additionally, implementers are free to add a field such as sourceId (or any other) given the current extension design.
This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet.