Operational runtime
HOLD
No production FHIR resource or operation is demonstrated while the runtime remains held.
CUBE OneCare maintains a target-requirements catalog for HL7 FHIR R4 (v4.0.1). The production runtime is on HOLD with zero demonstrated production resources and operations. This is not a conformance or certification claim.
Planning artifacts and target checks do not establish a live FHIR capability. Operational claims remain blocked until production evidence exists.
Operational runtime
HOLD
No production FHIR resource or operation is demonstrated while the runtime remains held.
Target requirements
Planning only
The catalog records intended requirements and must not be read as an active CapabilityStatement.
Customer exchange
HOLD
No production customer exchange or partner transaction is demonstrated.
The resource identifiers below are planning requirements only. Listing a resource does not mean it is available, authorized, persisted, or proven in production.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
Not demonstrated in the production runtime.
SMART launch, token flows, and Bulk Data Export remain target requirements. They are not active production capabilities.
patient/*.readTarget onlyTarget least-privilege access for an authorized patient context.
user/*.readTarget onlyTarget least-privilege access for an authorized user context.
system/*.readTarget onlyTarget backend-service access with tenant and purpose binding.
launchTarget onlyTarget launch context after authorization and session binding are proven.
HOLD until tenant, actor, purpose, session, and audit controls are proven end to end.
Not advertised as supported. Any future write path requires separate governance and runtime proof.
HOLD. No production export operation or customer delivery is demonstrated.
HOLD. No partner-specific production launch or exchange is demonstrated.
These are activation requirements, not claims that the current production FHIR runtime enforces them.
Must be proven for each actor, tenant, purpose, resource, and operation.
Must bind patient consent and revocation to every permitted data path.
Must be time-limited, justified, reviewed, and backed by durable audit evidence.
Must prevent cross-tenant access and enforce approved organizational attributes.
These vocabularies are target bindings for planned profiles; no production terminology support is implied.
SNOMED CT
Target binding
LOINC
Target binding
ICD-10-CM
Target binding
RxNorm
Target binding
CVX
Target binding
CPT
Target binding
Review target requirements with the integration team without treating roadmap artifacts as live capability.
External EHR integration requirements
Required