What CodeX is — and why it matters.
HL7 CodeX — the Common Oncology Data Elements Accelerator — is a member-driven FHIR Accelerator hosted by HL7 International. It was created to solve one of the most persistent problems in clinical oncology and genomic medicine: the lack of a shared, structured, interoperable data standard that allows cancer and genomic data to move between systems, institutions, and researchers without losing meaning along the way.
CodeX began with mCODE — the minimal Common Oncology Data Elements framework — which defines how a core set of cancer-related data elements should be represented in FHIR. The goal was simple and ambitious at the same time: if every oncology system used the same data model, a patient's cancer history could follow them from institution to institution, from clinical trial to clinical trial, from their oncologist to their primary care physician, without requiring manual translation or data loss.
"The challenge is not that genomic data doesn't exist. The challenge is that it exists everywhere and nowhere at once — in PDF lab reports, in proprietary databases, in systems that cannot talk to each other. CodeX is building the infrastructure to change that."
The GenomicX domain within CodeX extends this work into the broader genomic medicine space — moving beyond oncology to include molecular tumor boards, pathogen genomics, pharmacogenomics, and the full range of clinical genomics use cases that are rapidly moving from research into standard of care. This is the domain where Intersect Healthcare Systems participates.
What it means to be an invited member.
CodeX membership is structured, not open. Developer/Implementer membership — the category under which Intersect holds membership — is for organizations that are building systems on CodeX standards. It requires a demonstrated technical commitment to FHIR implementation and active contribution to the workgroups.
Being an invited member means Intersect was accepted into the CodeX community based on our implementation work and our technical approach. We are not observers. We are in the working groups where the standards are being written, where implementation decisions are being made, and where the real-world feedback of builders shapes what the standards say.
What Developer/Implementer Membership Means in Practice
- Active participation in workgroup meetings — not just access to published documents
- Contribution to use case development that shapes how standards are written
- Early access to draft standards before public release
- Direct relationships with the clinical, academic, and industry experts writing the standards
- Demonstrated implementation of CodeX/mCODE standards in a live FHIR system
- Obligation to provide real-world implementation feedback to the workgroup
The GenomicX domain: where we work.
The GenomicX domain is where the intersection of FHIR and genomic medicine is being defined. It brings together clinical geneticists, bioinformaticians, oncologists, pathologists, health IT developers, and standard bodies to answer a deceptively difficult question: how should genomic data be represented in a clinical record so that it is useful — not just stored?
Intersect participates actively in two GenomicX workgroups:
🧬 Molecular Tumor Board Workgroup
This workgroup is building the FHIR data model and workflow specifications that will enable molecular tumor boards to function with structured, interoperable data instead of slide presentations and free text. The goal is a standard that any system can implement — so that a tumor board's recommendations become structured FHIR resources that flow into the patient record and can be queried, tracked, and learned from at scale.
🦠 Pathogen Genomics Workgroup
This workgroup addresses the clinical use of pathogen genomic sequencing — how sequencing results from infectious disease diagnostics should be represented in FHIR and used in clinical decision support. Antimicrobial resistance profiling, outbreak detection, and infection control are among the applications that depend on getting this data structure right.
Our participation in both workgroups reflects the breadth of what Intersect is building — a platform that handles not just hereditary genomics but the full clinical genomics landscape that modern medicine requires.
Why this matters for Intersect's clinical partners.
For health systems and academic medical centers evaluating genomics infrastructure, CodeX membership carries a specific meaning: the genomic data in an Intersect deployment will be represented in the format that the rest of the industry is converging on.
That matters for three reasons:
Interoperability
Genomic data stored in mCODE-compliant FHIR resources can be shared with any CodeX-compliant system — another institution, a clinical trial registry, a research data warehouse — without custom integration work.
Future-Proofing
As payers, regulators, and accreditation bodies increasingly require structured genomic data reporting, organizations with CodeX-compliant infrastructure will be ready. Those on proprietary platforms will be rebuilding.
Standards Leadership
Early adoption of the standards being written today — while they are still being shaped — allows clinical partners to influence how those standards evolve. Intersect brings that influence into every deployment.
What we are building next.
Our CodeX participation directly informs the molecular tumor board workflow that is on Intersect's near-term roadmap. The workgroup is defining exactly how a case should be submitted, how variant interpretation should be structured, and how recommendations should be documented as FHIR resources. We are building the implementation that will demonstrate that this works in a real clinical environment.
We are seeking an academic oncology or molecular tumor board program to serve as the first clinical validation partner for this workflow. If your institution runs a molecular tumor board and wants to be part of defining how this works — not just adopting a standard after it is finalized — we want to talk.
The same applies to the Pathogen Genomics workgroup work. Clinical microbiology programs with whole-genome sequencing infrastructure and an interest in structured FHIR representation of sequencing results are exactly the kind of partners we are looking for.