2016-03-07 PA Call Minutes
Contents
Patient Administration Call
Meeting Information
| PA Work Group Meeting
Minutes |
Date: Monday
March 07, 2016 | ||
| Facilitator | Irma Jongeneel | Scribe | Alex de Leon |
| Attendee | Name | Affiliation | |
| X | Irma Jongeneel | HL7 The Netherlands | |
| X | Brian Postlethwaite | Health Connex, Australia | |
| X | Alex de Leon | Kaiser Permanente, USA | |
| X | Russell McDonell | HL7 Australia | |
| X | Sam Fischer | EPIC, USA | |
Agenda
Agenda Topics
- v2.9 update
- PSS Negation
- FHIR Tracker Items
Supporting Documents
Minutes
v2.9 Update
Before moving into the FHIR tracker items, Irma noted that the ODH Elements PSS has been moved to an "offline" discussion to be submitted to the PA Listserve as suggested by Alex. She then asked Alex to update the WG on the action items around the v2 (2.9) action items from last week and his attendance to the Publishing WG meeting on 3/1/2016.
Action Item#1 - Follow up with Ted and Wendy who might be on the Publishing call about the HTA (HL7 Terminology Authority) referenced items needed for the "cleanup" of the tables referenced in Chapter 3 of v2.x. Ted and Wendy were not on the call. Alex confirmed that it is vocabulary in the form of Ted and/or Wendy that need to follow up with the THA for resolution.
Action Item#2 - We should communicate that we have no changes for Chapter 3 (Patient Administration), however, since we are the stewards of other v2 content, we need to clarify whether we need to edit chapter 10 (Scheduling) and/or chapter 15 (Personnel Management). Alex confirmed with Publishing that we only have to edit Chapter 3.
Action Item#3 - Ask if we can postpone the vote for this Monday (today). The Publishing WG agreed that this could wait for today. Alex suggested that we vote right away.
Alex moves to approve the PSS for V2.9 work to be done. The Brian seconded.
Discussion: None
Vote: 4/0/0
Negation PSS
The WG then moved on to discuss the PSS around how to express negation.
Brian moves to limit our involvement into the as “interested party”, Alex seconds.
Discussion: None
Vote: 4/0/0
FHIR Tracker Items
FHIR Tracker Item# 8983
You can access the "Account" resource at this page: http://hl7.org/fhir/DSTU2/account.html
But this resource is not listed here: http://hl7.org/fhir/DSTU2/resourcelist.html
Is this a "real" resource in DSTU2? Should it be listed with the others on the resource page?
Brian moves to include the Account resource into the resource list. Russell seconds.
Discussion: None
Vote: 4/0/0
FHIR Tracker Item# 9270 - The slot resource should be able to specify multiple type values
The Slot should be able to provide a list of types that may be booked into the slot (which may be a subset, or superset of the schedule), not just a singular value.
This is then more consistent with the definition of the schedule.
This is still confusing people until we settle on the "breakup" of the type property into the 3 fields as discussed in Orlando. Better to get that settled before deciding on this change.
(Reminder: 3 fields were service category, service type and appointment type)
Defer to conversation about Appointment Types
9452 - add appointment-reference(encounter) standard extension
Add/document a standard extension to Appointment which references the Encounter act. In cases where an encounter contains/groups/is comprised of/fulfills multiple appointments. That's a fairly typical use case if the encounter is e.g. an outpatient encounter with a hospital.
The WG discussed this at length. Essentially there are 2 parts to this tracker 1) there is already a reference from Encounter to Appointment that it fulfills and 2) in cases where an encounter contains/groups/is comprised of/fulfills multiple appointments.
Please see tracker item for full details of the discussion.
The result is that more clarity is needed from the tracker item.
9623 - Can not associate telecom information with a particular address in the practitioner resource
The address and telecom information at the resource level are not associated with each other. Therefore it's impossible to determine which contactPoint to use with a specific address.
Consider someone trying to call that practioners home phone, or trying to fax that practitioner a document. Both are location specific contact information. When a provider has more than one address, it will be impossible to associate a specific contact point to a specific address.
Note: this is specific to the non-work related elements (see tracker #9621). There is a seperate tracker for the same conceptual issue, but in the practitionerRole backbone element. That's tracker #9622
This is related to tracker item 9244. Telecom will be on practitionerRole as well so the practitioner can be contacted by the role. Identifiers and telecom are included in practitionerRole since Orlando.
Since this is covered in the previous tracker item, this marked as resolved.
Brian moved to Russell seconded, Persuasive with Mod.
Pending:
FHIR Tracker Item # 9594 Can PatientRelationshipType be relaxed to include values used in My Health Record
relationship attribute of RelatedPerson resource is currently constrained to PatientRelationshipType – can it be relaxed or opened to include the following values that are used in the My Health Record? relationship attribute of RelatedPerson resource is currently constrained to PatientRelationshipType – can it be relaxed or opened to include the following values that are used in the My Health Record?
- Full Access Nominated Representative
- Authorized Representative
- Legally Appointed Authorized Representative
- Parent
- Guardian
- Nominated Representative
- Self
- Under 18 - Parental Responsibility
Meeting Outcomes
|
|
Next Meeting/Preliminary Agenda Items
|
Return to PA Main Page © 2016 Health Level Seven® International. All rights reserved.
