Kick off a bulk export request for the provided list of patients
post
/Patient/$export
The operation is defined at:
GET https://fhir-ehr.cerner.com/r4/OperationDefinition/patient-export?_format=json
Note:
- With the current implementation, the
patientparameter must be provided at least once. - Bulk data export requests do not currently recognize the Accept-Language header;
en-USis used instead. - Only one bulk export request for a client application and tenant combination may be in-progress at a single time.
- The authorization token must contain system read scopes for all resources requested in the
_typeparameter. - The experimental
_elementsparameter is not supported.
Provenance Behavior
- Provenances for the Location, Organization, and Practitioner resources cannot be exported.
- When the
_typeparameter is not provided and the authorization token includes the Provenance read scope, all relevant Provenance resources associated with each of the non-Provenance resources are exported by default. You may use theincludeAssociatedDataparameter to export only the latest provenance. - When the
_typeparameter is provided with specific resources and includes Provenance, all relevant Provenance resources associated with each of the non-Provenance resources are exported by default. - When both the
includeAssociatedDataparameter and the_typeparameter are provided, the_typeparameter must includeProvenance.
Optional Header
When the Prefer: handling=lenient header is provided, any unknown or unsupported parameters are ignored as specified in the Bulk Data Export parameters.
Request
Header Parameters
-
Accept(required): string
The media type to be requested. See what the resource's operation produces for what is supported.
-
Authorization(required): string
Contains the credentials to authenticate a consumer to the service. This should be the OAuth2 Bearer Token.
-
Content-Type(required): string
Specifies the content type of the request entity body. Accepted values are
application/fhir+json,application/json+fhir, andapplication/json. -
Prefer(required): string
Specifies whether the response is immediate or asynchronous.
respond-asyncis supported. A client must provide this header.
The body of the patient export operation.
Root Schema : PatientExport
Type:
objectA summary representation of the patient export (POST) operation.
Show Source
-
parameter(required):
array parameter
Parameters supported by the operation.
- The
patientparameter is required and must be provided at least once. - The
_type,_typeFilter,includeAssociatedData,_since, and_outputFormatparameters are optional and may be provided in the request body.
Details of the supported parameters:
patient:- A maximum of 20,000 values may be provided for
patient. - When the parameter name is
patient, the parameter value must be in the form ofvalueReference.
- A maximum of 20,000 values may be provided for
_type:- A string of comma-delimited FHIR resource types.
- When the parameter name is
_type, the parameter value must be in the form ofvalueString. - The following values are valid:
AllergyIntoleranceCarePlanCareTeamConditionCoverageDeviceDiagnosticReportDocumentReferenceEncounterGoalImmunizationLocationMedicationDispenseMedicationRequestPatientProcedureObservationOrganizationPractitionerProvenanceRelatedPersonServiceRequestSpecimen- When the
_typeparameter contains a reference resource (Location,Organization,Practitioner,RelatedPerson, orSpecimen) or an associated resource (Provenance), at least one of the following resources must also be provided:AllergyIntoleranceCarePlanCareTeamConditionCoverageDeviceDiagnosticReportDocumentReferenceEncounterGoalImmunizationMedicationDispenseMedicationRequestObservationPatientProcedureServiceRequest
- When the
_typeparameter is not provided, the resources to be exported are determined by the scopes provided in the authorization token. - Example:
Condition, Provenance
_typeFilter:- A string of comma-delimited FHIR REST queries provided in combination with
_type. - When the parameter name is
_typeFilter, the parameter value must be in the form ofvalueString. - When the
_typeFilterparameter is provided, the_typeparameter must be provided and must only have queries for the resources provided in_type. _typeFilterdoes not support queries for the following resources:LocationOrganizationPatientPractitionerProvenanceRelatedPersonSpecimen
_typeFiltersupports queries with the search parameters supported for the R4 resources with the exception of the following search parameters:_count_contained_containedType_elements_id_include_lastUpdated_revinclude_sort_summary_totalencounteridentifierpatientsubjectdate
- Supplying
_typeFilterwith the same resource multiple times is not supported. - Example:
Condition?clinical-status=active,Encounter?status=planned
- A string of comma-delimited FHIR REST queries provided in combination with
includeAssociatedData:- When the parameter name is
includeAssociatedData, the parameter value must be in the form ofvalueCode. - When provided, the patient export returns or omits a predefined set of FHIR resources associated with the request.
- A string of comma-delimited values. Valid values are
LatestProvenanceResourcesandRelevantProvenanceResources.
- When the parameter name is
_since:- Resources updated after this time are included in the response.
- When the parameter name is
_since, the parameter value must be in the form ofvalueInstant. - Example:
2021-03-18T19:19:42.000Z
_outputFormat:- The format for the requested bulk data files to be generated.
- When the parameter name is
_outputFormat, the parameter value must be in the form ofvalueString. - Valid values are
application/fhir+ndjson,application/ndjson, andndjson. - Defaults to
application/fhir+ndjsonwhen not provided.
{ "parameter": [ { "name": "patient", "valueReference": { "reference": "Patient/12783127" } }, { "name": "patient", "valueReference": { "reference": "Patient/12783128" } }, { "name": "patient", "valueReference": { "reference": "Patient/12783129" } }, { "name": "_type", "valueString": "Condition,Provenance" }, { "name": "_typeFilter", "valueString": "Condition?category=problem-list-item" }, { "name": "includeAssociatedData", "valueCode": "RelevantProvenanceResources" }, { "name": "_since", "valueInstant": "2021-03-18T19:19:42.000Z" }, { "name": "_outputFormat", "valueString": "application/fhir+ndjson" } ] } - The
-
resourceType(required):
string
Allowed Values:
[ "Parameters" ]The type of the FHIR resource.
{ "resourceType": "Parameters", }
Nested Schema : parameter
Type:
arrayParameters supported by the operation.
- The
patientparameter is required and must be provided at least once. - The
_type,_typeFilter,includeAssociatedData,_since, and_outputFormatparameters are optional and may be provided in the request body.
Details of the supported parameters:
patient:- A maximum of 20,000 values may be provided for
patient. - When the parameter name is
patient, the parameter value must be in the form ofvalueReference.
- A maximum of 20,000 values may be provided for
_type:- A string of comma-delimited FHIR resource types.
- When the parameter name is
_type, the parameter value must be in the form ofvalueString. - The following values are valid:
AllergyIntoleranceCarePlanCareTeamConditionCoverageDeviceDiagnosticReportDocumentReferenceEncounterGoalImmunizationLocationMedicationDispenseMedicationRequestPatientProcedureObservationOrganizationPractitionerProvenanceRelatedPersonServiceRequestSpecimen- When the
_typeparameter contains a reference resource (Location,Organization,Practitioner,RelatedPerson, orSpecimen) or an associated resource (Provenance), at least one of the following resources must also be provided:AllergyIntoleranceCarePlanCareTeamConditionCoverageDeviceDiagnosticReportDocumentReferenceEncounterGoalImmunizationMedicationDispenseMedicationRequestObservationPatientProcedureServiceRequest
- When the
_typeparameter is not provided, the resources to be exported are determined by the scopes provided in the authorization token. - Example:
Condition, Provenance
_typeFilter:- A string of comma-delimited FHIR REST queries provided in combination with
_type. - When the parameter name is
_typeFilter, the parameter value must be in the form ofvalueString. - When the
_typeFilterparameter is provided, the_typeparameter must be provided and must only have queries for the resources provided in_type. _typeFilterdoes not support queries for the following resources:LocationOrganizationPatientPractitionerProvenanceRelatedPersonSpecimen
_typeFiltersupports queries with the search parameters supported for the R4 resources with the exception of the following search parameters:_count_contained_containedType_elements_id_include_lastUpdated_revinclude_sort_summary_totalencounteridentifierpatientsubjectdate
- Supplying
_typeFilterwith the same resource multiple times is not supported. - Example:
Condition?clinical-status=active,Encounter?status=planned
- A string of comma-delimited FHIR REST queries provided in combination with
includeAssociatedData:- When the parameter name is
includeAssociatedData, the parameter value must be in the form ofvalueCode. - When provided, the patient export returns or omits a predefined set of FHIR resources associated with the request.
- A string of comma-delimited values. Valid values are
LatestProvenanceResourcesandRelevantProvenanceResources.
- When the parameter name is
_since:- Resources updated after this time are included in the response.
- When the parameter name is
_since, the parameter value must be in the form ofvalueInstant. - Example:
2021-03-18T19:19:42.000Z
_outputFormat:- The format for the requested bulk data files to be generated.
- When the parameter name is
_outputFormat, the parameter value must be in the form ofvalueString. - Valid values are
application/fhir+ndjson,application/ndjson, andndjson. - Defaults to
application/fhir+ndjsonwhen not provided.
{
"parameter": [
{
"name": "patient",
"valueReference": { "reference": "Patient/12783127" }
},
{
"name": "patient",
"valueReference": { "reference": "Patient/12783128" }
},
{
"name": "patient",
"valueReference": { "reference": "Patient/12783129" }
},
{
"name": "_type",
"valueString": "Condition,Provenance"
},
{
"name": "_typeFilter",
"valueString": "Condition?category=problem-list-item"
},
{
"name": "includeAssociatedData",
"valueCode": "RelevantProvenanceResources"
},
{
"name": "_since",
"valueInstant": "2021-03-18T19:19:42.000Z"
},
{
"name": "_outputFormat",
"valueString": "application/fhir+ndjson"
}
]
}
Nested Schema : items
Type:
Show Source
object-
name:
string
The name of the parameter
-
value[x]:
string
The value of the parameter
Response
Supported Media Types
- application/fhir+json
Default Response
This operation supports the System authorization type.
Example Request:
Example Request:
POST https://fhir-ehr.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Patient/$export
Example Request Body:
{
"resourceType": "Parameters",
"parameter": [
{
"name": "patient",
"valueReference": { "reference": "Patient/12783127" }
},
{
"name": "patient",
"valueReference": { "reference": "Patient/12783128" }
},
{
"name": "patient",
"valueReference": { "reference": "Patient/12783129" }
},
{
"name": "_type",
"valueString": "Condition,Provenance"
},
{
"name": "_typeFilter",
"valueString": "Condition?category=problem-list-item"
},
{
"name": "includeAssociatedData",
"valueCode": "RelevantProvenanceResources"
},
{
"name": "_since",
"valueInstant": "2021-03-18T19:19:42.000Z"
},
{
"name": "_outputFormat",
"valueString": "application/fhir+ndjson"
}
]
}
Example Response:
Status: 202 Accepted
Content-Location: https://fhir-ehr.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/bulk-export/jobs/<Job_ID>
Headers
-
Content-Location: string
Indicates the url to access the status of the export request.
-
X-Request-Id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the
X-Request-Id, if present. -
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the
opc-request-id, if present.