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

HL7 FHIR-i requests adding more strict context to extensions. #2

Open
bvdh opened this issue Nov 23, 2023 · 0 comments
Open

HL7 FHIR-i requests adding more strict context to extensions. #2

bvdh opened this issue Nov 23, 2023 · 0 comments

Comments

@bvdh
Copy link

bvdh commented Nov 23, 2023

Section Numbers/URLS

  1. Priority Descriptors - PCC - Paramedicine Care Summary (PCS) v2.0.0-draft (fhir.org)
  2. Status History Observations - PCC - Paramedicine Care Summary (PCS) v2.0.0-draft (fhir.org)
  3. PCS Encounter status history sub-type - PCC - Paramedicine Care Summary (PCS) v2.0.0-draft (fhir.org)

Issue
In FHIR-i are reviewing extensions defined in the FHIR space in order to clean them up, remove redundant extensions and improve the definition of the remaining ones.
During this process, a set of IHE defined extensions where discussed that need work.
The extensions context is 'Element', allowing it to be used on any element on any resource. FHIR-i is concerned that this is far to generic and strongly recommends restricting the use to the specific context where it is intended to be used. For all these extensions that would be Encounter.

Proposed Change
Restrict the use of these extensions to the root level of Encounter. This can be achieved by adding the line
Context: Encounter to the header of these extensions in the sushi fsh file.

Priority:

  • Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant