Dash Solutions today announced the availability of a healthcare-specific compliance and security suite to streamline application development on Amazon Web Services (AWS).
The collaboration between Dash Solutions and AWS follows the AWS “Shared Responsibility Model” for compliance and security for healthcare. The Dash Compliance Automation Suite allows AWS users to quickly configure HIPAA required customized administrative policies and technical controls on AWS.
Digital Health applications frequently impact patient outcomes by gathering, analyzing and creating unique patient data. As collaboration between Digital Health and traditional health systems increases and data moves between on premises and the cloud, the need for compliance and security increases in kind.
Specifically, HIPAA compliance regulations dictate requirements for storing, exchanging and sharing protected health information. Without a tool to streamline the compliance process, burgeoning Digital Health companies are forced to turn to expensive consultants, proprietary platforms which limit innovation, or spend countless hours on compliance minutiae.
Dash Compliance Automation Suite benefits companies by providing faster time to commercialization, reduced compliance costs and time investment, and minimized risk of compliance and security breaches.
“We chose to work with Dash because they offered additional technical monitoring and controls on AWS. They also helped us write and implement solid policies that were understood, enacted and enforced. Dash actually cared about all of our policies, even outside the scope of what Dash could monitor or connect into – such as things on the administrative level,” said Jacob Parsell, Redsson CTO and Dash customer.
“It is my pleasure to announce that Dash Solutions has strengthened its existing relationship with AWS as an Advanced Technology Partner in the AWS Partner Network on its road to achieving Healthcare Competency status. Dash continues to promote technology adoption in healthcare by lowering the burden of cloud compliance and security. Our commitment to advance the healthcare mission requires the best technology, and our relationship with AWS is a big part of that,” said Brett Lieblich, Dash Solutions CMO.
For more information about Dash Solutions please visit www.dashsdk.com.
About Dash Solutions
Dash Solutions is for digital health leaders, healthcare providers, and other innovative companies in healthcare facing the challenges of exchanging information under HIPAA compliance. Dash alleviates the burden of compliance allowing fresh innovation through technology adoption. Hospitals and health systems leverage Dash to evaluate security and compliance practices and to extend their reach beyond the datacenter into the public cloud.
You can find Dash Compliance Automation Suite on the web at www.dashsdk.com
Contact
For more information about Dash or this news item:
Jacob Nemetz, CEO
[email protected]
FAQ: Dash and AWS Collaboration for Healthcare Compliance
What does AWS Advanced Technology Partner status mean?
It indicates that a company has met AWS Partner Network requirements for technical validation, customer references, and alignment with AWS architecture guidance. It is a partner designation, not a certification of the partner’s own security or HIPAA compliance. Buyers should still review the partner’s independent audit reports and ask how it handles their data.
What is AWS Healthcare Competency?
Healthcare Competency is an AWS specialization for partners with demonstrated healthcare expertise, validated customer deployments, and solutions aligned to industry requirements such as security, interoperability, and clinical workloads. It signals relevant experience; it does not transfer any HIPAA obligation from the customer to the partner.
What does a compliance automation suite actually automate?
Typically it generates and maintains administrative policies, maps controls to framework requirements, continuously checks cloud configuration against those controls, collects evidence, and flags drift for remediation. It does not perform the risk analysis for you, and it does not replace the judgment of an auditor or the accountability of your security leadership.
How does compliance automation fit the AWS Shared Responsibility Model?
AWS is responsible for the security of the cloud, while the customer is responsible for security in the cloud, including configuration, access management, and monitoring. Automation operates on the customer’s side of that line: it helps you configure and evidence your own controls, and it cannot compensate for responsibilities that remain yours under the BAA.
Can a compliance platform make a company HIPAA compliant on its own?
No. HIPAA compliance depends on your documented risk analysis, implemented safeguards, workforce training, vendor agreements, and actual operational practice. A platform helps you build, monitor, and evidence those elements. Treat any vendor claiming to deliver compliance as a product with caution, and confirm what is being assessed and by whom.
What should I check before adopting a healthcare compliance platform?
Ask which frameworks and control versions it supports, whether it reads configuration directly from your cloud accounts or relies on manual attestation, how it handles evidence retention, and what access it requires to your environment. Request its own SOC 2 report and confirm how it protects the credentials it uses to connect to your accounts.
How much access does a compliance tool need to my AWS environment?
Most need read-only access to configuration and logging services, with narrowly scoped roles rather than broad administrative permissions. Ask for the exact IAM policy, whether cross-account roles are used, and how credentials are stored and rotated. Grant the minimum needed for monitoring and keep write access limited to defined remediation actions you approve.
Does using a compliance platform reduce the cost of an audit?
It can reduce the effort of evidence collection and the time spent remediating findings, which affects cost indirectly. Auditor fees themselves depend on scope, complexity, and the reporting period, and are not reduced by the tool you use. Ask your auditor early what evidence format they accept so automation output is usable rather than reworked.
How do I measure whether compliance automation is working?
Track control pass rates over time, mean time to remediate failed checks, the share of controls with current automated evidence, and the number of findings raised in the last audit. A useful signal is whether drift is caught and closed between audits rather than discovered during them.
Is a 2018 partnership announcement still relevant today?
Use it as background on the relationship, not as a statement of current capabilities. Partner designations, service names, and product features change, so verify the current status in the AWS Partner Network directory and confirm supported frameworks directly with the vendor before relying on the announcement in a procurement decision.