International Patient Summary Implementation Guide
2.0.0-ballot - STU 2 Ballot International flag

This page is part of the International Patient Summary Implementation Guide (v2.0.0-ballot: STU 2 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions

OperationDefinition: IPS Summary

Official URL: http://hl7.org/fhir/uv/ips/OperationDefinition/summary Version: 2.0.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: IpsSummary

This operation returns an IPS document in response to a POST request. The returned document MAY be generated on-demand and SHOULD represent the latest available information. This operation would not necessarily create a persisted IPS instance on the server responding to the request. When historic records or other documents are desired, this operation is not appropriate. For alternative operations and IPS generation guidance, please see IPS Generation and Data Inclusion

Generally when a patient's logical id is known, that id would be used to request the patient summary from a FHIR server (see [id] pattern below). When it is not known, servers MAY support using other identifiers (see identifier parameter below).

Servers MAY support profiles beyond the IPS. When supported, other profiles can be specified using the profile parameter. When not supported, servers MAY use the universal IPS Composition profile to identify what profile is returned by default.

Generated Narrative: OperationDefinition summary

URL: [base]/Patient/$summary

URL: [base]/Patient/[id]/$summary

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INidentifier0..1string
(token)

When the logical id of the patient is not used, servers MAY choose to support patient selection based on provided identifier. Unless the identifier system is unknown, requestors SHOULD include both the system and value (e.g. 'identifier=https://standards.digital.health.nz/ns/nhi-id|CNNJ9186') when using this parameter.

INprofile0..1uri

A specific profile for the patient summary may be specified. By default, servers MAY use the universal Composition profile to identify what profile the returned summary will adhere to. This is intended as a more flexible approach for implementers to support derivations of the IPS (e.g. national and jurisdictional implementations).

OUTreturn0..1Bundle

The Bundle returned is a document conforming to the specified input Composition profile parameter or the International Patient Summary Composition profile (if not otherwise specified)