MDS As A Service

Overview

• Engine deployed as Gem
• What all does services do?
• Where is the line drawn for MDS?
• WTF?
• Questions

Engine Deployed as Gem

• Services has been an engine from day one
• Previously embedded into abaqis2 source tree
• Pulled out of abaqis2 and now it's own project
• pvdgm_services Gem deployed on Rubygems.org

What all does Services Do?

• MDS Pull
  • Simple LTC
  • PCC
  • LCCA
• MDS Push
  • Providigm MDS Upload Web Service calls
• HL7 Inbound Web Service
  • As called by MirthConnect
• Future support (outbound web service calls like MedlineU and other things).
• And now, management of all MDS Uploaded data

Where is the line drawn for MDS?

• Controller for MDS Upload Web Service
• All DCI components for processing the upload
  • MDS File Upload
  • MDS File Upload Contents
  • MDS Assessments
• A connecter interface for application-specific processing
• Knows nothing about Facilities, Residents, Stays, QCLIs, etc.
• Provides no UI for MDS Uploads
  • Connect your own controllers through the Services DCI Context

WTF?

• To allow multiple applications to use the same MDS Upload service
  • A2 <=> A3
  • Possible other applications that we have no intention of building
    • MDS Scrubber
    • Medicare Fraud Detection
    • There's no end of things that we will likely never build...

Questions?