Open Issue 31: synchronous XDS/XCA/XDR and MHD Push
Opened this issue · 2 comments
Currently, only synchronous XDS/XCA/XDR and MHD Push are supported. This scope was limited
for the public-comment deadline. After public comment, we plan to add in asynchronous (WS-A and AS4)
and full MHD. One area that needs work is Digital Certificates to support async end-to-end security
(Not needed for sync that uses TLS).
- Currently, base FHIR doesn't include a publicKey, and recommends a local extension
https://jira.hl7.org/browse/FHIR-10764. We will add an extension. - Note VhDir has an extension http://hl7.org/fhir/uv/vhdir/StructureDefinition/digitalcertificate,
but it is very complex. Not clear if this complexity is needed.
If certificate information is not needed for synchronous endpoints, why it is needed for asynchronous endpoints?
For existing exchange communities, the security policies are often established outside of the directory, such that it is not necessary to store that information in the directory.
Copied from Issue #64 from @slagesse-epic:
Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)
Regarding Open Issue mCSD_28
Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
It is not clear to me why support for asynchronous transactions necessitate the need of carrying certificates on the Endpoint Resource.
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
Define asynchronous endpoints in the mCSD Endpoint Types Code System.
Priority:
Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.