OperationDefinition-docref

Sourcefhir.argonaut.r2#1.0.0:Argonaut Data Query Implementation Guide (v1.0.2)
resourceTypeOperationDefinition
iddocref
canonicalhttp://fhir.org/guides/argonaut/OperationDefinition/docref
statusdraft
publisherArgonaut Project
nameArgonaut Get DocumentReferences
date2016-10-18
descriptionThis operation is used to return all the references to documents related to a patient. The operation takes the input parameters: - patient id - start date - end date - document type and returns a [Bundle](http://hl7.org/fhir/bundle.html) of type "searchset" containing [Argonaut DocumentReference Profiles](http://fhir.org/guides/argonaut/StructureDefinition-argo-documentreference.html) for the patient. If the server has or can create documents that are related to the patient, and that are available for the given user, the server returns the DocumentReference profiles needed to support the records. The principle intended use for this operation is to provide a provider or patient with access to their available document information. The server SHOULD return at least all references for documents that it has made available in a document indexing system. This is the same as a simple query (`GET [base]/DocumentReference?patient=[id]`). This operaton differs from a simple query in that DocumentReferences may be created 'on-the-fly' in response to this operation. For example, in some cases the documents themselves may not exist but can be generated when needed so a reference to them can be generated using this operation. If no documents exist and an 'on-demand' document cannot be created then the operation will return an empty search bundle.
codedocref
systemfalse
typetrue
instancefalse
resourcesDocumentReference
Usages(none)

URL: [base]/DocumentReference/$docref

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN patient 1..1 id

The id of the patient resource located on the server on which this operation is executed. If there is no match, an empty Bundle is returned

IN start 0..1 string
( date )

The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all documents prior to the end date are in scope. If neither a start date nor an end date is provided, the most recent or current document is in scope.

IN end 0..1 string
( date )

The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all documents subsequent to the start date are in scope. If neither a start date nor an end date is provided, the most recent or current document is in scope

IN type 0..1 CodeableConcept http://hl7.org/fhir/ValueSet/c80-doc-typecodes (Required)

The type relates to document type e.g. for the LOINC code for a C-CDA Clinical Summary of Care (CCD) is 34133-9 (Summary of episode note). If no type is provided, the CCD document, if available, SHALL be in scope and all other document types MAY be in scope

OUT return 1..1 Bundle

The bundle type is "searchset"containing Argonaut DocumentReference Profiles


Produced 06 Apr 2023