This is the first balloted version of the Continuous Glucose Monitoring Implementation Guide.
descmd
This is the first balloted version of the Continuous Glucose Monitoring Implementation Guide.
first
true
category
Diagnostics
title
Continuous Glucose Monitoring
introduction
The Continuous Glucose Monitoring Implementation Guide provides a standardized approach for sharing CGM data between actors. This IG focuses on enabling the exchange of CGM data, including high-level reports and raw glucose observations, to support collaborative glucose management.
ci-build
http://build.fhir.org/ig/HL7/cgm
RelatedIgs
(None Found)
This IG has never been published
Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/uv/cgm (Problem #1 with package-list.json at http://hl7.org/fhir/uv/cgm: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
INFORMATION: ConceptMap/CGMSummaryToLoinc: ConceptMap.group[0].target: Target Code System http://loinc.org is only supported on the terminology server, so the target codes are not validated for performance reasons (1 uses)
02. Data Submitters POST CGM data as transaction Bundles to EHRs [base]/$submit-cgm-bundle. The Observation.performer element may be omitted in CGM profiles (i.e., Bundle entries) because the data is typically device-generated and the device is implicitly the performer. If needed, device information is captured through the Device resource and submitted as an entry in the CGM Data Submission Bundle.
Best Practice Recommendation: In general, all observations should have a performer (26 uses)
03. After ballot resolution and sufficient testing, the CGM editors will submit this code to THO as suggested.
INFORMATION: CodeSystem/cgm: CodeSystem: Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
04 As discussed in the guide's "Note on LOINC Codes" section (index.html#note-on-loinc-codes), this IG will use LOINC codes for all Observations and DiagnosticReports. LOINCs have been submitted and approved and are awaiting publication.
INFORMATION: CodeSystem/cgm-summary-codes-temporary: CodeSystem: Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
WARNING: CodeSystem/cgm-summary-codes-temporary: CodeSystem.concept[0]: HL7 Defined CodeSystems should ensure that every concept has a definition (1 uses)
05 This message refers to the FHIR F4 Bundle.language element which is not constrained in this IG.
INFORMATION: StructureDefinition/cgm-data-submission-bundle: StructureDefinition.snapshot.element[4].binding.extension[0]: The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
06 CGM Data Submission Standing Order Profile is derived from the Data Submission Standing Order Resource Profile. Because of the profile derivation, the example for the former - CGM Data Submission Standing Order - also conforms to and thus is an example of the latter.
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/cgm/StructureDefinition/data-submission-standing-order'): The Implementation Guide contains no examples for this profile (1 uses)
07 WE intentionally suppress narratives in this IG because narratives may not be meaningful or useful for resources generated by devices (e.g., lab instruments, CGM devices). The structured data is often sufficient for interpretation, and narratives do not add value in these contexts.
Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (23 uses)
08 This message refers to the FHIR F4 ServiceRequest.locationCode element which is not constrained in this IG.
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer. Using version '3.0.0', found versions: 2014-03-26, 3.0.0 (0 uses)
hl7.fhir.uv.cgm
