A spine surgeon operating across ten hospitals in a single region carries a financial complexity that most billing systems are not designed to handle. The fee structure for a TLIF at one hospital is different from the same procedure at another. The implant arrangement — whether the hospital supplies and pays for the implant, or whether the surgeon's own supply chain is engaged — varies by facility agreement and by case. PMJAY packages have fixed rates that diverge from TPA reimbursements for identical diagnoses. Tracking what is owed, from whom, and why, cannot be delegated to memory.
The Tag Architecture and Why It Isn't Redundant
The template carries five separate multichoice tag fields: Tags Scoli TB Kyphosis, Tags Tb Tumour Trauma Lysthesis, Tags Osteoporosis, Tags Disc LCS, and Tags Cervical. At first reading this looks like a poorly normalized data structure — overlapping categories, repeated procedure tags across fields. It isn't.
Each tag field maps to a diagnostic cluster that drives a distinct surgical technique family. The Scoli/TB/Kyphosis field captures correction surgery options: AIS, congenital scoliosis, PSO, VCR, Pontes, anterior column reconstruction, selective thoracic fusion. These tags help reconstruct what was actually done years later when a patient presents for revision. Was it a selective thoracic fusion or a lumbosacral extension? Was VCR performed, or just Pontes osteotomies? The procedure description in text is fallible. The structured tags are queryable.
The Cervical tag field covers ACDF, ACCF, lateral mass screws, laminoplasty, laminectomy, C1C2 screws, occipital cervical fusion, cervicodorsal extension, and traction. These are not duplicates of the Diagnosis field — they are the technique-level specifics beneath a cervical spine injury or cervical degenerative diagnosis. A patient with CRANIOVERTEBRAL diagnosis could have C1C2 screws only, or occipital cervical fusion extending to C5, or both combined. The tag captures it; the diagnosis field alone cannot.
Implant Charges as a Separate Financial Line
The separation of Amount due to me (exclusive of implant) from Implant charges due is the financial structure that most surgeon billing systems collapse into a single figure — and that collapse is where disputes originate. Each field has its own Break Up account and Break up of Implant charges text field for itemization.
The Other details of Payment checkboxes — Hospital will pay for Anaesthesia, Hospital will pay for Assistant, I will pay for Implant, and so on — are the agreement terms captured at case level. Hospital payment arrangements change. A facility that previously covered assistant fees stops doing so after a management change. If the agreement isn't recorded per case, disputes about who committed to what six months ago become irresolvable.
The Type of Payment field (Cash, TPA, PMJAY, CMF) determines the reimbursement pathway and affects the expected timeline for collection. A PMJAY case has a government-defined package rate and a specific authorization and claim cycle. A TPA case depends on pre-authorization status and the insurer's processing speed. Cash cases settle differently again. These are not equivalent payment types with the same follow-up strategy.
The Bill Image and the File Link
The Bill image field captures the physical hospital bill — the document that shows what the hospital actually charged the patient, against which the surgeon's fee components must reconcile. For TPA cases, this is the document submitted to the insurer. For disputed payment cases, this is the primary evidence.
The Images folder file link field handles the imaging archive — the pre-op MRI, the intra-op X-ray, the post-op check films — by linking to a device folder rather than embedding images in the database record. For high-volume spinal surgery, embedding full imaging into each record creates a database size problem. The file link solution keeps the case record lean while preserving the connection to the imaging set.
Clinical Records as a linked entries field connects the main case record to a separate clinical log library — follow-up notes, post-op reviews, complication flags — without duplicating the surgical case data in every follow-up entry.