Profile: mcode-primary-cancer-condition constrains FHIR Condition; set Condition.code from the mCODE Primary Cancer Disorder value set (SNOMED CT concepts for malignant neoplasm) — this is the required binding for the cancer diagnosis code
Populate Condition.bodySite using the mCODE Body Location Qualifier extension and codes from the Body Location Codes value set to document the anatomic site and optional laterality/orientation qualifiers
Apply the HistologyMorphologyBehavior extension on Condition to record the ICD-O-3 or SNOMED CT morphology and behavior code (e.g., adenocarcinoma, 8140/3)
Set Condition.subject to reference an mcode-cancer-patient Patient resource; set Condition.clinicalStatus to 'active' or 'remission' using the standard FHIR clinical status value set
Link the Condition to staging information by populating Condition.stage.assessment to reference a TNMStageGroup Observation resource, or leave it unset if staging is recorded separately
Validate the resource against the mCODE STU4 (v4.0.0) package using the FHIR validator with package hl7.fhir.us.mcode#4.0.0
Known gotchas
Conditions that are clearly secondary (metastatic) should use the SecondaryCancerCondition profile, not PrimaryCancerCondition — conflating primary and secondary is a frequent modeling error
The HistologyMorphologyBehavior extension is on Condition (not on Observation) and must use ICD-O-3 or SNOMED CT morphology codes — plain text histology descriptions are insufficient for mCODE compliance
mCODE STU4 (v4.0.0) is based on FHIR R4; do not reference STU3 (v3.0.0) profile URLs in a v4.0.0 context as the profile canonical URLs differ
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp