2016-11-15 PA Call Minutes
Patient Administration Call
|PA Work Group Conference Call
On today’s call we addressed the following tracker items:
12135 valueset-location-physical-type code "bd" should be described as "bedplace" rather than "bed" (Simone Heckmann) for discussion. This is an example valueset, but would suggest that we update this anyway. Suggested new text: "A space that is allocated for sleeping/laying on. This is not the physical bed/trolley that may be moved about, but the space it may occupy." Persuasive: Simone Heckmann/Cooper Thompson: 2-0-0
12225 Fix Patient.maritalStatus (Grahame Grieve) recommend that we approve this change Persuasive: Simone Heckmann/Cooper Thompson: 2-0-0
10762 Wrong system used in practitioner example files (Günter Zöchbauer) recommend that we approve this change This may need to be revisited as the practitioner.role is split out into the other resource. (no decision made)
6957 2015May core #22 - Change team member cardinalities (Emma Jones) Believe this has now been addressed by the new CareTeam resource, so I believe it’s been addressed. Persuasive with mod: Simone Heckmann/Cooper Thompson: 2-0-0 (this was already implemented with the change to the new CareTeam resource reference)
10578 Add an extension for primary diagnosis in the context of EpisodeOfCare (Aleksandra Pavlyshina) recommend that we approve this change: Add the extension as described to the EpisodeOfCare.condition element for the priority of the diagnosis. Discussion: Given that the Encounter is to be changed to make this a part of the resource and not an extension, we should consider making the same change in EpisodeofCare. Also noted that the proposed change on encounter (10544) needs to deal with search params too. Persuasive: Simone Heckmann/Cooper Thompson: 2-0-0 (and will advise Patient Care that this will be occurring)
9276 Add arrival date/time in Encounter (Finnie Flores) As in the last note, the time in the locations history could convey that information. Recommend no change as disposition After discussion, the proposed representation using the location periods should work, will contact submitter to check if meets their needs.
7671 2015May core #962 - The notion of a provider, in a role, for a period of time seems like a common pattern. Should this be pulled out into a participation type. (Greg Staudenmaier/Claude Nanjo/Kensaku Kawamoto) This has been refactored into the CareTeam resource. So believe we can close this now. We should notify the submitters and verify that the issue is now resolved. Persuasive with Mod: Simone Heckmann/Cooper Thompson: 2-0-0 (no change to be applied)
End of call here
7964 2015May core #1284 - Update type of Priority. (Sean Moore - Epic) refer to the last note on the item, recommend providing a standard extension referencing the http://hl7.org/fhir/v2/0485/index.html valueset on the priority. Thoughts Cooper? Main issue with changing the datatype is that priority is something that you want to sort on, and valuesets need extra information for ordering, and trying to merge priorities from multiple systems is problematic.
10524 RelatedPerson.relationship: include codes from http://hl7.org/fhir/v3/RoleCode where concept is-a _AffiliationRoleType (Igor Sirkovich)
12141 Add a code for 'Attorney' to relationship and participant.role value sets (Aleksandra Pavlyshina) does this also get covered by 10524? CareTeam has Participant type which is not a PA valueset, however related person and person.contact may want to have it extended to support attorney, but expect possibly more appropriate with RelatedPerson only. So persuasive with mod?
11471 Beef up use-cases - 2016-09 core #635 (Lloyd McKenzie) review text provided by Iryna (below)
Administration Resources are cornerstone resources that are used by clinical and other domains of the FHIR Standard. • Managing a Master Record of a Patient and a Person (e.g. MPI) - A #Patient resource is used to describe patient demographic and visit information and any updates to it. It can be used to communicate #Patient information to other systems (e.g. other registries, clinical, ancillary and financial systems). Some systems distinguish the Patient Registry (or Client Registry) from the Person Registry. A #Person resource is a base for the Person Registry system. The Patient/Person Management use case includes creation, update, as well as merge/unmerge and link/unlink scenarios. • Managing a Master Record of a Provider and Service Catalogue (e.g. Provider Registry, Service Directory) – A #Practitioner resource is a base resource for enabling the registry of individuals, related to providing health care services. Other resources, such as #Organization, #Location, #HealthcareService, are creating a complete picture of where, how and by whom the care services are enabled to a patient. The resources can be used for managing the master record or as a reference in clinical resources to inform about participants and places for various clinical resources. • Managing Other Administrative Records – The Administration domain of the FHIR standard includes creation and update of #Device and #Substance records. Resources can be used for managing a master record or communicating its information to other systems. • Enabling Patient Profiles, Clinical Reporting, Connecting clinical records – Administration Resources are referred by almost all clinical resources. Querying systems, using the references to Administration Resources enables the creation of profiles and reports of various complexities. Enabling Clinical Grouping and Financial Reporting – Other use cases are included in the roadmap of resources, developed by the Patient Administration group. The roadmap section lists plans and updates of the current work.
The Practitioner Role split discussion part 2 and hopefully vote, then this related tracker item 10762 Wrong system used in practitioner example files (Günter Zöchbauer) recommend that we approve this change This may need to be revisited as the practitioner.role is split out into the other resource.
Return to PA Main Page © 2016 Health Level Seven® International. All rights reserved.