CureMD

Discovery and planning (2–4 weeks)

Kick-off meeting to define goals, workflows, and success metrics.

Collect current process maps, patient flow, charting conventions, billing rules, payer mix, and security/compliance requirements.

Confirm user roles, specialties, locations, and integration needs (labs, imaging, EHR incentives, payer portals).

Define project milestones, go-live date, data migration scope, and change management plan.

System design and configuration (4–8 weeks)

Build and customize templates for encounters, progress notes, orders, e-prescribing, and population health dashboards.

Configure practice rules: billing/coding defaults, claim scrubbing rules, payer-specific requirements, ICD-10/ CPT mapping, and denial management workflows.

Set up user roles, security groups, access controls, audit trails, and role-based dashboards.

Establish workflows for scheduling, registrations, consent capture, and telehealth if included.

Data migration and testing (2–6 weeks)

Migrate patient demographics, history, lab results, medications, and outstanding encounters from legacy systems.

Cleanse and validate data; perform test runs for scheduling, documentation, eRx, orders, and billing.

End-to-end testing: user acceptance, scenario testing for typical and edge cases, and concurrent processing checks.

Training and change management (2–4 weeks)

Hands-on training sessions for clinicians, billers/cagers, and admins.

Training materials, tip sheets, and sandbox environment access.

Go-live readiness assessments and contingency plans.

Deployment and go-live (0–2 weeks)

Phase-in go-live (e.g., pilot departments first) or full organization switch.

Post-live support window with on-site or remote assistance, quick-reference guides, and check-ins.

Optimize workflows based on real-world usage and feedback.

Stabilization and optimization (ongoing)

Ongoing optimization of templates, orders, and billing rules.

Regular health checks, performance optimization, and security/compliance reviews.

Periodic updates and feature rollouts as CureMD releases.

Documentation templates: encounters, progress notes, discharge summaries, discharge instructions.

Order sets and smart phrases (macros) for faster data capture.

Billing and coding rules: payer-specific requirements, claim edits, auto-attachments, and denials workflows.

Scheduling and patient flow: appointment types, reminders, block scheduling, and multi-location calendars.

Security and roles: granular access controls, user permissions, audit reporting.

Dashboards and reporting: KPI dashboards, population health metrics, payer performance, revenue leakage indicators.

Patient portal: patient education materials, appointment requests, secure messaging, e-consents.

Interfaces and integrations: lab feed, imaging results, eRx, RxHub, HIEs, and practice management integrations.

Custom workflows: referral routing, discharge process, prior authorization steps, and denial management paths.

Clinical decision support: alerts for drug interactions, allergies, preventive care reminders.

Setup/implementation fees

One-time implementation/configuration fee is common and varies by scope.

For small practices, typical ranges might be in the low to mid five figures (e.g., $15,000–$40,000+),

depending on:

• Number of users and locations.

• Data migration complexity.

• Custom templates and workflows.

• Required integrations and interfaces.

• Training depth and go-live support.

Software licensing and per-user costs

CureMD generally operates on a subscription/licensing model with per-user or per-provider pricing, plus potential monthly or annual fees.

Pricing is often tiered by role (clinicians, administrative staff, billers) and feature bundles (clinical, financial, patient portal, analytics).

Data migration and activation charges

Some contracts include data migration as part of the implementation, while others bill separately depending on data volume and cleansing needs.

Maintenance and support

Ongoing maintenance and support fees are typically annual and may be a percentage of license/subscription cost (e.g., 15–25% per year) or a fixed annual fee.

Support levels vary (basic, standard, premium) and determine response times, access to a dedicated CSM, and on-site support options.

Costs can depend on:

• Level of support (24/7 vs business hours)

• Access to updates/upgrades

• Training refreshes and ongoing education

• Availability of a dedicated customer success manager

Custom development and integrations

Some integrations may incur per-transaction or per-connection costs with third-party vendors.

Connectivity and networking (vpn, secure data transfer).

Role-based onboarding: tailored sessions for clinicians (physicians, NPs, PAs), nurses, billers/coders, schedulers, and admins.

Training modalities: a mix of live instructor-led sessions, self-paced e-learning modules, and hands-on practice in a sandbox/test environment.

Curriculum coverage: core EHR documentation (notes, orders, e-prescribing, charting), practice management workflows (scheduling, registrations, billing), patient portal usage, and basic reporting/dashboards.

Specialty training: templates, order sets, and workflows customized for the user’s specialty (e.g., pediatrics, cardiology, dermatology) when available.

Training materials: user guides, quick reference cards, video tutorials, and searchable help within the system.

Change management and adoption support: guided go-live plans, change-readiness assessments, and communication/templates to help with workflow transitions.

Train-the-trainer option: facility-super users who receive deeper training to support ongoing staff.

Go-live coaching: on-site or remote go-live support during the initial rollout window, with intensified support for the first days/weeks.

Ongoing learning: periodic refresher sessions, new feature trainings when releases occur, and access to a customer support portal with knowledge base.

