Continuous Glucose Monitoring
1.0.0-ballot - STU 1 Ballot International flag

This page is part of the Continuous Glucose Monitoring (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

OperationDefinition: Submit CGM Bundle Operation

Official URL: http://hl7.org/fhir/uv/cgm/OperationDefinition/submit-cgm-bundle Version: 1.0.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: SubmitCGMBundle

This operation is used to submit CGM data. The input is a Bundle of type 'transaction' containing CGM data (summary reports, sensor readings, etc.) and the output is a Bundle of type 'transaction-response' containing processing results for each submitted resource, or an OperationOutcome resource for overall failures.

The response Bundle will:

  • Maintain the same order as the submission Bundle
  • Include status and location information for each successfully processed entry
  • Include error details for any entries that could not be processed

Servers SHOULD support conditional create requests and persist client-supplied identifiers. Servers SHALL document in their developer documentation:

  • Which search parameters can be used in conditional create requests
  • How client-supplied identifiers are handled
  • Any deduplication strategies employed

Generated Narrative: OperationDefinition submit-cgm-bundle

URL: [base]/Bundle/$submit-cgm-bundle

Input parameters Profile:CGM Data Submission Bundle

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INresource1..1Bundle

A Bundle of type 'transaction' containing CGM data including summary reports, sensor readings, and related resources.

OUTreturn1..1Bundle

A Bundle of type 'transaction-response' containing processing results for each submitted resource. Each entry in the response Bundle corresponds to an entry in the submission Bundle and includes:

  • HTTP status code indicating success/failure
  • Location header for successful creations
  • OperationOutcome for any entry-specific errors

If the entire operation fails, a single OperationOutcome resource is returned instead.