Mindray BC-5000Vet — research profile

Current status: RESEARCH. The model's marketed hematology capabilities are not an interface or Cortex compatibility contract. BC-30Vet behavior, a simulator fixture, or a generic HL7 assumption must not be inherited by this unit.

Exact evidence required

For the installed model and firmware/software build, obtain the authorised LIS or PIMS interface contract and record:

• connection direction and connector type;
• framing, character set, message family/version, sender/receiver identity, and positive/negative acknowledgement rules;
• which differential, reticulocyte, correction, and quality-control fields are actually licensed and transmitted;
• order/query/worklist behavior, sample correlation, retries, duplicate control identifiers, and offline recovery.

No server address, network value, message version, menu path, or firewall change should be copied from another model.

Controlled evidence collection

Run only with a synthetic/deidentified patient and an authorised order. Compare the device's report with the Cortex durable receipt, API JSON, and visible client value field by field. Exercise malformed/checksum input, duplicate, disconnect/restart, correction, multiple-group, unmatched, and each separately requested capability.

Raw diagnostic captures stay encrypted and access-controlled outside Git and are deleted when the signed evidence packet is complete, no later than seven days. Only deidentified fixtures, hashes, and provenance belong in the repository.

The exact profile remains research or unsupported until its own evidence passes the controlled acceptance matrix. A successful result does not certify worklist, quality-control, or imaging behavior.