A Server that certifies to the 21st Century Cures Act for accessing patient data SHALL implement all components in the USCDI [USCDI link]

A Server that certifies to the 21st Century Cures Act for accessing patient data SHALL implement all components in the ... the US Core CapabilityStatement [Definition] .

Implementations meeting US EHR certification [of the ONC IT Health Certification program] requirements must support all US Core’s required scopes.

[For organization participating in the ONC Health IT Certification program] CVX vaccine codes are required

NDC vaccine codes SHOULD be supported as an additional code [of CVX Vaccine Codes]

[For organization participating in the ONC Health IT Certification program Servers SHALL support the additional USCDI requirement:], The reason or indication for the prescription

[For organization participating in the ONC Health IT Certification program Servers SHALL support the additional USCDI requirement:] reported adherence to prescribed medication instructions

Although both MedicationRequest.reasonCode and MedicationRequest.reasonReference are marked as Additional USCDI Requirements [which are required for organizations participating in the ONC Health IT Certification program]. The certifying Server system is not required to support both, but SHALL support at least one of these elements

[For organizations participating in the ONC Health IT Certification program and supporting MedicationRequest.reasonReference,] Servers SHALL support at least one target resource in MedicationRequest.reasonReference

Although none of the Observation.derivedFrom references are flagged as Must Support, the Certifying System SHALL* support at least one of them

Although Patient.deceased[x] is marked as additional USCDI, certifying systems are not required to support both [boolean and dateTime data types], but SHALL support [at] least Patient.deceasedDateTime

Certifying systems [, those that are participating in the ONC Health IT certification program,] SHALL... follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for Patient.address.line and Patient.address.city for new and updated records.

[For organizations participating in the ONC Health IT Certification program] Servers … SHALL support ... US Core Procedure Profile for communicating the reason or justification for a referral as Additional USCDI Requirements

[For organizations participating in the ONC Health IT Certification program,] although both Procedure.reasonCode and Procedure.reasonReference are marked as Additional USCDI Requirements, the certifying Server system is not required to support both, but SHALL support at least one of these elements.

[For organizations participating in the ONC Health IT Certification program] Servers … SHALL support ... US Core Service Request Profile for communicating the reason or justification for a referral as Additional USCDI Requirements

[For organizations participating in the ONC Health IT Certification program,] although both ServiceRequest.reasonCode and ServiceRequest.reasonReference are marked as Additional USCDI Requirements, the certifying Server system is not required to support both, but SHALL support at least one of these elements.

[For organizations participating in the ONC Health IT Certification program,] when using ServiceRequest.reasonReference Servers SHALL support at least one target resource in ServiceRequest.reasonReference

[For organizations participating in the ONC Health IT Certification program,] when using ServiceRequest.reasonReference …The referenced resources SHOULD be a US Core Profile as documented in Referencing US Core Profiles

If an element is marked as Additional USCDI and defined by a pattern [as described by ElementDefinition.pattern], then the pattern defines the elements and element values that the Certifying System SHALL be capable of providing.

Primitive elements are single elements with a primitive value…. If they are marked as Additional USCDI, then the Certifying System SHALL be capable of providing the element value to meet the Additional USCDI requirement.

For any complex element marked as Additional USCDI, the Certifying System SHALL be capable of providing at least one of the sub-element values.

[I]f any sub-element is marked as Additional USCDI [for a complex element] and the parent element is not… [and] the parent element is represented in the structure, Certifying System SHALL support the sub-elements labeled as Additional USCDI.

When a Reference type element is labeled as Additional USCDI and has a single target profile referenced, the target profile SHALL be supported for Certifying Systems.

When a Reference type element labeled as Additional USCDI, has multiple target profiles referenced, and specific targets are labeled as Must Support, the Must Support target profile(s) SHALL be supported by Certifying Systems.

[I]f a slice is labeled as ... Must Support/Additional USCDI and the slicer element is not labeled as ... Additional USCDI, then if the ... certifying system supports the element, it must support the slice's definition. There are no examples of this structure in US Core.

[I]f a slice is labeled as … Must Support and the slicer element is ... labeled as … Must Support/Additional USCDI, then … certifying system [SHALL support] the element[ and] the slice's definition.

Certifying Systems SHALL support, a category of "sdoh"

Certifying Systems ... SHOULD support the ... US Core Simple Observation Category codes

Certifying Systems ... MAY support other categories

[For the US Core Observation Screening Assessment Profile,] Certifying Systems SHALL support, the US Core Screening Assessment Observation Category codes

[For the US Core Observation Screening Assessment Profile,] Certifying Systems SHOULD support, the US Core Screening Assessment Observation Maximum Category codes

[For the US Core Observation Screening Assessment Profile,] Certifying Systems MAY support other codes.

Although the [US Core Interpreter Needed Extension] is marked as an Additional USCDI Requirement on both US Core Patient and US Core Encounter Profiles, the certifying Server system is not required to support the extension on both profiles but SHALL support the extension on at least one.

[For US Core Simple Observation Profile, ]Certifying Systems ... SHOULD support the other US Core Simple Observation Category codes [in addition to the US Core Screening Assessment Observation Category codes]

[For US Core Simple Observation Profile, ]Certifying Systems SHALL support, the US Core Screening Assessment Observation Category codes

[For US Core Simple Observation Profile, ]Certifying Systems ... MAY support other categories [in addition to US Core Screening Assessment Observation Category codes and US Core Simple Observation Category codes].

[I]f a slice is labeled as Additional USCDI... and the slicer element is ... labeled as Must Support/Additional USCDI..., then ... the Certifying System... [SHALL support] the element[ and] the slice's definition.

When a Reference element is labeled as Additional USCDI has multiple target profiles referenced, but none are labeled as Must Support, at least one target profile SHALL be supported by Certifying Systems.

If an Additional USCDI element has a choice of datatypes for its content, the datatypes the Certifying System SHALL support are labeled as Must Support.

Healthcare Service Location Codes (HSLOC) and SNOMED-CT Healthcare Facility Type value sets meet the USCDI applicable vocabulary standard for the Encounter Location Data Element. Certifying Systems MAY use a code from either vocabulary.