Stream: implementers
Topic: UserSession
Grahame Grieve (Nov 16 2017 at 02:06):
@Bryn Rhodes : feedback on UserSession:
- let's just change identifier to 0..1 and see what happens
- I don't follow how a session can have one status, with a source.
- I don't follow workstation as a CodeableConcept. I don't know where else we've misused a code for something like this. Let's just change it now
- let's fix value to value[x] now
Grahame Grieve (Nov 16 2017 at 02:06):
focus remains very confusing for me; it blurs the boundary of live vs stored in a way we haven't seen on any other resource
Bryn Rhodes (Nov 16 2017 at 08:20):
Yeah, I'm not clear on status either, I suggested it be defined just as status and source as top-level elements. @Isaac Vetter any thoughts?
Grahame Grieve (Nov 16 2017 at 08:29):
well there's 2 different issues - why does status have a source? and if it has a source, does that imply that different sources can have different statuses? and why is there a backbone element - but there are cases where we do that just for logical grouping
Bryn Rhodes (Nov 16 2017 at 08:30):
I actually really liked focus, and we've been talking about adding focus as a general feature to knowledge resources (as a type element at the definition level) because it lets you talk about what the artifact is "about" (e.g. a measure's focus is implicitly Patient now, but we'd like to be able to say it's Organization for structure measures).
Bryn Rhodes (Nov 16 2017 at 08:32):
On status having a source, from the comments in the specs I was working from, it's a way to prevent looping in a bi-directional sync, but that implies it's the source of the UserSession information, not the source of the status, so the grouping doesn't really make sense.
Grahame Grieve (Nov 16 2017 at 08:33):
well, the focus here is different to the focus you'd have on knowledge resources
Last updated: Apr 12 2022 at 19:14 UTC
