March 2026 marked a shift from stabilization to operating intelligence.
CARE HMIS at Sree Sudheendra Medical Mission Hospital had been live for two months and was now functioning without continuous hands-on support. Kerala CARE had completed a year of statewide palliative care operation and was entering a phase where governance, dashboards, responsibility structures, and data quality mattered as much as basic adoption.
The March work therefore focused on the systems that make live deployments governable: scan-based check-in, queue visibility, pharmacy usability, LOINC mapping, analytics pipelines, hospital dashboards, and role hierarchy across the palliative grid.
Independent hospital operation
At Sree Sudheendra, teams were able to manage day-to-day workflows independently. The CARE team continued to provide refresher training and targeted support, but the hospital was no longer dependent on continuous handholding for routine activity.
Feature updates were driven by live feedback from doctors and nursing staff. Management teams collaborated with the CARE team to refine reports and dashboards. Sudheendra-specific documentation and process-flow videos were started to make onboarding and workflow consistency more durable.
This stage is important because it changes the implementation relationship. The deployment team is no longer merely helping users survive the system. It is helping the institution improve through the system.
Scan-based check-in and queue clarity
March introduced QR-based patient scanning and appointment status validation directly within the encounter header.
For front-desk and nursing workflows, this reduced manual search effort and made patient check-in faster. In high-volume hospital settings, even a few saved clicks per patient compound into shorter queues and less staff fatigue.
Queue management also improved through clearer token status indicators, contextual tooltips for queue actions such as "call next patient," and mobile-optimized queue and appointment layouts. These improvements made the system easier to operate from tablets and phones, reflecting how staff actually move through hospital spaces.
The patient flow model was becoming more precise: appointments, tokens, encounters, queues, and service points were being linked in ways that supported real-time movement.
Billing, pharmacy, and procurement visibility
The billing layer gained faster billing from prescription queues, allowing staff to initiate billing for individual prescriptions directly. Discount rules became configurable at the system level, improving governance over pricing behavior.
QR code generation and invoice printing became more reliable, with loading indicators and formatting fixes. Billing navigation and charge item interactions were improved to make live workflows more predictable.
Pharmacy and inventory gained pack-size display, clearer out-of-stock representation, better stock display logic, and total purchase value in purchase delivery screens. The total delivery value helped storekeepers reconcile deliveries with vendor bills.
These are small controls with large operational value. They reduce ambiguity at the exact points where hospitals lose time: pharmacy counters, billing desks, store rooms, and reconciliation reviews.
Clinical context and documentation
March added a clear visual indicator for deceased patients in patient information views, reducing the risk of unintended actions on inactive records.
Diagnostic report clarity improved through better reference-range display. Service request cards gained more clinical context, including body site and patient instructions. Camera-based consent capture allowed staff to upload consent forms directly from a device camera, reducing friction in clinical documentation.
The team also created new report templates and discharge summaries based on doctor and management requirements. This is a recurring CARE pattern: the system becomes more useful when generic infrastructure is translated into the specific documents clinicians and administrators actually need.
LOINC mapping and interoperability
The Sudheendra deployment began mapping lab orders to LOINC codes.
This is a technical detail with long-term importance. LOINC mapping helps standardize lab activity definitions, making diagnostic data more interoperable and analytically useful. Alongside earlier SNOMED CT work and FHIR-aligned lab resources, it strengthens CARE's ability to produce structured health data rather than local-only records.
For a platform intended to support multiple hospitals and public health programs, standards are not branding. They are what keep data portable as deployments multiply.
Dashboards as an operating layer
March expanded analytics across both palliative and hospital deployments.
For palliative care, the Activity Dashboard gained cards tracking first virtual and home health encounters. The definition of "Active Patients" was updated to include patients with encounters in the past 100 days or appointments scheduled in the next 100 days. Appointment distribution dashboards tracked bookings and check-ins per user across zones, with completed encounters across home health and virtual care.
Public dashboard updates added cards such as patients in consultation, home visits, and telehealth sessions booked and checked in. Facility dashboards gained metrics for new registrations, live patients, demographic breakdowns, volunteer linkage, mobility status, nursing and doctor statistics, care coverage, procedures, diagnoses, data quality indicators, volunteer visits, and referrals.
For the hospital, the team built automation to extract data from Metabase and structure it into a dedicated database for hospital-specific reporting. Pharmacy, finance, sales, daily operations, purchase, sales return, and doctor-wise charge item dashboards improved visibility into clinical and financial performance.
CARE was becoming not only the place where work happened, but the place where work could be reviewed.
Responsibility from state to ward
Kerala CARE also advanced governance structure.
On 9 March, a state review at IMA Kochi gathered feedback from district and NHM representatives after a year of usage. On 24 March, the team met the State Mission Director of NHM to review progress and align priorities.
The responsibility feature was completed to manage roles and hierarchy from state to ward level. This allows structured control over access and accountability across administrative levels.
For statewide public health programs, this kind of hierarchy is essential. Without it, dashboards can show data but cannot create clear responsibility for action.
Operational intelligence became the next platform layer
March's work pushed CARE into a more demanding product layer: operational intelligence.
Can a hospital check patients in faster? Can pharmacy billing happen from the prescription queue? Can a storekeeper reconcile delivery value against a vendor bill? Can lab orders map to LOINC? Can dashboards expose data quality issues? Can state, district, facility, and ward roles be represented in the software?
These are not launch questions. They are infrastructure questions. CARE was now operating in that deeper layer.