If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.
Interactive meeting - Adobe Connect
We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at http://connect.iu.edu/omrsdf. For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.
Given what is going on around REST development, instead of trying to implement a transactional API it might be more effective to modify the existing resources (e.g. EncounterResource) to support multiple edits
This entails identifying specific desired behaviors, e.g., Being able to edit obs in an existing encounter and submit without having to void them individually.
Ensure common transactions are encapsulated in REST calls.
We agree the REST API should expose high level operations that encapsulate the necessary transactions. For example, Darius confirmed on this call that updating an obs via the REST API _does_ void the existing one and create a new one, returning it. Where we identify missing high level operations, especially commonly needed ones, the REST API should be ammended.
Tickets/wiki pages on this topic should use the "transactional-rest" label to help identify them.
Create a path to facilitate anyone joining the community with ability to understand how things work and the path forward. That is the way REST API is supposed to behave when editing/modifying resources
Create a ticket to facilitate proper behavior with editing encounters (Add a label transactional-rest) - (@Willa)
Audio recording of the call: Listen online or download (available after the meeting)