Identify the specific US Core 7.0.0 screening instrument being used (e.g., PHQ-9, GAD-7, AUDIT-C) and locate the corresponding LOINC panel and component codes for the questionnaire items
Create FHIR Observation resources conforming to the US Core Screening and Assessment Observation profile; set Observation.category to survey (http://terminology.hl7.org/CodeSystem/observation-category) and include the SDOH category extension if applicable
Populate Observation.code with the LOINC instrument panel code, Observation.component[] with individual question/answer pairs, and Observation.value[x] with the total score or summary finding
Set all US Core 7.0.0 must-support elements including status, category, code, subject, effective[x], and value[x]; confirm hasMember references to component Observations if using a panel structure
POST the Observation resources to the FHIR server and verify retrieval using GET /Observation?patient={id}&category=survey&code={panel-LOINC}
Validate the resources against the US Core Screening and Assessment profile using $validate and resolve any must-support obligation warnings
Known gotchas
US Core 7.0.0 introduces the Screening and Assessment Observation profile as a new profile distinct from the Observation laboratory result and vital signs profiles; using the wrong profile category will cause validation failures
Must-support obligations in US Core 7.0.0 include both data absent reason handling and explicit population requirements that differ from US Core 6.x; implementers migrating from 6.x must review the updated must-support definition in the 7.0.0 IG
Screening responses captured via SDC QuestionnaireResponse and then extracted to Observation must preserve the original LOINC question codes in Observation.code rather than using local codes; use of local or proprietary codes breaks cross-system interoperability
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