Stream: FHIRcast
Topic: view position/layout - hub.viewId
Bill Wallace (Sep 12 2019 at 19:03):
It would be useful to have an id for which view or area something is being opened in. That allows some information to be transmitted about where something is being opened/updated. My suggestion is hub.viewId and that the recommended values are integers starting at 0, but to allow for other values.
A standard use might be:
imagingstudy.open
viewId: 0
...
to open in the 0/default position, and then for a comparison study:
imagingstudy.open
viewId: 1
to open in the second position.
To allow communication more nuanced information something like:
patient.open
viewId: teachingFile.0
which would say this patient is being opened, but in this case it means as a teaching file, not as a regular view position (could be a relative, or a similar patient etc, application specific, but something they can describe in conformance statements)
Isaac Vetter (Sep 13 2019 at 02:25):
Hey Bill, I'm trying to understand -- practically what would the different views be? I'm ignorantly imaging one view as the main activity (the default position) a second view perhaps as a sidebar activity, running alongside the main activity. Otherwise, I struggling to imagine other views. What would additional views be?
Isaac Vetter (Sep 13 2019 at 02:25):
Your example of a teachingView may be mixing the view or area with the authorization to request context changes.
Bill Wallace (Sep 13 2019 at 16:06):
Hi @Isaac Vetter Other views could be other tabs, for example, suppose one is reviewing a given patient, and a high priority case comes in. Then, a second view might temporarily overlay the previous view (set aside view 1). Then, that one gets closed, and the user returns to the original case.
For a study, imagine displaying an MG, with a relevant CT and a prior MG. The primary view would be study viewId 0, while the CT might be view ID 2 and the MG viewId 1. That becomes even more important as we add things like viewing multiple documents (say the report associated with study 1, and the report associated with study 2 to see what happened in the CT and prior MG).
Last updated: Apr 12 2022 at 19:14 UTC
