Stream: fhircast-github
Topic: fhircast-docs / Issue #155 May 2019 Ballot Comment: Updat...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot opened Issue #155
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot labeled Issue #155
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot edited Issue #155
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 22:50):
isaacvetter commented on Issue #155
During conversation at the Montreal, May 2019 working group meeting, @RicardoQuintano, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to:
@bvdh, we really are looking at this type of idea, a specific example is #250
Proposed Resolution: Not persuasive. This is a great idea, just outside of 1.0 scope.
Github Notifications (FHIRcast) (May 08 2019 at 15:13):
NiklasSvenzen labeled Issue #155
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 02:26):
isaacvetter labeled Issue #155:
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 05 2019 at 14:15):
wmaethner unlabeled Issue #155:
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 27 2019 at 14:32):
isaacvetter commented on Issue #155:
## :telephone_receiver: II Working Group Vote (6-27-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Martin Bellehumeur moved the following disposition, seconded by @NiklasSvenzen
Disposition: Not Persuasive with Mod
Disposition Comment: We will move the event catalog out of the specification, but define a syntax for events based upon FHIR resources and actions. Current proposal may look like [<fhir resource>].[<action>], e.g.:Patient.open.:+1: For: 8
:expressionless: Abstain: 1
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jun 27 2019 at 14:32):
isaacvetter labeled Issue #155:
## May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:43):
wmaethner closed Issue #155:
May 2019 Ballot Comment: Update the context with FHIR resources
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Event Catalog
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-S EnhancementSummary: Update the context with FHIR resources
Comment: Issue/comment imported from https://github.com/HL7/fhircast-docs/issues/72
"An application that is connected to a FHIR Cast session can access the FHIR repository, typically this access is read only. So far as I understand the EMR gathers all changes to the repo in its "context", based on changes in this context the CDS Hooks events are send.
Based on this model, an application should be able to suggest changes to the context. This could be done using the FHIR Cast spec.
I propose that we add a new event: fhir-change
Event-name: fhir-change
Context:
operation: create-update-delete
resouce: FHIR resource
The list of resource updates will be included in the result of the rest interface."
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
