This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2017-03-24 Learning Health Systems Call"
Jump to navigation
Jump to search
Line 92: | Line 92: | ||
* Motion to approve previous call minutes, [[2017-03-17_Learning_Health_Systems_Call]]: <mover>/<seconder> | * Motion to approve previous call minutes, [[2017-03-17_Learning_Health_Systems_Call]]: <mover>/<seconder> | ||
+ | Discussion | ||
* Emma reviewed [[media: Orthopedic_use_case.xlsx | Orthopedic use case.xlsx ]] | * Emma reviewed [[media: Orthopedic_use_case.xlsx | Orthopedic use case.xlsx ]] | ||
− | |||
* RelatedPerson.relationship conveys relationships, such as daughter, wife, son, so CareTeam.participant.member would allow access to RelatedPerson.relationship | * RelatedPerson.relationship conveys relationships, such as daughter, wife, son, so CareTeam.participant.member would allow access to RelatedPerson.relationship | ||
* PractitionerRole has specialties, but it is independent of CareTeam context. If a physician is both intensivist and pulmonologist, then we need to decide how to represent a single specialty in context of this care team | * PractitionerRole has specialties, but it is independent of CareTeam context. If a physician is both intensivist and pulmonologist, then we need to decide how to represent a single specialty in context of this care team | ||
Line 102: | Line 102: | ||
* CareTeam.participant.specialty 0..* -- is this needed? | * CareTeam.participant.specialty 0..* -- is this needed? | ||
− | Motion | + | Motion |
+ | * John Roberts motioned, Emma seconded that LHS recommends to PC that CareTeam.participant.responsibility and CareTeam.participant.specialty should be added. Vote: 7-0-0 | ||
− | * | + | Discussion |
+ | * The US-based Argonaut Provider Directory [http://www.fhir.org/guides/argonaut/pd/StructureDefinition-argo-practitionerrole.html PractitionerRole profile] has a binding to [http://www.fhir.org/guides/argonaut/pd/ValueSet-provider-specialty.html NUCC value set] for PractitionerRole.speciality |
Revision as of 21:04, 24 March 2017
Facilitator | Stephen Chu | Note taker(s) | Michelle Miller |
Attendee | Name | Affiliation
| |
Russell Leftwich | InterSystems | ||
X | John Roberts | Tennessee Department of Health | |
X | Stephen Chu | Individual | |
Evelyn Gallego | ONC | ||
X | Kathy Walsh | LabCorp | |
Asim Muhammad | Philips Research Europe | ||
Laura Heermann-Langford | Intermountain Healthcare | ||
X | Emma Jones | Allscripts | |
Jeff Brown | Cancerlinq | ||
X | Lisa Nelson | Individual | |
Dave Carlson | VA | ||
Chris Melo | Phillips Healthcare | ||
X | Michelle Miller | Cerner | |
Benjamin Kummer | Columbia University | ||
Matt Rhan | |||
Michael Padula | |||
X | Jim McClay | ||
Serafina Versaggi | VA | ||
Rob McClure |
Minutes
- Chair: Stephen Chu
- Scribe: Michelle Miller
- WebEx: https://intersystems.webex.com/meet/rleftwic
- Motion to approve previous call minutes, 2017-03-17_Learning_Health_Systems_Call: <mover>/<seconder>
Discussion
- Emma reviewed Orthopedic use case.xlsx
- RelatedPerson.relationship conveys relationships, such as daughter, wife, son, so CareTeam.participant.member would allow access to RelatedPerson.relationship
- PractitionerRole has specialties, but it is independent of CareTeam context. If a physician is both intensivist and pulmonologist, then we need to decide how to represent a single specialty in context of this care team
CareTeam resource changes -- GF#12509
- CareTeam.participant.role (existing) - need to update definition of role (since it mentiones responsibility) Example: PCP
- CareTeam.participant.responsibility 0..* (new) - Example: PT, Wound Care
- CareTeam.participant.specialty 0..* -- is this needed?
Motion
- John Roberts motioned, Emma seconded that LHS recommends to PC that CareTeam.participant.responsibility and CareTeam.participant.specialty should be added. Vote: 7-0-0
Discussion
- The US-based Argonaut Provider Directory PractitionerRole profile has a binding to NUCC value set for PractitionerRole.speciality