Continuous Glucose Monitoring
1.0.0 - STU 1 International flag

Continuous Glucose Monitoring, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cgm/ and changes regularly. 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
Standards status: Trial-use Maturity Level: 2 Computable Name: SubmitCGMBundle

This operation is used to submit CGM data. The input is a 'transaction' Bundle that conforms to the CGM Data Submission Bundle Profile, containing CGM data (such as summary reports and sensor readings). The output is a 'transaction-response' Bundle 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

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

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INresource1..1Bundle (CGM Data Submission Bundle)

A 'transaction' Bundle that conforms to the CGM Data Submission Bundle Profile containing multiple resources related to Continuous Glucose Monitoring (CGM) data

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.