The NIK Field Is the Thread That Holds Everything Together
Indonesia's NIK — Nomor Induk Kependudukan — is the national population registration number. Every Indonesian citizen has one. In a COVID-19 case management database, the NIK field does more work than any other: it cross-references the patient against the national civil registry, prevents duplicate case entries for the same individual across different reporting periods, and anchors every subsequent contact trace to a uniquely identified person rather than a name that might appear three different ways across three different data sources.
This is what the Dumai DINKES contact tracing template gets right at the structural level. The patient record is not just a case. It's an identified individual — NIK, date of birth, age in years and months, address broken down to RT (neighborhood unit) and kelurahan (urban ward) level — with every downstream epidemiological event attached to that identity.
What Gets Logged When a Case Is Confirmed
The confirmation date (Tgl.Terkonfirmasi) anchors the case in the transmission timeline. The spread status field (Status Penyebaran) classifies the individual into one of four epidemiological categories: Suspect, Kontak Erat (close contact), Probable, or Screening. These are not informal labels — they correspond to the Ministry of Health classification protocol, and the distinction determines isolation protocols, testing priority, and how the case gets counted in district-level reporting.
The Kontak Erat field is a free-text field capturing the identity of the close-contact source — who this person was in contact with when transmission likely occurred. In an active tracing workflow, this field drives the next wave of case searches. Health history (Histori Kesehatan) captures whether the patient is still under treatment (Masih Dirawat) or has recovered (Sudah Sembuh), with a separate recovery date field (Tgl. Sembuh) that allows precise calculation of case duration.
Isolation logistics are captured in Tempat Isolasi — the assigned isolation facility, whether home, a community isolation center, or hospital. Combined with the residential address fields and the Peta Rumah location field, which stores a GPS pin for the patient's home, officers in the field could map active cases and isolation compliance spatially across the kecamatan and kelurahan grid.
When the Cluster Becomes Visible in the Data
By the third week of an active cluster, a database structured this way allows the epidemiology team to filter confirmed cases by kelurahan and cross-reference the Kontak Erat entries. When fifteen entries in Kelurahan A all point back to the same source name in the close-contact field, that source becomes the index case for a cluster investigation — regardless of whether that person was ever logged as a confirmed case themselves.
Filtering by confirmation date against recovery date across an active RT identifies households where duration exceeds the expected isolation period, flagging cases for follow-up visits. The phone number field (No. Telp/Hp) and the GPS home pin both go to the same place — a field officer with a motorcycle and a daily visit list.
The template was built for Dumai's specific administrative geography, with address fields matching the RT/kelurahan/kecamatan hierarchy that local health officers use operationally. That specificity is exactly why it works under pressure.