US Core and USCDI support
The profiles, data classes and implementation choices supported by this Health IT Module under US Core 6.1.0 and USCDI v3.
This Health IT Module supports US Core 6.1.0, which is the implementation guide adopted for USCDI v3 under the HTI-1 final rule. 47 US Core profiles are supported across 26 resource types.
Documentation published before November 2026 referenced US Core STU 3.1.1 and USCDI v1. Those references are superseded. The versions on this page are the supported ones.
Adopted standards
| Standard | Version supported |
|---|---|
| HL7 FHIR | R4 (4.0.1) |
| HL7 FHIR US Core Implementation Guide | 6.1.0 |
| USCDI | v3 |
| SMART App Launch Implementation Guide | 2.0.0 |
| FHIR Bulk Data Access (Flat FHIR) | 2.0.0 |
| OAuth 2.0 Authorization Framework | RFC 6749 |
| PKCE for OAuth 2.0 Public Clients | RFC 7636 |
| OpenID Connect Core | 1.0 |
| OAuth 2.0 Token Introspection | RFC 7662 |
| OAuth 2.0 for Native Apps | RFC 8252 |
Supported profiles by resource
A resource returned by this API conforms to the profile or profiles listed against its type. The
same list is published in the server's CapabilityStatement under
rest.resource.supportedProfile.
| Resource | US Core profiles |
|---|---|
AllergyIntolerance | |
CarePlan | |
CareTeam | |
Condition | |
Coverage | |
Device | |
DiagnosticReport | |
DocumentReference | |
Encounter | |
Goal | |
Immunization | |
MedicationDispense | |
MedicationRequest | |
Observation |
|
Patient | |
Procedure | |
QuestionnaireResponse | |
ServiceRequest | |
Specimen | |
RelatedPerson | |
Location | |
Medication | |
Organization | |
Practitioner | |
PractitionerRole | |
Provenance |
US Core Choices and References
US Core permits a server to make certain implementation choices, and requires those choices to be documented. The choices this Health IT Module makes are set out below, as required by the §170.315(g)(10) Certification Companion Guide.
Representation choices
| Choice | What Maximus does |
|---|---|
| Response format | application/fhir+json only. XML is not supported. |
DocumentReference.content.attachment | Returned as url, referencing a Binary endpoint, rather than inline data. Retrieve the document with a second authenticated GET against that URL. |
DiagnosticReport.presentedForm | Returned as an attachment reference on the same basis as DocumentReference. |
| Clinical notes | Exposed through both DocumentReference and DiagnosticReport, as US Core requires. |
Condition categories | problem-list-item, encounter-diagnosis and health-concern are all supported and are separately addressable through granular scopes. |
| Medications | MedicationRequest.medication[x] is returned as medicationCodeableConcept wherever the medication is coded. Where a contained or referenced Medication is used, it is resolvable via the Medication endpoint. |
Provenance | Supported as a read interaction. Provenance is returned for resources where author and organization information is recorded. |
Reference resolution
References between resources are returned as relative literal references of the form
Type/id, resolvable against the service base URL.
"subject": { "reference": "Patient/example-patient" }
# resolves to
GET https://fhir.maximus.care/api/r4/Patient/example-patient
Contained resources are used only where the referenced resource has no independent identity.
_include and _revinclude are not supported; resolve references with a
follow-up read.
Missing data
Where US Core marks an element as must support and the data is genuinely absent, Maximus
follows the US Core missing-data guidance rather than omitting the element silently: a
dataAbsentReason or a nullFlavor-equivalent code is returned where the profile
defines one.
Additional data supported
Beyond the data classes required by USCDI v3, this Health IT Module also exposes the following, as disclosed under 45 CFR 170.404(a)(2):
| Resource | Additional capability |
|---|---|
Coverage | Patient insurance coverage, beyond the USCDI requirement. |
Encounter | Full encounter history, searchable by date and id. |
ServiceRequest | Orders and referrals, searchable by category, code, status and authored date. |
Questionnaire and QuestionnaireResponse | Structured assessments, including SDOH screening instruments. |
RelatedPerson | Patient contacts and next of kin. |
Specimen | Specimen detail supporting laboratory results. |
MedicationDispense | Dispense records, where recorded. |
PractitionerRole | Practitioner-to-organization roles and specialties. |
Endpoint | Practice-level service endpoint metadata. |
These are offered on the same terms as the certified capabilities. They are exposed through the same scopes and the same authorization model, and carry no additional fee.