HBEDS SaaS for Hospital Bed Capacity Reporting and Operational Readiness.
DataScience9 HBEDS helps hospitals and public-health programs automate bed-capacity intake, validate hospital-specific logic, manage onboarding, and maintain an auditable pipeline from source extraction through NHSN-ready submission.
NHSN-ready reporting
HBEDS normalizes hospital bed-capacity data into the required NHSN model with validation around OrgID, Context, ReportingStatus, CollectionDate, and ExtractionDate.
Streamlined onboarding
A staged onboarding flow guides every hospital through discovery, source assessment, mapping, interface build, and monitored production readiness.
Operational visibility
Admins can provision hospitals, track integration health, review validation events, and manage platform users without relying on ad hoc spreadsheets.
Automated onboarding flow
Discovery intake
Capture the hospital legal name, NHSN OrgID or CMS CCN, facility scope, technical and operational contacts, EHR landscape, transport capability, source extract ownership, cadence, and cutover constraints before build work starts.
Source assessment
Validate how staffed and occupied beds are actually calculated, identify the source of record, confirm refresh timing, and document adult/pediatric, ICU, closure, and surge logic with evidence.
Mapping design
Turn local hospital categories into an approved HBEDS mapping specification with confidence levels, rationale, and explicit handling for ambiguous or unsafe classifications.
Interface build
Implement the selected FHIR, API, or SFTP adapter, run schema and business-rule validation, persist canonical records, and prove monitoring is active before testing.
Go-live and monitoring
Track fresh submissions, stale snapshots, validation outcomes, outbound NHSN transmissions, and audit history so the hospital remains supportable after activation.
HBEDS platform scope
Detailed functionality mapped to the onboarding and reporting requirements
HBEDS is designed for near real-time hospital bed-capacity reporting to jurisdiction systems and NHSN. The platform supports JSON-based submission and preserves the exact data semantics required for the official bed-capacity model.
- Pre-validates hospital identity through NHSN OrgID and supports multi-context reporting with the NHSN Context field.
- Supports `ReportingStatus` values such as ActiveCMS, ActiveNoCMS, Test, and Inactive.
- Captures CollectionDate and ExtractionDate to preserve source timing and downstream traceability.
- Supports hospital-to-jurisdiction collection as frequently as every 15 minutes and outbound NHSN submission at least every 3 hours with hourly snapshots.
- Implements the required distinction between 0, null, and 9999 so dashboards do not confuse true zeroes, missing values, and non-offered services.
- Includes staffed and unblocked inpatient beds while excluding virtual locations, blocked beds, and beds no longer in use.
Mapping management workbench
Admin-facing controls for released mappings, review workflows, and release governance
Design and review
- Filter source-field mappings by hospital, source system, transport, version, and approval status.
- Review bed-type rules with local match criteria, canonical targets, and effective dates side by side.
- Inspect snapshot aggregation rules as released runtime configuration instead of tracing Java rollups.
Release operations
- Publish and inspect mapping releases per hospital and source system with an explicit active version.
- Compare draft mappings with the released runtime set before cutover or rollback.
- Export current released mapping packages for implementation review and audit evidence.
Admin APIs
- `/sourcefieldmapping/released` for runtime source-field mappings.
- `/bedtypemapping/released` and `/snapshotaggregationrule/released` for released bed and aggregation rules.
- `/mappingrelease/active` for the currently promoted mapping version in production.
Built for hospital onboarding at scale
HBEDS replaces fragmented spreadsheets and email-based onboarding with one structured SaaS workflow for implementation, validation, and operational support.
Talk to our teamPlatform stack
- React administration console
- Java REST API and onboarding services
- PostgreSQL operational data model
- FHIR, API, and SFTP ingestion adapters
- Canonical bed-status transformation pipeline
- JSON-based NHSN submission workflow
- Audit logging and raw payload archive
- Monitoring metrics and scheduled health checks
Admin capabilities
- Set up a new hospital with legal identity, NHSN OrgID, CMS CCN, facility type, timezone, and active status.
- Create one or more hospital contexts for facility-within-facility reporting such as HOSP, IRF, IPF, CHLD, or OTH.
- Record hospital technical and operational contacts, escalation paths, and support availability.
- Register source systems with vendor, product version, middleware, transport method, endpoint details, and refresh interval.
- Manage onboarding status across discovery, mapping, testing, active, paused, and failed integration states.
- Add platform users and assign roles such as `cdph_admin`, `cdph_user`, `authorized_partner`, `hospital_user`, `contractor_admin`, `contractor_support`, and `auditor`.
- Grant hospital-specific access to users and preserve audit logs for changes, submissions, and alerts.
Status and governance
- Freshness monitoring for stale snapshots and slow hospital feeds.
- Validation events and evidence-backed stage approvals.
- Submission batches, raw payload archive, and canonical record persistence.
- Platform-user management with role-based access and MFA state.
- Transport-aware workflows for FHIR, API, and SFTP integrations.