Rare disease software manages the whole patient journey for conditions with small, dispersed populations — registry, diagnosis, treatment and infusion tracking, drug inventory and long-term reporting. iCare is our platform for it, in production for a government rare disease programme covering haemophilia, thalassemia and sickle cell.
What rare disease software has to do
Rare disease programmes break the assumptions that ordinary hospital software is built on: patients are few, they are spread across many centres, treatment is episodic and expensive, and the drug itself is often in short supply. A working system has to cover:
Patient registry — enrolment, diagnosis data, genotype and phenotype records, consent state, and a longitudinal history that survives staff turnover.
Treatment and infusion tracking — scheduled and actual doses, product batch, reactions and adherence, with the clinical record updated as treatment happens.
Drug and inventory management — demand forecasting against a constrained supply, batch and expiry control, cold-chain status, and stock visibility across centres.
Clinical workflows — approvals, escalations and the specific forms each programme requires, without the team re-keying data into a second system.
Reporting — cohort outcomes, consumption versus allocation, and the compliance reports funders and ministries ask for.
Why rare disease programmes need different software
🧩Small, dispersed cohorts
Twenty patients at each of fifteen centres is a normal programme. Software designed for a single hospital census cannot see the whole cohort, which is exactly what clinical decisions and drug planning need.
💉Constrained drug supply
When a product is scarce or cold-chain sensitive, inventory is a clinical constraint. Allocation logic and expiry control belong in the same system as the treatment record.
📊Longitudinal data
Outcomes accrue over years and across clinicians. Registries must stay queryable and auditable long after the person who entered the first record has moved on.
🔒Sensitive data, real obligations
Genetic and paediatric data carries the strictest handling expectations. Access control, audit trails and data residency are design inputs, not add-ons.
iCare: what is in the platform
iCare is our rare disease management platform, in production for a government programme. The modules map to the list above rather than to a generic EMR:
📋Patient registry
Enrolment, diagnosis, genotype and phenotype records, consent state, and full clinical history per patient.
💉Treatment & infusion tracking
Scheduled versus administered doses, product and batch traceability, reactions and adherence tracking.
📦Inventory management
Batch and expiry control, cold-chain status, allocation against demand, and stock visibility across centres.
📊Reporting
Cohort outcomes, consumption reporting and the programme-specific reports funders require.
We describe controls, not certificates. For rare disease deployments the architecture supports:
Role-based access control down to field level, with separation between clinical, pharmacy and administrative roles.
Audited access — every view and edit of a patient record is attributable to a named user.
Encryption in transit and at rest, with configurable data residency for jurisdictions that require it.
Deployment options from managed cloud to private infrastructure inside your own network.
Backup, retention and de-identification procedures documented per programme.
If your procurement requires HIPAA, ABDM, GDPR or local health-data alignment, we will map the controls to the specific clause list during discovery — and say plainly where a control is not yet in place. See also our healthcare software development practice.
Who this is for
Government health programmes running national or state rare disease registries and drug allocation.
Hospitals and treatment centres that need to feed one cohort registry from several clinical sites.
Patient foundations and advocacy groups that maintain their own registry and outcome data.
Pharma and life-sciences teams that need real-world evidence and post-authorisation follow-up infrastructure.
Frequently asked questions
Rare disease software manages the complete journey of patients with conditions that affect small, geographically dispersed populations — registration and diagnosis, treatment and infusion scheduling, drug inventory, and long-term outcome reporting. Because the patient cohort is small, the software has to work across many sites rather than at one hospital.
iCare is SoftEdge’s rare disease management platform. It covers patient registry, treatment and infusion tracking, drug inventory, clinical workflows and reporting, and it is deployed in a government rare disease programme covering haemophilia, thalassemia and sickle cell.
The platform is configured per programme. It is in production for haemophilia, thalassemia and sickle cell disease, and the same registry, treatment and inventory model applies to other inherited and chronic rare conditions where treatment is episodic and drug supply is constrained.
iCare is built with a HIPAA-ready architecture: role-based access control, encrypted data at rest and in transit, audited access to patient records, and configurable data residency. Compliance is a property of the deployment, so we document the controls in place for your specific environment rather than making a blanket certification claim.
Through a phased interoperability roadmap rather than a big-bang integration. Programmes typically start with controlled import and export (CSV and HL7-style messages), then add FHIR resources where the receiving system supports them and where ABDM or national programme requirements call for it.
Yes. Registries are configured per condition and per programme: consent and enrolment rules, treatment protocols, inventory thresholds, approval workflows and the exact reports your ministry, funder or ethics committee requires.