Blood Transfusion Inquiry Records to Retrieve

If an authority asks about a transfusion complaint, assemble one linked file around the exact unit or component identifier. Pull the donor record, master records for blood and component, testing records, issue and supplied-component entries, cross-matching report issued to the patient, and the transfusion adverse reaction record connected to the complaint.¹²

Your file should let the reviewer move backwards to the donor and forwards to the recipient without guessing which entry belongs to the event. That is the practical test of donor-to-recipient traceability.

Keep the two retention provisions separate

Rule 122G makes maintenance of the records and registers specified in Schedule F Part XIIB and XIIC a condition of your licence.² Its testing-record condition requires testing records to be maintained for five years from the date of manufacture.²

Schedule F Part XIIB separately closes section L by saying that the “above said records” shall be kept for five years; it names no start date.¹ The date-of-manufacture trigger therefore belongs to testing records only.

When an inquiry arrives, isolate the linked originals from routine filing or disposal and use your blood bank record retention schedule to check where every part of the file is held. Work from copies while you build the response pack, and keep the source records under your existing document controls.

Retrieve the trail in a fixed order

Starting from one identifier reduces the chance that your team will combine records from different donations, components or recipients. The retrieval path below follows the donor, master, issue, cross-matching and adverse reaction records named in Schedule F Part XIIB.¹

1. Lock the starting identifier. Copy the unit or component identifier exactly as it appears in the authority’s request. Record any alternate identifier shown on the issue or recipient paperwork.
2. Open the component master record. Confirm the parent donation identifier and place the linked component separation records beside it.
3. Move backwards to collection and testing. Retrieve the donor record, blood master record and the relevant testing records under the same donation identifier.
4. Move forwards to issue. Retrieve the issue-register entry, record of the component supplied and the cross-matching report issued to the patient.
5. Attach the complaint-side record. Add the transfusion adverse reaction record and confirm that its recipient and component identifiers resolve to the same issue entry.

If the file shows that your centre handled a grouping mismatch, place the associated blood group discrepancy records beside the main trail. Keep the retrieval exercise confined to what was recorded. Clinical interpretation and causation sit outside this records pack.

Use an identifier map before copying pages

Write down which identifier connects each record before your team starts scanning or exporting. Schedule F Part XIIB names the records, but your map must show how the entries in this particular inquiry resolve to one event.¹

If the request gives you only a recipient identifier, begin with the issue entry and cross-matching report, find the component identifier there, and then travel backwards. When two records disagree, show the mismatch in your index instead of choosing the value that appears most likely.

Add supporting registers when the trail calls for them

Schedule F Part XIIB also names records of anticoagulant bags, a register of diagnostic kits and reagents, and purchase, use and stock records for disposables.¹ Include the relevant extract when the authority asks for it or when a core record refers to a batch, kit or disposable entry that forms part of the retrieval trail.

A support register should resolve back to the same unit, test or recorded activity. If your team can find a test result but cannot retrieve the referenced reagent entry, list that as a gap rather than silently leaving the supporting record out.

Build a response pack that can be checked

Your pack should preserve the connections among the record types required by Rule 122G and Schedule F Part XIIB.²¹ Arrange it in the same order every time:

• the authority’s request and a cover index;
• the identifier map used for retrieval;
• copies of the donor, master, testing, issue, cross-matching and adverse reaction records in retrieval order;
• relevant supporting-register extracts;
• a page-level reference to the location of each original; and
• a clear note for every missing page, conflicting identifier or illegible entry.

Give every copy a stable reference in the index. If you discover a gap, follow your centre’s controlled correction process and preserve the original entry. A response pack should show what your centre held when the inquiry arrived, including where the trail breaks.

Run the retrieval before an inquiry arrives

Choose a completed issue and ask someone who did not process it to assemble the file. Start once with the component identifier and again with the recipient identifier. Record every missing link, unreadable scan and register that can be found only because one technician remembers the cupboard.

Make this drill part of your regular compliance record controls. When an inquiry arrives, your team should be retrieving an established chain, not inventing a filing method while an authority waits.

Sources

1. Drugs and Cosmetics Rules, 1945, Schedule F Part XIIB, section L cdsco.gov.in
2. Drugs and Cosmetics Rules, 1945, Rule 122G cdsco.gov.in