The Launch of the iCoDE Standard Project

Published in Journal of Diabetes Science and Technology on 2022-05-09.

Nicole Y. Xu; Kevin T. Nguyen; Ashley Y. DuBord; David C. Klonoff; Julian M. Goldman; Shahid N. Shah; Elias K. Spanakis; Charisse Madlock-Brown; Siavash Sarlati; Azhar Rafiq; Axel Wirth; David Kerr; Raman Khanna; Scott Weinstein; Juan Espinoza

Read the paper at the publisher (DOI 10.1177/19322968221093662)

Abstract

The first meeting of the Integration of Continuous Glucose Monitor Data into the Electronic Health Record (iCoDE) project, organized by Diabetes Technology Society, took place virtually on January 27, 2022. Clinicians, government officials, data aggregators, attorneys, and standards experts spoke in panels and breakout groups.

Three themes were covered: why digital health data integration into the electronic health record is needed, what integrated continuously monitored glucose data will look like, and how this process can be achieved in a way that will satisfy clinicians, healthcare organizations, and regulatory experts.

Put this to work

Finding application record

Test whether the published finding applies in another setting.

For: Practitioners, researchers, founders, and operating leaders.
What you keep: A finding application record you can review, revise, and send.
What counts as sound: Answers a named decision
Separates evidence from assumptions
Includes the strongest contrary case
Names missing evidence
Ends with a test, owner, and date

Read the published paper and its limits before acting on the result.

Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.

The caseName the organization, setting, product, or piece of work without including confidential information.The decisionWhat must someone decide, and who owns that decision?Evidence in handList records, observations, measurements, rights, or prior work that can be checked.What is still unknownName missing evidence, disputed assumptions, and practical constraints.

Review the prompt

Finding application record 1.0

PURPOSE
Test whether the published finding applies in another setting.

CONTEXT
The case: Not provided
The decision: Not provided
Evidence in hand: Not provided
What is still unknown: Not provided

METHOD
1. State the finding being used.
2. Compare the original setting with yours.
3. List evidence that transfers and evidence that does not.
4. Name alternative explanations.
5. Define a replication or application test.

TASK
Use the method below to produce a Finding application record.

RULES
Separate facts, inferences, assumptions, estimates, hypotheses, and unknowns. Do not invent evidence, performance, rights, customers, economics, or regulatory standing. Quote or link the source for material facts. State uncertainty. Name what would disprove the conclusion. End with the smallest credible test, an owner, a decision date, and a stop condition.

A SOUND ANSWER
- Answers a named decision
- Separates evidence from assumptions
- Includes the strongest contrary case
- Names missing evidence
- Ends with a test, owner, and date

CAUTION
Read the published paper and its limits before acting on the result.

You can leave any field blank. The prompt will mark it as not provided.

If the record survives your review, send the question, evidence, unknowns, and requested next step.

Discuss a replication or application Intellectual Frontiers on LinkedIn