Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Practitioner/PractitionerRole in Volume 1 #133

Closed
slagesse-epic opened this issue Oct 4, 2022 · 0 comments · Fixed by #147
Closed

Clarify Practitioner/PractitionerRole in Volume 1 #133

slagesse-epic opened this issue Oct 4, 2022 · 0 comments · Fixed by #147
Assignees
Labels
CP-worthy Should create a CP to be linked to this issue

Comments

@slagesse-epic
Copy link
Member

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)

1:46

Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.

The description of Practitioner says "Each Practitioner may be related to one or more Organizations, one or more Locations and one or more Healthcare Services." However, relationships between Practitioners and Organizations, Locations, and Healthcare Services is done via the FHIR PractitionerRole resource.

Furthermore, we decided that OrganizationAffiliation is a first class Resource in mCSD, but not PractitionerRole.

Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.

It would be helpful to explain how PractitionerRole fits into the ecosystem in Volume 1. Further, PractitionerRole and OrganizationAffiliation should have a similar level of visibility, I think.

Priority:

  • Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
@lukeaduncan lukeaduncan added the CP-worthy Should create a CP to be linked to this issue label Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CP-worthy Should create a CP to be linked to this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants