SOC 2 Case Study
SOC 2 Case Study
Categorization of information
Maintenance and support of the security system and necessary backup and
offline storage
Incident response
<Insert 2>
XYZ designs its processes and procedures related to TMS to meet its objectives for its
MT services. Those objectives are based on the service commitments that XYZ makes
to user entities, the laws and regulations that govern the provision of MT services, and
the financial, operational, and compliance requirements that XYZ has established for
the services. The MT services of XYZ are subject to the security and privacy
requirements of the Health Insurance Portability and Accountability Act Administrative
Simplification, as amended, including relevant regulations, as well as state privacy
security laws and regulations in the jurisdictions in which XYZ operates.
Security commitments to user entities are documented and communicated in Service
Level Agreements (SLAs) and other customer agreements, as well as in the
description of the service offering provided online. Security commitments are
standardized and include, but are not limited to, the following:
Security principles within the fundamental designs of the TMS that are designed
to permit system users to access the information they need based on their role in
the system while restricting them from accessing information not needed for their
role
<Insert – 3>
XYZ Service Organization (XYZ) provides medical transportation (MT) services
throughout the United States. The Company was founded in 19XX to provide MT
services to Medicaid recipients.
<Insert – 4>
The TMS runs on Microsoft Windows file servers using a wide area network.
The TMS uses the IBM DB2 relational database management system. These database
servers and file servers are housed in XYZ’s secured network operations centers
(NOCs).
< Insert -5 >
The TMS is a Microsoft Windows client-server application developed and maintained
by XYZ’s in-house software engineering group. The software engineering group
enhances and maintains the TMS to provide service for the company’s transportation
providers, governments and managed care providers (user entities), treating facilities,
and riders. XYZ’s software is not sold on the open market.
The TMS tracks information in real time. The information is immediately stored in the
database and is accessible for daily operations, service authorization, trip scheduling,
provider reimbursement, agency monitoring, and report generation. The information
can be retrieved, reviewed, and reported as needed to create the history of approvals
and denials for any rider. Information can be retrieved by rider identification number,
rider name, trip date, facility attended, and transportation provider.
The XYZ member services website is like the facility services website, except its focus
is on the riders. After a rider has successfully logged in, he or she is able to request
new trip reservations, view pending requests and processed reservations, edit pending
requests, withdraw pending requests, and cancel existing reservations. Requests are
placed in a request queue within the TMS database for review by call center personnel
through the TMS.
The facility staff manages the facility database for the TMS. They also maintain
the transportation standing orders within the system and take single trip
requests from facilities only.
The claims staff receives requests for payment and adjudicates these claims in
the software. This includes invoice management, trip verification, and billing
support.
IT
<Insert – 7>
As defined by XYZ, …. constitutes the following:
Transaction data
Output reports
Input reports
System files
Error logs
Transaction processing is initiated by the receipt of a trip or standing order request.
This request typically comes directly from a rider or treating facility by telephone or via
the websites, or it may arrive by fax from a treating facility. After the trip is completed,
the transportation provider sends XYZ paper documents with daily trip information,
including information about completed trips, cancellations or no-shows, and weekly
driver logs, all of which is entered into the system's verification module; a portion of this
trip completion information may be entered on the XYZ transportation provider web
interface.
Output reports are available in electronic PDF, comma-delimited value file exports, or
electronically from the various websites. The availability of these reports is limited by
job function. Reports delivered externally will only be sent using a secure method—
encrypted email, secure FTP, or secure websites—to transportation providers, treating
facilities, and governments or managed care providers using XYZ-developed websites
or over connections secured by trusted security certificates. XYZ uses Transport Layer
Security to encrypt email exchanges with government or managed care providers,
facility providers, and transportation providers.