Access control and identity management: role-based access controls (RBAC), least-privilege principles, and strong authentication options (potentially including SSO and MFA).

Data encryption: encryption at rest and in transit for patient data; secure transmission protocols (e.g., TLS) for data exchanges.

Audit trails and logging: comprehensive activity logs tracking user access, modifications, and administrative actions for accountability and compliance.

Regulatory alignment: designed to support HIPAA compliance, with policies and procedures to protect electronic protected health information (ePHI).

Data segmentation and privacy: controls to segment data by patient, location, and user role; consent management mechanisms where applicable.

Backup and disaster recovery: regular backups, defined RPO/RTO targets, and tested disaster recovery plans.

Vendor and data protection controls: third-party risk assessments, secure interfaces, and documented data handling practices.

Release cadence: CureMD generally follows a regular update cycle that may include minor updates (patches), feature enhancements, and periodic major releases. Frequency can range from monthly to quarterly for non-disruptive improvements; major releases might occur a few times per year.

Update management: updates are typically tested in a staging or sandbox environment before production deployment; release notes are provided outlining new features, enhancements, bug fixes, and any configuration changes required.

Customer impact: CureMD typically aims to minimize downtime; updates may be scheduled during off-peak hours or communicated in advance with a rollback plan if issues arise.

Customizations and upgrades: heavy customization can affect upgrade paths. CureMD or the partner will advise on any needed changes to custom templates, workflows, or integrations to ensure compatibility with new releases.

Data ownership

• In typical contracts, the customer owns the data that it generates and stores in CureMD (clinical records, billing data, schedules, patient demographics, etc.).

• CureMD acts as a data processor/host for the customer’s data under the terms of the service agreement.

• CureMD generally reserves rights to data usage for system operation, support, analytics, and product improvement only as permitted by the contract and applicable law.

Data access and export rights

• You should expect structured export rights to retrieve your data upon request, often in common formats (e.g., CSV, HL7 FHIR exports, CCD/CDA exports for clinical data, or ADT feeds for demographics).

• Some contracts include a defined data extract window and a data escrow or transitional data availability period post-termination.

• Availability of patient-level data for migration to another system, subject to any vendor-specific constraints (e.g., ongoing obligations, fees for data extraction, or retained copies for compliance).

Data portability and transition

• CureMD typically supports data migration out via standard formats or APIs, but the ease and cost can depend on data scope (history depth, attachments, imaging, external documents).

• For multi-tenant setups or specific integrations, ensure there are clear data migration plans, timelines, and responsibilities during transition.

Scalability options

• CureMD typically offers tiered pricing and licensing that can scale with the number of providers, staff, locations, and modules.

• Add-on modules (e.g., advanced analytics, population health, telehealth) can be activated as needed; similarly, modules can be deactivated or removed if no longer required.

Process to scale

• Flexible provisioning for new locations, additional clinicians, or support staff is common, but you should confirm lead times, onboarding costs, and any minimums.

• Data migration and interoperability considerations should be discussed when scaling, especially for new locations or specialties.

• SLA and support impact: confirm how scaling affects support SLAs, training requirements, and implementation effort.

Costs and negotiation points

• Clarify whether scaling incurs one-time professional services fees or ongoing per-user licensing changes

• Confirm any minimum commitment terms for the initial contract and what the terms are for mid-term expansions or contractions.

Renewal terms

• Most CureMD contracts renew annually or per-term (e.g., 2–3 years) with automatic renewal unless cancelled within a specified window.

• Price escalation: expect potential annual or per-entity price escalators, with disclosures of cap or percentage increases.

• Renewal notices: there is usually a required notice period (e.g., 60–180 days) before renewal to renegotiate terms or cancel.

Cancellation and termination

• Termination for convenience vs. termination for cause: many contracts allow termination for cause (breach) with cure periods; termination for convenience is less common and may require penalties or fees.

• Exit assistance: contracts often include a transition/post-termination period during which CureMD assists with data export and knowledge transfer.

• Data return and deletion: upon termination, you typically have a window to export data; after that period, CureMD may purge data in alignment with retention policies, subject to contractual obligations.

• Outstanding payments: termination usually requires settlement of any outstanding invoices; there may be early-termination fees if a fixed-term commitment was signed.

• Migration assistance: some contracts include a limited period of free or discounted migration support to another system, though this is not guaranteed.

Hidden/implicit terms to confirm

• Any minimum commitment terms or penalties for early termination.

• Fees related to data export, system decommissioning, or reverting to a legacy system.

• Requirements around returning hardware, if applicable, or decommissioning of interfaces and integrations.

HIPAA: ePHI protection, access controls, audit logs, breach notification, and BAAs.

HITRUST: many healthcare IT vendors pursue HITRUST CSF alignment or certification; verify current status for CureMD or your region.

SOC 2/ISO 27001: security and operational controls related to data processing and service organization controls; some CureMD deployments reference these reports.

PCI DSS: relevant if CureMD handles payment card data (for integrated payment or e-payments)

Industry-appropriate privacy laws: state privacy laws (where applicable), and any regional data residency requirements if applicable.