| PA Work Group Conference Call
Minutes
Phone Number: +1 770-657-9270
Participant Passcode: 986210
Go to Meeting | GoToMeeting
Meeting Information
| PA Work Group Conference Call
Minutes
Phone Number: +1 770-657-9270
Participant Passcode: 986210
Go to [ https://global.gotomeeting.com/join/311685429%7C GoToMeeting]
|
Date: Tuesday, June 28, 2016
Time: 12:00 PM (US Pacific Time, GMT -7)
Quorum Met (Chair+2, Yes/No)? Yes
|
| Facilitator
|
Irma Jongeneel
|
Scribe
|
Brian Postlethwaite
|
|
|
| Attendee
|
Name
|
Affiliation
|
| X
|
Irma Jongeneel
|
HL7 The Netherlands
|
| X
|
Brian Postlethwaite
|
Health Connex, Australia
|
| X
|
Cooper Thompson
|
EPIC, USA
|
| X
|
Kevin Paprocki
|
EPIC, USA
|
| X
|
Rim Cothren
|
CAHAI, USA
|
| X
|
Line A Saele
|
Nasjonal IKT HF, Norway
|
| X
|
Eric Heflin
|
Sequoia Project/THSA
|
Agenda
Agenda Topics
- Tracker Items
- Practioner Role 10 min
Supporting Documents
Minutes
9193 Provide a way to a diagnosis in the context of encounter
Group: These exist, no change, check notes in tracker.
7881 Add Encounter coverage
Group: Reference added, Brian Postlethwaite/Line Saele: 6-0-0
Group: The reference from Account to Coverage needs to be completed as part of the Coverage review cleanup/follow-up.
7964 Update the type of Priority in Appointment?
Group: This was previously suggested as standard extension, however haven’t had any further feedback.
PractitonerRole Discussion
PractitionerRole domain Resource
+ security for updates
+ privacy
+ distributing resources
+ searching
+ reduced versioning (potentially)
+ referencing externally/contained
+ historical roles don’t clutter main resource (size concerns)
- additional resources required
- more complex, no simple way for querying who a practitioner record “belongs” to, have to use chained search parameters.
e.g. Give me a practitioner with the Identifier, and this Role (from the pracRole)
This type of query is currently not possible as the reference goes from pracRole to prac, and chained search params only follow the reference forward, not backward. The future _has search technique should cover it. Chattiness of the interfaces, potentially reverse the direction of the link from org to prac role.
- leaves the base practitioner without organization on it
- searches require chaining, and _include/_revinclude from servers (and _has if that happens)
PractitionerRole backbone
+ simpler model
+/- resources that reference need to include role also (note – usually do anyway)
- size of resource when history of roles increases
- searching for roles requires client side filtering (of roles)
Changes that would be required for PractitionerRole domain promotion
Don’t believe that we would change ANY of the references from practitioner to role. All the resources that I checked either didn’t care about the role, or already specified which was used (which is better, as don’t want changes to the PracRole to effect the recording of other resources.
Schedule/Slot Availability however is still a potential issue.
Using Linkage resource for cloning copies of Endpoints from directories.
Also consider the thoughts on Person + extras = Practitioner.
Brian to circulate the notes on Argonaut
Meeting Outcomes
- Brian to circulate the notes on Argonaut
- Brian to ask Paul Knapp about the changes to coverage etc as agreed in Montreal
|
Next Meeting/Preliminary Agenda Items
- Next telecom meeting: 07-05-2016
|
Navigation
Return to PA Main Page
© 2016 Health Level Seven® International. All rights reserved.
|
