MeDcZONEMeDcZONE — Client Requirements Intake
Secure client intake form
اللغة / Language:
MeDcZONE

MeDcZONE

Clinical Management Platform

Document Ref.

MDC-PRICING-INTAKE-2026

Client Requirements & Pricing Intake Questionnaire

This questionnaire captures every factor that shapes the final commercial proposal for the MeDcZONE platform — facility footprint, module scope, user population and patient volume (which drive the capacity-sizing and hardware bill of materials), integration scope, deployment model, branding, data migration, compliance, training, support and licensing. Kindly complete each section as fully as possible; fields marked with an asterisk (*) are required to produce a priced Scope of Work, Datasheet and Capacity Sizing document. Attach supplementary material (RFP, network diagrams, legacy system exports) where indicated.

How to complete

Fill each field directly. Tick the boxes that apply. Where a value is not yet known, enter “TBD” rather than leaving the field blank — a TBD is still a valid answer and lets us flag the assumption in the proposal.

Section 1

Organization & Facility Footprint

The number, type and geography of sites is the primary driver of licence scope, implementation effort and the hardware bill of materials.

1.1

Tick all that apply across the licensed estate

1.2
1.3
1.4

One row per site: name, city, type, beds, OR rooms, pharmacy outlets

NameCityBedsORsPharm.

Section 2

Clinical & Operational Module Scope

The platform is licensed as one perpetual right covering all applications; however, the modules in active scope define implementation effort, training and support sizing.

2.1

Tick every module that must be live in Phase 1

2.2
2.3

Specialty clinical workspaces layered on the shared encounter spine

2.4

Section 3

User Population & Patient Volume — Sizing Inputs

These figures feed the Capacity Sizing module: application tier, database tier, object storage, caching, realtime and network sizing. Provide current, design and peak where possible.

3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11

Volumes that must be imported before Go-Live — patient records, encounters, imaging (DICOM), documents

Section 4

Integrations & Interfaces

Each external interface carries design, build and test effort. Indicate the systems, the standard and the direction.

4.1
4.2

For each integration: system name, standard (HL7 v2.x / FHIR / DICOM / REST), inbound or outbound

SystemStandardDirectionNotes
4.3

Section 5

Deployment & Hosting

The deployment model affects infrastructure cost, support model and data-residency obligations.

5.1
5.2
5.3
5.4
5.5
5.6

Section 6

Branding, Website & Mobile Application

The platform is delivered under the client’s brand across web and mobile, with bilingual content configuration.

6.1
6.2
6.3
6.4
6.5
6.6

Section 7

Data Migration & Legacy Systems

Migration scope is priced by volume, source-system complexity and the cleansing/mapping effort required.

7.1
7.2
7.3
7.4

Section 8

Compliance & Regulatory

Accreditation and regulatory requirements drive configuration, audit logging and document-template work.

8.1
8.2
8.3

Section 9

Training & Implementation

Implementation effort is driven by the number of sites, the number of staff to train, and the go-live model.

9.1
9.2
9.3
9.4
9.5
9.6

Section 10

Support & SLA

The licence includes 12 months of coverage from Go-Live. Extended coverage and SLA tiers beyond that are priced separately.

10.1
10.2
10.3
10.4
10.5

Section 11

Commercial & Licensing

These inputs frame the commercial structure of the proposal.

11.1
11.2
11.3
11.4
11.5
11.6

Section 12

Timeline & Milestones

Milestone targets let us sequence the proposal and validate feasibility against the implementation plan.

12.1
12.2
12.3
12.4
12.5

Section 13

Attachments & Additional Notes

Supplementary material reduces assumptions and sharpens the proposal.

13.1
13.2
13.3