SMART PH4H
0.9.9 - release

This page is part of the PH4H (v0.9.9: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Artifact Index

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Medication Overview (Minimal)

Minimal medication overview payload for use within a QR code payload. Based on the IHE Pharmacy Medication Overview logical model, with short element labels (one or two letters) and simple data

Medication Treatment Line (Minimal)

Minimal medication treatment line payload for use within a QR code payload. Based on the IHE Pharmacy Medication Treatment Line logical model, with short element labels (one or two letters) and simple data types suitable for encoding in a compact QR code payload.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

SMART Bundle (IPS)

This profile represents the constraints applied to the Bundle resource by the International Patient Summary (IPS) for use within the SMART Guidelines.

Note: The profile expects atleast one SMART Consent entry to be present.

SMART Composition (IPS)

This profile represents the constraints applied to the Composition resource by the International Patient Summary (IPS) for use within the SMART Guidelines

Note: The profile expects atleast one SMART Consent entry to be present within Advance Directives section

SMART Consent

A profile of the consent resource to track consent of a pilgrim to participate

FHIR R5 upgrade notes (need this implemented as a structure map):

  • make cardinality of decision 1.. and should stop using it in lieu of verification.verified
  • use verification.verifiedBy instead of Consent.organization
  • the period extenion should be replaced by Consent.period
  • the Consent.patient should be replaced by Consent.subject
  • Consent.verification.verifiedBy should be used instead of Consent.organization

Terminology: Structure Maps

These define transformations to convert between data structures used by systems conforming to this implementation guide.

MedicationOverviewLMToMedicationOverviewBundle
MedicationOverviewMinToMedicationOverviewBundle
MedicationOverviewMinToMedicationOverviewLM

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example DocumentReference Consent Paperwork

Example copied from FHIR-IPS used for Composition

Example MedicationOverviewMin (compact QR payload)

Minimal medication overview payload for Martha DeLarosa with two medication lines, suitable for QR code transmission.

Example SMART Consent

Example SMART Consent

MedicationOverviewTransformed