Krick Fire
We're a software development studio based in Rajasthan, India, registered under GST and Udyam (MSME). We're the team building the product below.
About Us
We're a software development studio based in Rajasthan, India, registered under GST and Udyam (MSME). We're the developer of record for DigiParivarHealth. The product is in active development right now, and we're working through the process of integrating with the Ayushman Bharat Digital Mission (ABDM) sandbox for testing.
Our Product
DigiParivarHealth
We built DigiParivarHealth to solve a problem a lot of Indian families deal with every day: adult children trying to manage their parents' healthcare from another city. Appointments, medications, lab reports, insurance, emergencies, all of it, usually spread across paper files with no single place to see the full picture. The app is offline-first, meaning it keeps working with encrypted local storage and syncs in the background, so it holds up even in the low-connectivity areas common across Tier 2 and Tier 3 India.
It comes as two connected apps built from one codebase.
Patient & Caregiver App
- A digital health vault for prescriptions, lab reports, discharge summaries and immunization records
- Medication tracking and reminders
- Appointment booking and video consultations
- Vitals and wellness tracking, like cycle, sleep and activity
- Lab test booking with report delivery
- Health insurance premium management
- Emergency SOS that shares your location with family contacts
Doctor & Clinic App
- Clinic management for admins, doctors, reception and pharmacy staff
- Electronic prescriptions and OPD queue management
- Doctor availability, scheduling and video consultations
- Pharmacy dispensing and inventory
ABDM Integration
Why we are integrating with ABDM
We want a patient's health records to travel with them, not stay locked inside our app. That means connecting with India's national digital health ecosystem so records are portable across the hospitals, labs and clinics people actually visit. We're requesting sandbox access for:
- M1: ABHA creation and verification
- M2: Storing and sharing records as a Health Information Provider
- M3: Accessing records with consent as a Health Information User
- M4: Provider and facility registry integration, HPR and HFR
- HSPA: Registering as a Health Services Provider Aggregator
- EUA: Electronic User Authentication for logging patients in with their ABHA
- Health Locker: Long-term storage of a patient's health records
- PHR App: A personal health record experience where patients manage their own data
Here's what that looks like in practice. The Patient & Caregiver app acts as a Health Information Provider (HIP). When a caregiver or patient adds a record, like a prescription, lab report or discharge summary, it gets linked to the patient's ABHA address and only shared with other facilities if the patient explicitly consents. The Doctor & Clinic app acts as a Health Information User (HIU), so a doctor can ask for consent to view a patient's existing records from other ABDM-linked facilities before a consultation.
Beyond the core HIP and HIU flows, we're also requesting access as a Health Services Provider Aggregator (HSPA), so patients can use ABHA-based sign in (EUA) across the app, keep a long-term Health Locker of their records, and use the app as a full PHR experience for managing their own health data directly.
Compliance
Compliance & data handling
- All data stays in India, hosted on Supabase Postgres in the Mumbai region
- FHIR R4 is our clinical data standard for every health record
- We follow the DPDP Act 2023: explicit consent, minimal data collection, and the right to access or erase your data
- Data is encrypted at rest, on the device and the database, and in transit over TLS 1.3
- We never put protected health information in logs, analytics or crash reports