Stream: fhircast-github
Topic: fhircast-docs / Issue #75 Supporting proprietary events
Github Notifications (FHIRcast) (Feb 22 2019 at 07:00):
bvdh opened Issue #75
A implementer may choose to use some events that have not (yet) been defined by FHIR Cast.
I suggest that we support these.
Regarding naming, I suggest that we use the same approach as CDS hooks and require that these are named with reverse domain notation (e.g. org.example.patient-transmogrify)
Github Notifications (FHIRcast) (Feb 27 2019 at 22:47):
isaacvetter commented on Issue #75
@bvdh - excellent point, any thoughts on the referenced PR #78 ?
Github Notifications (FHIRcast) (Feb 27 2019 at 22:47):
isaacvetter assigned Issue #75(assigned to isaacvetter)
A implementer may choose to use some events that have not (yet) been defined by FHIR Cast.
I suggest that we support these.
Regarding naming, I suggest that we use the same approach as CDS hooks and require that these are named with reverse domain notation (e.g. org.example.patient-transmogrify)
Github Notifications (FHIRcast) (Mar 01 2019 at 07:17):
No that seems to cover the issue.
Github Notifications (FHIRcast) (Mar 05 2019 at 15:43):
isaacvetter closed Issue #75(assigned to isaacvetter)
A implementer may choose to use some events that have not (yet) been defined by FHIR Cast.
I suggest that we support these.
Regarding naming, I suggest that we use the same approach as CDS hooks and require that these are named with reverse domain notation (e.g. org.example.patient-transmogrify)
Last updated: Apr 12 2022 at 19:14 UTC
