Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40010

Non-FHIR users cannot store app state

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • (NA)
    • Hide

      The current specification provides a baseline of capabilities. EHRs can go beyond, if they wish to support other types of subject references. We can clarify by adding to the end of http://hl7.org/fhir/smart-app-launch/2023Jan/app-state.html#querying-app-state:

      > The EHR MAY support additional queries, and an app MAY issue additional queries when they are supported.

      This allows enough room for experimentation with .identifier – but based on participation in current implementations, EHRs are able to support fhirUser scopes and user-oriented FHIR references.

      Show
      The current specification provides a baseline of capabilities. EHRs can go beyond, if they wish to support other types of subject references. We can clarify by adding to the end of http://hl7.org/fhir/smart-app-launch/2023Jan/app-state.html#querying-app-state: > The EHR MAY support additional queries, and an app MAY issue additional queries when they are supported. This allows enough room for experimentation with .identifier – but based on participation in current implementations, EHRs are able to support fhirUser scopes and user-oriented FHIR references.
    • Bas van den Heuvel / Yunwei Wang: 13-0-0
    • Clarification
    • Non-substantive

    Description

      This clause seems to require that if the subject is a user, then that user must be represented by one of the FHIR resources. This is stricter than the requirements elsewhere in the spec. It should be possible to store data for subject who do not have a FHIR representation. Consider allowing Basic.subject.identifier for non-FHIR users.

      Existing Wording:

      4. Basic.subject.reference is optional, associating App State with at most one subject. When omitted, global configuration can be stored in App State. When present, this SHALL be an absolute reference to a resource in the EHR’s primary FHIR server. The EHR SHALL support at least Patient, Practitioner, PractitionerRole, RelatedPerson, Person. The EHR’s documentation MAY establish support for a broader set of resources.

      (Comment 26 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: