Clinical Practice Guidelines
3.0.0-ballot - STU 3 Ballot International flag

Clinical Practice Guidelines, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cqf-recommendations/ and changes regularly. See the Directory of published versions

OperationDefinition: CPG Common Patient Summary

Official URL: http://hl7.org/fhir/uv/cpg/OperationDefinition/cpg-common-patient-summary Version: 3.0.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: CPGCommonPatientSummary
Other Identifiers: OID:2.16.840.1.113883.4.642.40.48.33.2

The summary operation generates a patient summary for a patient

Use Patient $summary to obtain the current patient summary as a document Bundle for a selected patient. This can supply a portable clinical overview to a receiving system or a guideline implementation that needs to assemble its patient context.

The operation describes agreed document conventions, such as the International Patient Summary. It does not require every returned document to use one named profile. A patient summary document has a different role from a guideline-specific case summary.

Language: en

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

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
OUTreturn1..1Bundle

The document Bundle that is the current patient summary document

The result of this operation is a patient summary document, constructed according to agreed conventions such as the International Patient Summary.

Notes:

  • Invoke the operation on a Patient instance. It does not declare system-level or Patient-type-level invocation, and it declares no input parameters beyond the patient selected by the request URL.
  • Expect one returned Bundle representing the current summary document. Agree the applicable document convention with the service and validate the document structure and profile it claims; the return parameter itself is typed as Bundle without a specific target profile.
  • Check the document's patient identity, authorship, dates, source information, and clinical coverage before using it as evaluation data. A summary can omit information needed by a particular recommendation.

For guideline-specific organization of patient information, see case features. For execution context and data acquisition, see integration mechanisms.