1 / 9

Electronic Submission of Medical Documentation (esMD) AoR L2 Harmonization

Electronic Submission of Medical Documentation (esMD) AoR L2 Harmonization. May 22, 2013. Meeting Etiquette. Please announce your name each time prior to making comments or suggestions during the call Remember: If you are not speaking keep your phone on mute

Download Presentation

Electronic Submission of Medical Documentation (esMD) AoR L2 Harmonization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Electronic Submission of Medical Documentation (esMD)AoR L2 Harmonization May 22, 2013

  2. Meeting Etiquette • Please announce your name each time prior to making comments or suggestions during the call • Remember: If you are not speaking keep your phone on mute • Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call • Hold = Elevator Music = very frustrated speakers and participants • This meeting, like all of our meetings, is being recorded • Another reason to keep your phone on mute when not speaking! • Feel free to use the “Chat” or “Q&A” feature for questions or comments From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute  NOTE: This meeting is being recorded and will be posted on the esMD Wiki page after the meeting

  3. Agenda

  4. Schedule • Wednesday, 1 - 3 PM ET: eDoC Workgroup meeting • 1 - 2 PM ET: eDoC Use Case Meeting • 2 - 3 PM ET: eDoC Structured Data SWG Meeting • Friday, 2 - 3 PM: eDoC Structured Data SWG Meeting

  5. AoR L2 Digital Signature Needs • Does RIM support digital signatures? Artifacts needed include: • Signed digest • GMT date/time • Signature purpose • OCSP • Validated delegation of rights • Multiple signers • Public certificates of all signers • Textual output (CDA viewer compatible) – e.g., “Digitally signed by Dr. Bob Smith on 1/1/2015 20:00 GMT as Legal Authenticator” • Signature section compatibility with unstructured body

  6. Digital Signature & CDA Unstructured Body CDA Document Digital Signatures Header Unstructured Body e.g. PDF Alt Name Space -- Digital Signature Section Text Entry

  7. HL7 RIM & Digital Signatures • SignatureCode • A code specifying whether and how the participant has attested his participation through a signature and/or whether such a signature is needed. E.g., a surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. • CE (Coded Element); cardinality 0..1: Element may be omitted and can have, at most, one occurrence.

  8. HL7 RIM & Digital Signatures • SignatureText • A textual or multimedia depiction of the signature by which the participant endorses his or her participation in the Act as specified in the Participation.typeCode and that he or she agrees to assume the associated accountability. E.g., an "author" participant assumes accountability for the truth of the Act statement to the best of his knowledge. • Digital signature: this attribute can represent digital signatures, for example, by reference to a signature data block that is constructed in accordance to a digital signature standard, such as XML-DSIG, PKCS#7, PGP, etc. • ED: Encapsulated Data. Cardinality 0..1: Element may be omitted and can have, at most, one occurrence.

  9. AoR L2 Requirements and Options • Switch to Excel file

More Related