1 / 35

Sleep Medicine Epidemiology and Information Systems

Sleep Medicine Epidemiology and Information Systems. Michael Rueschman mrueschman@partners.org. What We Do. Existing Infrastructure. Moved in Summer 2010 Initially 9 personnel; now 27 and growing Primary IT/IS staff did not move to Boston

lea
Download Presentation

Sleep Medicine Epidemiology and Information Systems

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. Sleep Medicine Epidemiology and Information Systems Michael Rueschman mrueschman@partners.org

  2. What We Do

  3. Existing Infrastructure • Moved in Summer 2010 • Initially 9 personnel; now 27 and growing • Primary IT/IS staff did not move to Boston • Most equipment left behind, save for one file server (no longer in use)

  4. Sleep Reading Center

  5. Source: http://en.wikipedia.org/wiki/Polysomnography

  6. Clinical Trials

  7. What to do?

  8. File Transfer

  9. File Storage

  10. Data Entry

  11. Databases

  12. Virtual Machines

  13. Usage Summary • SFTP transfers and Diplomat • RFA and MAD • SQL Server 2008 and MySQL clusters • REDCap • DIPR Cluster (4 VMs) • Web services (DNS, proxy, hosting)

  14. Future Pursuits • Improving remote PSG scoring capabilities • Sharing large files with collaborators • Replacing legacy systems and consolidating existing systems • Interfacing with clinical systems • Increasing web presence

  15. How has it all worked?

  16. Weaknesses • Less direct control, particularly of our data • Navigating the “layers” to find the right source • Available solutions may be less than ideal

  17. Weakness: Case Study Ticket 4905659

  18. Ticket 4905659 • Opened April 9th, 2011 • 10 or so e-mails; 3 phone calls • At least 11 people involved in ongoing conversations • Resolution pending…

  19. Strengths • Less direct control, particularly of our data • Using the expertise of others to improve the quality of our work • Systems are (largely) stable and reliable • Multiple offerings allow for flexibility • Cheaper

  20. Strengths: Case Study sleepfreeze.dipr.partners.org

  21. Thanks! For more information: http://sleepepi.partners.org/ http://understandingsleep.org/

More Related