Modernizing NIH's Clinical Research Support System (CRSS)
Since 2011 we have supported NIH's clinical research system with full technical responsibility, rebuilt it, and moved it to FedRAMP-compliant government cloud.
The challenge
A classic ASP and PHP system running in a contractor data center relied on batch loads, manual server access for study document uploads, and manual user provisioning. It had to move to government infrastructure on a very tight timeline.
What was delivered
- Architected the target environment with the NIH Center for Information Technology.
- Rebuilt the application in .NET and React with APIs, automated workflows, NIH single sign-on, and configurable metadata.
- Built the System Security Plan with the customer's ISSO.
- Run vulnerability scans with Invicti (web applications), Tenable Nessus (infrastructure), and DbProtect (databases), and remediate the findings.
- Support continuous monitoring, working with Splunk Universal Forwarder for log forwarding, and promote releases through the Change Advisory Board.
Approach
We replaced manual steps with automated workflows and made study metadata configurable, so routine changes no longer need code releases. Security work (planning, scanning, remediation) is part of normal delivery rather than a separate phase.
Outcomes
- Data migrated to government infrastructure on schedule.
- Now hosted on FedRAMP-compliant government cloud.
- Near-zero downtime within the service-level agreement.
- 35% or more fewer metadata change requests after configurable metadata was introduced.
Let's discuss your next project.
Tell us what you are trying to change. We will reply with practical next steps, whether or not we turn out to be the right fit.