Skip to content

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

@bvdh

Description

@bvdh

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions