meet US Core profile requirements when writing Patient and Condition resources

domain: fhir-us-core · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. For US Core Patient: include at least one Patient.identifier with a system and value, Patient.name with family or given, Patient.gender (required), and Patient.birthDate (must-support); also include race and ethnicity extensions (us-core-race, us-core-ethnicity) if available.
  2. Populate Patient.name.family and Patient.name.given as separate structured fields rather than only text; many systems require structured name components for matching.
  3. For US Core Condition: set Condition.clinicalStatus (required binding to ConditionClinicalStatusCodes), Condition.verificationStatus (required), and Condition.category with at least one coding from the ConditionCategoryValueSet (e.g. 'encounter-diagnosis' or 'problem-list-item').
  4. Condition.code must be present and should use SNOMED CT or ICD-10-CM; if using ICD-10-CM include the system http://hl7.org/fhir/sid/icd-10-cm.
  5. Set Condition.subject to a reference to the Patient resource; include Condition.onsetDateTime or onsetPeriod when the onset date is known.
  6. Validate both resources against the relevant US Core profile canonical URLs using $validate or the HL7 validator before submission.

Known gotchas

Related routes

Validate resources against US Core profiles and check must-support field compliance
fhir · 6 steps · unrated
Write US Core CarePlan and CareTeam resources for a patient with chronic conditions and link them to the relevant Conditions and Practitioners managing the patient
hl7.org/fhir/us/core · 5 steps · unrated
Query US Core profiles for a patient's clinical data ensuring MustSupport element compliance
hl7.org/fhir · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans