Loading...

XML

Word

Printable

JSON

Specification:

US UDAP Security (FHIR)
Raised in Version:

1.0.0
Work Group:

Security
Related URL:
http://hl7.org/fhir/us/udap-security/STU1/discovery.html#signed-metadata-elements
Related Page(s):

Discovery
Related Section(s):
2.3
Grouping:
- STU1-Update
- block-vote
Resolution Description:

Hide

Propose to include the following in 2.0

"The client and the server SHALL conform to the underlying server metadata profile."

Include above the note in 2.3

"The client and server SHALL validate the signed endpoints as per Section 3 (insert link) in UDAP Server Metadata."

Add note at the end of Section 2.4

"The authors recommend that the client be prepared to handle server metadata signed with a key for a different trust community than expected, regardless if the community parameter was used."

Show
Propose to include the following in 2.0 "The client and the server SHALL conform to the underlying server metadata profile." Include above the note in 2.3 "The client and server SHALL validate the signed endpoints as per Section 3 (insert link) in UDAP Server Metadata." Add note at the end of Section 2.4 "The authors recommend that the client be prepared to handle server metadata signed with a key for a different trust community than expected, regardless if the community parameter was used."
Change Category:
Clarification
Change Impact:
Non-compatible
Applied for Version:

current

The IG references https://www.udap.org/udap-server-metadata-stu1.html, but doesn't normatively require the client to do the behavior in section 3. Client validation of signed endpoints. It should.