Stream: methodology
Topic: subject/focus split
Grahame Grieve (Oct 21 2019 at 18:20):
The observation resource splits between subject and focus. I think that this concept applies to other resources too, but it hasn't been discussed.
Here's what I want to do about this:
- for every reference to a participation resource (CareTeam, Device, Group, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson), the definitions must define an applicable role code
- the role code must define what kind of role that this plays, to ensure that the committee has thought about this in a structured fashion
- the role code must be taken from an approved list of codes maintained by MnM
- The v3 RoleCode is a candidate for the set of codes... but I am suspicious of it
Lloyd McKenzie (Oct 21 2019 at 19:22):
I don't understand this solution or how it deals with subject vs. focus. Also, are you wanting role or participation?
Grahame Grieve (Oct 21 2019 at 19:24):
I think I care about both Role code and Participation type
Grahame Grieve (Oct 21 2019 at 19:24):
maybe the second - I'd have to investiage
Grahame Grieve (Oct 21 2019 at 19:26):
the intent of the solution is that committees would have to be explicit about what kind of participation / role this thing is playing in their design, and the code list from which they choose makes them think through the issues that arose in Observation with subject/focus (and other issues)
Lloyd McKenzie (Oct 21 2019 at 20:02):
SUBJ vs. RTGT are participations in v3. Role is always Patient or Specimen, regardless of how you're referencing them.
Lloyd McKenzie (Oct 21 2019 at 20:03):
I'm not a fan of adding a "participation code" every time we reference one of these resources. We do that in a couple of places, generally around performer, but I don't think it makes sense/is necessary as a general case
Grahame Grieve (Oct 21 2019 at 20:07):
I do not mean that we would add it to the content of the resource, but that we will require it to be present in the definitions (as a stated fixed value) if it's not present in the instance
Grahame Grieve (Nov 05 2019 at 03:59):
can we talk about this on MnM today?
Grahame Grieve (Nov 05 2019 at 22:27):
Decision, for now:
- create a task to ask for discussion of focus vs subject on Procedure
- create a task to ask for a discussion of focus vs subject on ServiceRequest
- create a task to ask for clarification about how to ask for a procedure on an implanted device in a patient
Grahame Grieve (Nov 05 2019 at 22:28):
- also: discuss this at the round table + also schedule for mention at the workflow session
Grahame Grieve (Nov 14 2019 at 01:02):
add:
- create a task for clarification of subject/focus on Specimen
Last updated: Apr 12 2022 at 19:14 UTC
