hl7/fhir-ipa

International Patient Access Implementation Guide Source

International Patient Access FHIR Specification

Authors: Grahame Grieve, Eric Haas, Rob Hausam, Vassil Peytchev, Mikael Rinnetmäki, Isaac Vetter

The International Patient Access API Specification describes how an application acting on behalf of a patient or a practitioner can access information about the patient from a clinical records system using a FHIR R4 based API. The clinical records system may be supporting a clinical care provider (e.g., a hospital or a general practitioner), a health data exchange, or other system managing patient records, including a national health record system (more...).

The specification is published at https://www.hl7.org/fhir/uv/ipa/.

CI snapshots

Each branch of this repository is automatically built and published by the build.fhir.org infrastructure. You can locate the built snapshot with the branch name. For instance, the lates commit to the master branch is published at https://build.fhir.org/ig/HL7/fhir-ipa/branches/master. Or select from the list of branches.

Discusssion

Please join the discussion on the specification on the #IPA channel at the FHIR Community chat.

The specification is also discussed on weekly Zoom calls.

fhir-ipa's Issues

improve distinction between medstatement and medrequest

Pharmacy WG points out that https://build.fhir.org/ig/HL7/fhir-ipa/StructureDefinition-ipa-medicationstatement.html

• contains a bunch of irrelevant documentation regaarding condition
• should better explain when to use medstmt and medrequest ... for FHIR developers (but it's appropriate to tell app developers to SHALL query for both)
• Medication is not in the list of artifacts.
• Probably should remove normal English terms in favor of FHIR resource names (e.g. MedRequest and not Prescription, etc).
  ** argument is: Prescription can be not medication. MedicationRequest profile doesn't actually use the word Prescription. It's confusing to HL7 insiders.

rp-1 on RelatedPerson is in wrong place

rp-1 on RelatedPerson is in wrong place should be on root not .active and add .condition on
relationship and patient see below:`

currently the diff looks lke this:

differential:
  element:
    - id: RelatedPerson
      path: RelatedPerson
    - id: RelatedPerson.active
      path: RelatedPerson.active
      min: 1
      max: '1'
      constraint:  # <<<<< not here
        - key: rp-1
          severity: error
          human: Either a name or a relationship SHALL be provided (or both)
          expression: name.exists() or relationship.exists()
      mustSupport: true
    - id: RelatedPerson.relationship
      path: RelatedPerson.relationship
      mustSupport: true
    - id: RelatedPerson.name
      path: RelatedPerson.name
      comment: >-
        In some contexts, the real name of the related person is obscured. The
        resource SHOULD include at least some useable name for the person in the
        name.text element
      mustSupport: true

should be:

differential:
  element:
    - id: RelatedPerson
      path: RelatedPerson
      constraint:  # <<<<< here !!!
        - key: rp-1 
          severity: error
          human: Either a name or a relationship SHALL be provided (or both)
          expression: name.exists() or relationship.exists()
    - id: RelatedPerson.active
      path: RelatedPerson.active
      # no need for min and max here either
      mustSupport: true
    - id: RelatedPerson.relationship
      path: RelatedPerson.relationship
      condition: rp-1  # <<<<< ref here...
      mustSupport: true
    - id: RelatedPerson.name
      path: RelatedPerson.name
      comment: >-
        In some contexts, the real name of the related person is obscured. The
        resource SHOULD include at least some useable name for the person in the
        name.text element
      condition: rp-1  # <<<<< and here...
      mustSupport: true

correct or expand ipa-by-country.md

https://github.com/HL7/fhir-ipa/blob/master/input/pagecontent/ipa-by-country.md

is Australian Argonaut compatible with IPA?
Are there other national specs that we should add here? i.e. https://confluence.hl7.org/display/PC/IPA%3A+national+specification+comparison

SMART authorization requirement

Is it a hard requirement that SMART SHALL/MUST be followed for IPA (https://github.com/HL7/fhir-ipa/blob/main/input/pagecontent/access.md)?

condition?patient&clinical-status&category should more clearly be a SHOULD

in:

• condition profile
• fetching page

US Core specific IPA?

https://github.com/HL7/fhir-ipa/blob/main/input/resources/CapabilityStatement-ipa-server.json#L46 why does IPA say something specific to US Core?