Document Digital Signature - Supplement revision 2: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
JohnMoehrke (talk | contribs)
2,910 edits
No edit summary
JohnMoehrke (talk | contribs)
2,910 edits
No edit summary
Line 1: Line 1:
This work item is a revision to the current [[DSG]] supplement to update Digital Signatures to new IHE documentation template, and to use a newer version of XADES standard.  
This work item is a revision to the current [[DSG]] supplement to update Digital Signatures to new IHE documentation template, and to use a newer version of XADES standard.  
*Harmonize with the S&I Framework initiative esMD  
*Harmonize with the S&I Framework initiative esMD and HL7 CDA Digital Signature
*If we update DSG we need to do something with NAV as well. Consider whether to move away from the use of the NAV manifest since ITI was discussing the lack of interest in NAV being used alone. Do we pull the schema into the DSG spec, update NAV or something else entirely? (Just as we were talking about deprecating NAV, someone came to Connectathon and wanted it)
** Harmonize the signature block requirements
*Look to see if there are lessons learned as we update. Ask Massimo from Tiani, ask esMD, etc.
** Potentially add option for CDA encapsulated signature
*we need to pull the NAV schema into the DSG spec.
*Look to see if there are lessons learned as we update. Ask Massimiliano from Tiani, ask esMD, etc.
*QRPH wants DSG document that encapsulates the content. This is mostly for RFD use-cases. Need to warn Document Sharing use-cases that this might not be well supported by Document Consumers.
*Also: do we also mention the new CDA signature as an option, consider an encapsulating DSG (which may be covered by DEN), etc.  
*Also: do we also mention the new CDA signature as an option, consider an encapsulating DSG (which may be covered by DEN), etc.  
*Add an Option that a Document Source could claim that indicates that it creates a DSG document representing the SubmissionSet. That is that the DSG document includes signature for all documents it is submitting in the submission set, and where that DSG document is included in the submission set.




Need people. Plan: Put a call out to the ITI implementer’s list (and the two vendors from CAT this year who did DSG) and other ITI lists looking for someone to help write this. Putting the call out to user-centric organizational bodies such as hospitals, EHRA, IHE USA implementation workgroup, etc via HIMSS would also be helpful.
Need people. Plan: Put a call out to the QRPH, PCC, PCD, ITI implementer’s list (and the two vendors from CAT this year who did DSG) and other ITI lists looking for someone to help write this. Putting the call out to user-centric organizational bodies such as hospitals, EHRA, IHE USA implementation workgroup, etc via HIMSS would also be helpful.


== T-Con May 14 at 9am Central Time ==
Doodle poll to determine next best time for regular meeting:
 
== T-Con Wednesday May 28 at 9am Central Time ==
Meeting Number: 922 584 193
Meeting Number: 922 584 193


Revision as of 09:30, 14 May 2014

This work item is a revision to the current DSG supplement to update Digital Signatures to new IHE documentation template, and to use a newer version of XADES standard.

  • Harmonize with the S&I Framework initiative esMD and HL7 CDA Digital Signature
    • Harmonize the signature block requirements
    • Potentially add option for CDA encapsulated signature
  • we need to pull the NAV schema into the DSG spec.
  • Look to see if there are lessons learned as we update. Ask Massimiliano from Tiani, ask esMD, etc.
  • QRPH wants DSG document that encapsulates the content. This is mostly for RFD use-cases. Need to warn Document Sharing use-cases that this might not be well supported by Document Consumers.
  • Also: do we also mention the new CDA signature as an option, consider an encapsulating DSG (which may be covered by DEN), etc.
  • Add an Option that a Document Source could claim that indicates that it creates a DSG document representing the SubmissionSet. That is that the DSG document includes signature for all documents it is submitting in the submission set, and where that DSG document is included in the submission set.


Need people. Plan: Put a call out to the QRPH, PCC, PCD, ITI implementer’s list (and the two vendors from CAT this year who did DSG) and other ITI lists looking for someone to help write this. Putting the call out to user-centric organizational bodies such as hospitals, EHRA, IHE USA implementation workgroup, etc via HIMSS would also be helpful.

Doodle poll to determine next best time for regular meeting:

T-Con Wednesday May 28 at 9am Central Time

Meeting Number: 922 584 193

Meeting Password: meeting

https://himss.webex.com/himss/j.php?MTID=med046b88e9ca8ed166d37f3fa95cec09

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

To only join the teleconference

To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.

Call-in toll-free number (US/Canada): 1-866-469-3239

Call-in toll number (US/Canada): 1-650-429-3300

Global call-in numbers: https://himss.webex.com/himss/globalcallin.php?serviceType=MC&ED=285349737&tollFree=1

Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf

Access code:922 584 193

Retrieved from "http://wiki.ihe.net/index.php?title=Document_Digital_Signature_-_Supplement_revision_2&oldid=76965"