This wiki has undergone a migration to Confluence found Here
FHIR Digital Signature Working Page
Revision as of 21:42, 8 October 2014 by GrahameGrieve (talk | contribs) (Created page with "This page documents a series of proposals arising out of the digital signature implementation project = Proposal 1 : A page for digital signature implementation notes = We s...")
This page documents a series of proposals arising out of the digital signature implementation project
Proposal 1 : A page for digital signature implementation notes
We should add a digital signature page that:
- describes the use cases that we support
- details general implementation considerations & where to look for support
- describes a profile on xml digital signatures
- describes some FHIR specific transforms that when used with FHIR resources confer robustness against format changes, and meet the use cases
- deals with xml vs json
Proposal 2
We should add a note to both the xml and json pages describing signature ready xml and json. Implementers are recommended to conform to this
XML ready for Digital Signature
- default namespaces - only use default namespaces for fhir and xhtml namespaces
- outside the xhtml, no whitespace except in attributes
- no processing instructions, no xml comment
JSON ready for digital Signature
- all unimportant whitespace removed from the JSON representation
XML/JSON that conforms to this profile can be reproduced exactly from the data in the resource, without needing to store the actual XML (or can be recreated correctly from the JSON)
Proposal 3
That we define a standard transform