{"id":24001,"date":"2026-08-12T06:41:10","date_gmt":"2026-08-12T06:41:10","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=24001"},"modified":"2026-08-12T06:41:10","modified_gmt":"2026-08-12T06:41:10","slug":"lims-software-development","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/lims-software-development\/","title":{"rendered":"How to Build a Laboratory Information Management System (LIMS), Sample Tracking, Results Management, 21 CFR Part 11, and Lab Analytics 2026"},"content":{"rendered":"

Laboratories are among the most data-intensive environments in science and healthcare.<\/span><\/p>\n

A pharmaceutical quality control lab running 500 tests per day generates 500 sample records, thousands of individual test results, calibration records for every instrument used, stability study data for every batch released, and a complete audit trail linking every result to the analyst who generated it and every instrument used to produce it.<\/span><\/p>\n

Managing this through paper and spreadsheets is not just inefficient, it is a regulatory violation waiting for its inspection moment.<\/span><\/p>\n

A LIMS Software Development manages every sample from the moment it enters the laboratory through testing, results review, reporting, and archiving, with the complete audit trail and electronic signature controls that FDA 21 CFR Part 11 and EU GMP Annex 11 require.<\/span><\/p>\n

The global LIMS market is projected to reach <\/span>$3.2 billion by 2030<\/span><\/a> at a CAGR of 7.4%. The buyers are pharmaceutical QC labs, CROs (Contract Research Organisations), environmental testing labs, food and beverage testing labs, clinical diagnostics labs, and research institutions.<\/span><\/p>\n

EngineerBabu<\/span><\/a> built Somnoware, the IoT-connected monitoring platform acquired by ResMed, and healthcare platforms for Apollo Hospitals. CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: <\/span>mayank@engineerbabu.com<\/span><\/a><\/p>\n

\"\"<\/p>\n

What a LIMS Must Handle<\/b><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Function<\/b><\/td>\nModule<\/b><\/td>\n<\/tr>\n
Sample registration<\/span><\/td>\nSample login, barcode generation, chain of custody<\/span><\/td>\n<\/tr>\n
Test management<\/span><\/td>\nTest methods, specifications, SOP links<\/span><\/td>\n<\/tr>\n
Workflow management<\/span><\/td>\nLab workflow, task assignment, prioritisation<\/span><\/td>\n<\/tr>\n
Instrument integration<\/span><\/td>\nData import from lab instruments (HPLC, GC, MS, spectrophotometers)<\/span><\/td>\n<\/tr>\n
Results entry and review<\/span><\/td>\nManual entry, instrument data, supervisor review<\/span><\/td>\n<\/tr>\n
Out-of-specification (OOS) management<\/span><\/td>\nOOS investigation workflow, CAPA<\/span><\/td>\n<\/tr>\n
Stability testing<\/span><\/td>\nProtocol management, time-point tracking, trend analysis<\/span><\/td>\n<\/tr>\n
Certificate of analysis (CoA)<\/span><\/td>\nAutomated CoA generation and release<\/span><\/td>\n<\/tr>\n
Audit trail<\/span><\/td>\nImmutable record of all actions, 21 CFR Part 11<\/span><\/td>\n<\/tr>\n
Electronic signatures<\/span><\/td>\nCompliant e-signatures for results and release<\/span><\/td>\n<\/tr>\n
Calibration management<\/span><\/td>\nInstrument calibration schedule, certificate tracking<\/span><\/td>\n<\/tr>\n
Inventory management<\/span><\/a><\/td>\nReagents, standards, consumables<\/span><\/td>\n<\/tr>\n
Reporting and analytics<\/span><\/td>\nTurnaround time, OOS rate, analyst performance<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Module 1 – Sample Registration and Chain of Custody<\/b><\/h2>\n

The sample lifecycle:<\/b><\/p>\n

Every sample that enters the laboratory gets a unique barcode or QR code at the point of login. This identifier follows the sample through every step, from receipt through testing through reporting through storage or disposal.<\/span><\/p>\n

Sample login data captured:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field<\/b><\/td>\nDetails<\/b><\/td>\n<\/tr>\n
Sample ID<\/span><\/td>\nLIMS-generated unique identifier<\/span><\/td>\n<\/tr>\n
Barcode \/ QR code<\/span><\/td>\nPrinted label applied to sample container<\/span><\/td>\n<\/tr>\n
Sample type<\/span><\/td>\nRaw material, in-process, finished product, stability<\/span><\/td>\n<\/tr>\n
Material code<\/span><\/td>\nItem code linked to product master<\/span><\/td>\n<\/tr>\n
Batch number<\/span><\/td>\nManufacturer’s batch identifier<\/span><\/td>\n<\/tr>\n
Quantity received<\/span><\/td>\nAmount received for testing<\/span><\/td>\n<\/tr>\n
Collection date\/time<\/span><\/td>\nWhen sample was collected<\/span><\/td>\n<\/tr>\n
Received date\/time<\/span><\/td>\nWhen received in the lab<\/span><\/td>\n<\/tr>\n
Condition on receipt<\/span><\/td>\nAcceptable \/ Damaged \/ Non-conforming<\/span><\/td>\n<\/tr>\n
Storage requirement<\/span><\/td>\nAmbient \/ Refrigerated \/ Frozen<\/span><\/td>\n<\/tr>\n
Requested tests<\/span><\/td>\nWhich analyses are required<\/span><\/td>\n<\/tr>\n
Priority<\/span><\/td>\nRoutine \/ Urgent \/ Emergency<\/span><\/td>\n<\/tr>\n
Requesting department<\/span><\/td>\nWhich department or customer submitted<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Chain of custody:<\/b><\/p>\n

Every time a sample changes hands, from receiving to storage, from storage to analyst, from analyst to secondary reviewer, from testing lab to archive, the LIMS records the transfer with the timestamp and the identity of both parties.<\/span><\/p>\n

This chain of custody is required for forensic integrity of pharmaceutical and environmental testing samples.<\/span><\/p>\n

\"\"<\/p>\n

Module 2 – Test Method and Specification Management<\/b><\/h2>\n

The test method library:<\/b><\/p>\n

Every test performed in the laboratory is defined by a validated test method, the procedure, equipment, reagents, acceptance criteria, and calculation that produce a reportable result. The LIMS maintains a library of all validated methods.<\/span><\/p>\n

Test method record:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field<\/b><\/td>\nDetails<\/b><\/td>\n<\/tr>\n
Method number<\/span><\/td>\nUnique identifier, e.g., QC-HPLC-001<\/span><\/td>\n<\/tr>\n
Method title<\/span><\/td>\n“HPLC Assay of Active Pharmaceutical Ingredient”<\/span><\/td>\n<\/tr>\n
Version<\/span><\/td>\nCurrent version, version control tracked<\/span><\/td>\n<\/tr>\n
Effective date<\/span><\/td>\nWhen this version became current<\/span><\/td>\n<\/tr>\n
Applicable products<\/span><\/td>\nWhich materials this method applies to<\/span><\/td>\n<\/tr>\n
Equipment required<\/span><\/td>\nHPLC system, column, detector<\/span><\/td>\n<\/tr>\n
Reagents and standards<\/span><\/td>\nWith grade and concentration<\/span><\/td>\n<\/tr>\n
Procedure<\/span><\/td>\nStep-by-step instructions or SOP reference<\/span><\/td>\n<\/tr>\n
Acceptance criteria<\/span><\/td>\nPass\/fail limits for each parameter<\/span><\/td>\n<\/tr>\n
Calculation<\/span><\/td>\nFormula for result calculation<\/span><\/td>\n<\/tr>\n
Out-of-specification criteria<\/span><\/td>\nWhen a result triggers OOS investigation<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Specification management:<\/b><\/p>\n

Each product or material has specifications, the acceptance limits for every quality attribute. The LIMS stores specifications with versioning, when a specification changes (regulatory update, internal improvement), the new version is effective from a defined date and old results are evaluated against the specification that was current when the test was performed.<\/span><\/p>\n

Module 3 – Instrument Integration<\/b><\/h2>\n

Manual data entry is the most common source of transcription errors in laboratory operations. Instrument integration eliminates manual transcription by importing results directly from analytical instruments into the LIMS.<\/span><\/p>\n

Integration methods by instrument type:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Instrument Type<\/b><\/td>\nIntegration Method<\/b><\/td>\n<\/tr>\n
HPLC \/ UHPLC<\/span><\/td>\nChromatography data system (CDS), Empower, Chromeleon, exports to LIMS via API or file<\/span><\/td>\n<\/tr>\n
GC \/ GC-MS<\/span><\/td>\nSame as HPLC, CDS integration<\/span><\/td>\n<\/tr>\n
UV-Vis spectrophotometer<\/span><\/td>\nDirect instrument API or file export<\/span><\/td>\n<\/tr>\n
FTIR \/ Raman spectroscopy<\/span><\/td>\nSoftware export<\/span><\/td>\n<\/tr>\n
Balance \/ analytical balance<\/span><\/td>\nRS-232 serial connection, direct data capture<\/span><\/td>\n<\/tr>\n
pH meter<\/span><\/td>\nSerial connection or Bluetooth<\/span><\/td>\n<\/tr>\n
Karl Fischer titrator<\/span><\/td>\nDirect instrument interface<\/span><\/td>\n<\/tr>\n
Dissolution apparatus<\/span><\/td>\nDissolution software integration<\/span><\/td>\n<\/tr>\n
ICP-MS<\/span><\/td>\nSoftware export<\/span><\/td>\n<\/tr>\n
Automated clinical analyser<\/span><\/td>\nHL7 interface (for clinical labs)<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The bidirectional instrument interface:<\/b><\/p>\n

A fully integrated LIMS sends work orders to instruments, the instrument knows which sample to test and which method to run. The instrument runs the analysis and sends results back to the LIMS automatically.<\/span><\/p>\n

The analyst confirms the result and releases it for review. Zero manual data entry between instrument and LIMS.<\/span><\/p>\n

\"\"<\/p>\n

Module 4 – Results Review and Out-of-Specification Management<\/b><\/h2>\n

The review workflow:<\/b><\/p>\n

Every result goes through a defined review chain before it is reportable:<\/span><\/p>\n\n\n\n\n\n\n\n
Review Level<\/b><\/td>\nReviewer<\/b><\/td>\nAction<\/b><\/td>\n<\/tr>\n
Level 1, Analyst review<\/span><\/td>\nAnalyst who performed the test<\/span><\/td>\nConfirms result is entered correctly, no obvious errors<\/span><\/td>\n<\/tr>\n
Level 2, Peer review<\/span><\/td>\nSecond analyst<\/span><\/td>\nReviews raw data, calculations, instrument logs<\/span><\/td>\n<\/tr>\n
Level 3, Supervisor review<\/span><\/td>\nLab supervisor<\/span><\/td>\nReviews for compliance with method and specification<\/span><\/td>\n<\/tr>\n
Level 4, QA review<\/span><\/td>\nQuality Assurance<\/span><\/td>\nFinal approval before CoA release<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Out-of-specification (OOS) management:<\/b><\/p>\n

When a result falls outside specification, the LIMS automatically initiates an OOS investigation:<\/span><\/p>\n\n\n\n\n\n\n
Phase<\/b><\/td>\nAction<\/b><\/td>\nTimeline<\/b><\/td>\n<\/tr>\n
Phase I, Lab investigation<\/span><\/td>\nReview for assignable cause (analyst error, instrument malfunction, calculation error)<\/span><\/td>\n24\u201348 hours<\/span><\/td>\n<\/tr>\n
Phase II, Full investigation<\/span><\/td>\nIf no assignable cause, re-testing, root cause analysis, CAPA<\/span><\/td>\n15\u201330 days<\/span><\/td>\n<\/tr>\n
Disposition<\/span><\/td>\nBased on investigation, batch released, rejected, or reprocessed<\/span><\/td>\nPer investigation conclusion<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Every OOS investigation is documented in the LIMS, including the investigation hypothesis, testing performed, conclusion, and the disposition decision. This documentation is the primary evidence in an FDA inspection when a batch was released despite an initial OOS result.\u00a0<\/span><\/p>\n

Module 5 – 21 CFR Part 11 and Electronic Signatures<\/b><\/h2>\n

The audit trail requirements:<\/b><\/p>\n

FDA 21 CFR Part 11 requires that every electronic record in a regulated LIMS have a complete, computer-generated audit trail showing:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
Audit Trail Requirement<\/b><\/td>\nTechnical Implementation<\/b><\/td>\n<\/tr>\n
Who made each entry<\/span><\/td>\nUser authentication, every action linked to authenticated user<\/span><\/td>\n<\/tr>\n
What was entered or changed<\/span><\/td>\nBefore and after values captured for every modification<\/span><\/td>\n<\/tr>\n
When the action occurred<\/span><\/td>\nUTC timestamp on every record<\/span><\/td>\n<\/tr>\n
System-generated entries<\/span><\/td>\nCannot be modified by users<\/span><\/td>\n<\/tr>\n
Tamper evidence<\/span><\/td>\nAudit trail records stored in append-only manner<\/span><\/td>\n<\/tr>\n
Archived<\/span><\/td>\nAudit trail maintained for the lifetime of the records<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Electronic signatures:<\/b><\/p>\n

For regulated LIMS, electronic signatures must be:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
Requirement<\/b><\/td>\nImplementation<\/b><\/td>\n<\/tr>\n
Linked to the individual<\/span><\/td>\nCannot be reused or reassigned<\/span><\/td>\n<\/tr>\n
Unique<\/span><\/td>\nNo two individuals share the same signature<\/span><\/td>\n<\/tr>\n
Under sole control<\/span><\/td>\nPassword-protected, cannot be delegated<\/span><\/td>\n<\/tr>\n
Manifested at signing<\/span><\/td>\nSignature execution requires password re-entry<\/span><\/td>\n<\/tr>\n
Associated with the signed record<\/span><\/td>\nSignature is permanently linked to the signed record<\/span><\/td>\n<\/tr>\n
Legally equivalent<\/span><\/td>\nTreated as equivalent to a handwritten signature<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

In the LIMS, every review and approval action requires the user to re-enter their password at the point of signing, not just log in at the start of the session. This “intent to sign” step is the key 21 CFR Part 11 requirement that many laboratory systems implement incorrectly.<\/span><\/p>\n

\"\"<\/p>\n

Module 6 – Stability Testing Management<\/b><\/h2>\n

Pharmaceutical stability testing is a long-running, tightly regulated programme, samples stored at defined conditions (temperature and humidity) are tested at defined time points over a period of months to years to demonstrate that the product remains within specification throughout its shelf life.<\/span><\/p>\n

The stability protocol:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n
Element<\/b><\/td>\nDetails<\/b><\/td>\n<\/tr>\n
Product<\/span><\/td>\nWhich product is in the stability programme<\/span><\/td>\n<\/tr>\n
Study type<\/span><\/td>\nReal-time, accelerated, intermediate, stress<\/span><\/td>\n<\/tr>\n
Storage conditions<\/span><\/td>\ne.g., 25\u00b0C\/60% RH, 40\u00b0C\/75% RH, -20\u00b0C<\/span><\/td>\n<\/tr>\n
Time points<\/span><\/td>\n0, 3, 6, 9, 12, 18, 24, 36 months<\/span><\/td>\n<\/tr>\n
Tests at each time point<\/span><\/td>\nWhich analyses are performed<\/span><\/td>\n<\/tr>\n
Batch numbers<\/span><\/td>\nWhich batches are in the programme<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The time-point management:<\/b><\/p>\n

The LIMS tracks every time point for every batch in every stability protocol. When a time point is approaching, typically 7 days in advance, the LIMS alerts the stability coordinator to pull samples from the stability chamber and schedule testing. Missing a time point without documentation is a GMP violation.<\/span><\/p>\n

The trend analysis:<\/b><\/p>\n

For each product attribute over the stability time course, the LIMS calculates a regression line, projecting when the attribute will reach its specification limit at the current rate of degradation. This shelf-life projection supports the product’s expiry date claim and identifies products approaching their re-evaluation date.<\/span><\/p>\n

\"\"<\/p>\n

Build Cost: LIMS Software Development<\/b><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Module<\/b><\/td>\nCost Range (USD)<\/b><\/td>\nNotes<\/b><\/td>\n<\/tr>\n
Sample registration + chain of custody<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\nBarcode printing, receipt workflow<\/span><\/td>\n<\/tr>\n
Test method + specification management<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\nVersion control, product linkage<\/span><\/td>\n<\/tr>\n
Workflow management + task assignment<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\n<\/td>\n<\/tr>\n
Instrument integration (10 instrument types)<\/span><\/td>\n$10K \u2013 $20K<\/span><\/td>\nPer instrument type ~$1K\u2013$2K<\/span><\/td>\n<\/tr>\n
Results entry + review workflow<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\nMulti-level review chain<\/span><\/td>\n<\/tr>\n
OOS investigation management<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\nPhase I, Phase II, CAPA<\/span><\/td>\n<\/tr>\n
21 CFR Part 11 audit trail<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\nAppend-only, tamper-evident<\/span><\/td>\n<\/tr>\n
Electronic signatures<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nPassword re-entry at signing<\/span><\/td>\n<\/tr>\n
Stability testing management<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\nProtocol, time-points, trends<\/span><\/td>\n<\/tr>\n
CoA generation + release<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nTemplate-based PDF<\/span><\/td>\n<\/tr>\n
Calibration management<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nSchedule, certificates, alerts<\/span><\/td>\n<\/tr>\n
Inventory management (reagents, standards)<\/span><\/td>\n$4K \u2013 $8K<\/span><\/td>\n<\/td>\n<\/tr>\n
Analytics + KPI dashboard<\/span><\/td>\n$4K \u2013 $8K<\/span><\/td>\nTAT, OOS rate, throughput<\/span><\/td>\n<\/tr>\n
AWS + VAPT + Year 1 ops<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\n<\/td>\n<\/tr>\n
Total<\/b><\/td>\n$85K \u2013 $167K<\/b><\/td>\nFull LIMS platform<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

EngineerBabu built Somnoware (acquired by ResMed) and healthcare platforms for Apollo Hospitals. CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: <\/span><\/i>mayank@engineerbabu.com<\/span><\/i><\/a><\/p>\n

FAQs about LIMS Software Development<\/b><\/h2>\n
    \n
  • \n

    What is 21 CFR Part 11 compliance in a LIMS and what are the key technical requirements?<\/b><\/h3>\n<\/li>\n<\/ul>\n

    FDA 21 CFR Part 11 establishes the standards for electronic records and electronic signatures in FDA-regulated industries, including pharmaceutical laboratories. The key technical requirements for a LIMS are: a complete, computer-generated audit trail showing every action on every record (who, what, when) that cannot be modified or deleted by users; electronic signatures that are unique to each individual, executed with intent (requiring password re-entry at the point of signing), and permanently linked to the signed record; access controls ensuring only authorised personnel can create, modify, or delete records; system validation demonstrating that the software performs as intended; and data integrity controls ensuring records cannot be altered undetected. A LIMS that does not meet these requirements cannot be used in an FDA-regulated laboratory environment, using it would constitute a 21 CFR Part 11 violation that can result in FDA warning letters and consent decrees.<\/span><\/p>\n

      \n
    • \n

      What is an out-of-specification (OOS) investigation in pharmaceutical labs and how does a LIMS manage it?<\/b><\/h3>\n<\/li>\n<\/ul>\n

      An out-of-specification (OOS) result is a test result that falls outside the established acceptance criteria for a specification. FDA guidance (2006 OOS Guidance) requires a two-phase investigation when an OOS result is obtained. Phase I is the laboratory investigation, a thorough review for assignable causes including analyst error, instrument malfunction, calculation errors, and sample preparation problems. If an assignable cause is identified and confirmed, the original result may be invalidated and a retest performed. Phase II is the full investigation, if no assignable laboratory cause is found, a broader investigation including manufacturing review, additional testing, and root cause analysis is required. A LIMS manages this by automatically initiating the OOS workflow when a result outside specification is entered, guiding the analyst through the Phase I checklist, tracking all retesting and investigation actions with timestamps and electronic signatures, and requiring supervisor and QA approval before any OOS investigation can be closed.<\/span><\/p>\n

        \n
      • \n

        What is stability testing in pharmaceuticals and how does a LIMS automate the programme?<\/b><\/h3>\n<\/li>\n<\/ul>\n

        Pharmaceutical stability testing is the scientific programme that demonstrates a drug product remains safe, effective, and of acceptable quality throughout its approved shelf life when stored under defined conditions. ICH Q1A (R2) guidelines define the required storage conditions, long-term at 25\u00b0C\/60% RH for zone I\/II climates, accelerated at 40\u00b0C\/75% RH, and time points at which testing must occur, 0, 3, 6, 9, 12, 18, 24, 36 months for a 36-month shelf life claim. A LIMS automates the stability programme by storing the complete protocol for each product and batch, calculating the due date for every time point, alerting the stability coordinator when samples must be pulled from the chamber, generating the test work order for the time point, tracking results against stability specifications, and producing the trend analysis showing the regression of each attribute over time that supports the product’s expiry date claim.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

        Laboratories are among the most data-intensive environments in science and healthcare. A pharmaceutical quality control lab running 500 tests per day generates 500 sample records, thousands of individual test results, calibration records for every instrument used, stability study data for every batch released, and a complete audit trail linking every result to the analyst who […]<\/p>\n","protected":false},"author":1,"featured_media":24002,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1271],"tags":[],"class_list":["post-24001","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-development"],"_links":{"self":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24001","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/comments?post=24001"}],"version-history":[{"count":1,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24001\/revisions"}],"predecessor-version":[{"id":24008,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/24001\/revisions\/24008"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media\/24002"}],"wp:attachment":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media?parent=24001"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/categories?post=24001"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/tags?post=24001"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}