FHIR-40510 |
Update client and server requirements for “community” parameter |
FHIR-41520 |
Clarify “state” parameter required for authorization code flow |
FHIR-42958 |
Add guidance for use of PKCE |
FHIR-43003 |
Update server metadata requirements for extensions and certifications |
FHIR-43005 |
Clarify server may grant a subset of “scopes_supported” |
FHIR-43006 |
Clarify scope requirements for Tiered OAuth |
FHIR-43020 |
Clarify where client requests scopes in each workflow |
FHIR-43022 |
Clarify use of a client secret is not permitted |
FHIR-43024 |
Add STU Note regarding concurrent use with SMART |
FHIR-43120 |
Clarify JWT conformance requirements |
FHIR-45173 |
Add certification example for privacy disclosures |
FHIR-46113 |
Add certification example for exchange purposes |
FHIR-46448 |
Add scope guidance based on TEFCA SOP |
FHIR-48921 |
Clarify that Registered Claim Names should be omitted from registration response |
FHIR-49143 |
Representation/formatting of word may be confused as conformance language |
FHIR-49179 |
Remove reference to SMART configuration for scope negotiation |
FHIR-49184 |
Add underlying UDAP.org reference for “extensions” parameter |
FHIR-49633 |
Example narrative should be for B2C and authorization code in 3.2.2 |
FHIR-48986 |
Add text and STU note about logical server groups |
FHIR-49141 |
Move conformance language out of home page |
FHIR-49142 |
Update invalid conformance language |
FHIR-49174 |
Clarify token use must be consistent with authorization context |
FHIR-49177 |
Require supported signing algorithms for registration in server metadata |
FHIR-49178 |
Move US Realm requirements from 5.2.1.1; Change subject_id to recommend NPI |
FHIR-49181 |
Clarify how certification template is used and the non-normative nature of examples |
FHIR-49185 |
Add guidance on how to use this IG and SMART App Launch framework together |
FHIR-49187 |
Move JWT requirements to General Requirements page |
FHIR-49239 |
Clarify signed metadata has precedence over plain JSON elements |
FHIR-49631 |
Clarify that unassigned parameters should be omitted from registration response |
FHIR-50929 |
Remove dependency of hl7.fhir.us.core: 3.1.1 |
FHIR-50963 |
Specify the IG standards status |
FHIR-51054 |
Add time synchronization to community checklist |
FHIR-51244 |
Pluralize exchange_purpose in example certification keys table |