Mindray BC-30Vet — research profile

Current status: RESEARCH / E2. Public product information identifies the BC-30Vet as a four-part veterinary hematology analyzer. It does not establish the interface contract of the exact unit in a clinic, and it is not a Cortex support declaration.

Do not copy settings from this page

The repository previously contained a fixed network role, port, message version, acknowledgement, and query recipe. Those values were not tied to a model/firmware capture and have been removed. Do not infer them from another Mindray model or from the simulator.

Before any test, obtain the exact unit's:

• model, firmware/software build, region, and licensed options;
• LIS/interface manual or written integrator contract;
• connector direction (device client or Cortex listener), framing, character set, message family/version, sender identity, and acknowledgement behavior;
• result, order/query, quality-control, correction, duplicate, reconnect, and offline semantics.

Controlled test packet

Use a synthetic/deidentified patient and an authorised test order. Record the device report, exact Cortex profile/driver/build, settings, timestamps, and tester authorization. Compare the source report with the durable Cortex receipt, API JSON, and visible client value field by field.

Keep raw TX/RX diagnostic evidence encrypted outside Git and delete it when the signed comparison packet is complete, no later than seven days. Commit only deidentified fixtures, hashes, and the source provenance.

Promotion rule

The profile stays research or unsupported until the exact model/firmware tuple passes the controlled bench or field matrix. Result push, order/query, quality-control, and imaging are independent capability decisions. A successful connection or one parsed result cannot promote the whole model family.