VRRS Teleconference

2 views
Skip to first unread message

Dennis Ballance

unread,
Jun 26, 2013, 11:09:54 AM6/26/13
to vr...@googlegroups.com, ot...@asteris.biz, Paul Fisher, Schofield, Donald, McCarthy, Patrick, Stuart Turner, Erin Kilpatrick, DVM, mma...@clemson.edu, Litchfield, Ben, Erin Kilpatrick, DVM, Kevin Grant, Peterson, Kris, Mark Skeels, Greer, Bob, Santamaria, Suzanne, and...@vetrocket.com, Aerik Sylvan (aerik@vetrocket.com), Alma Tisher
Given the july 4 holiday, I propose this alternate meeting time.
 
Here are the notes from the last meeting:
 
  1. Attendees: Mike Martin, Stuart Turner, Jason Otis, Aerik Sylvan, Evelyn Eichorn
  2. Purpose of standard: How closely tied is a document standard to its exchange method? 
  1. Binding these is good in that it can give a full solution to a potential implementor.
  2. Binding these is challenging in that there may be multiple legitimate exchange methods.
    3.
  1. Confidentiality, deduplication, and other issues will need to be solved.
  2. The specific technologies used (REST, SOAP, encrypted email) is less important than ensuring that the mechanism meets the exchange requirements.
    3.
  1. If there is a reference implementation that people outside of the solution review it, the community can adopt it as a de facto standard.
  2. A potential growth area is medical record document format.
  3. Consists of three things
    4.
  1. Document structure
  2. Technology-independent requirements
    3.
  1. Privacy - Two approaches - no requirements, so no need; or, set industry standards.
  2. Confidentiality
  3. Security
    4.
  1. Encryption requirements - all point-to-point communications are encrypted. This allows for either an encrypted connection, or encrypted data via an unencrypted connection. In other words, the LAYER that is encrypted is unspecified.
    2.
  1. Integrity
    2.
  1. Nonrepudiation - 100% confidence that both parties are aware that the delivered document is complete and accurate.  This includes reliability.
    2.
  1. Documents that are imported can subsequently be exported in a complete and intact form (i.e. with no loss).
    2.
  1. Amendments -
  2. Data retention - Legal requirements vary. Determine if this is in scope for this requirement.
    3.
  1. Sample implementation using one or more technical implementation
    2.
 
 
 
1. Please join my meeting.
2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.
 
United States: +1 (773) 897-3016
Access Code: 234-719-277
Audio PIN: Shown after joining the meeting
Meeting ID: 234-719-277
GoToMeeting®
Online-Meetings made easy®
 
 
 
 
 
 
invite.ics
Reply all
Reply to author
Forward
0 new messages