Stream: cds hooks/github
Topic: docs / Issue #256 How are cards rendered? (was May 2018 B...
Github Notifications (Aug 06 2018 at 16:55):
isaacvetter edited Issue #256(assigned to isaacvetter)
## May 2018 Ballot Comment 50
Submitted by @bvdh from Philips Healthcare
Chapter: CDS Services
Section: CDS Service Response - Card Attributes
Type: A-S :bulb:
In Person Requested? Yes :bust_in_silhouette:Existing Wording:
detail OPTIONAL string Optional detailed information to display; if provided MUST BE represented in (GitHub Flavored) Markdown without HTML. (For non-urgent cards, the EHR MAY hide these details until the user clicks a link like "view more details...".)
Comment:
Maybe a separate section on card representation should be added.## Triage Information
Triage Notes:
Reviewed with BasProposed Disposition: Persuasive
Proposed Disposition Comment:
We agree that guidance to developers as to how implementers renders cards would be good. However, this is outside of the specification.
_This issue was imported by @cds-hooks-bot from the consolidated CDS Hooks May 2018 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
