Systems
PIS (pharmacy systems)
Medication orders out, dispense and inventory back.
What this class of system is
A PIS runs pharmacy dispensing, inventory, and drug data.
orophin speaks HL7 v2, CSV, and DB polling. Out: medication orders; in: dispense and inventory. Forge, Sentinel, and Vault consume and produce the data.
Everything above rides one path. The on-prem orophin agent speaks the protocol on the hospital's own network and opens a single outbound mutually authenticated link to the Pensieve backend. Your network team approves egress.
On the wire
What it emits, and what carries it
The traffic
A medication order leaves as RDE^O11 and a dispense returns as RDS^O13, where the pharmacy system speaks HL7 at all. Many in India do not: they expose a stock table and a sales table, and the honest connection is a read-only poll of both. An automated dispensing cabinet emits its own event per door opening, which is the closest thing to a dose record most wards have.
What breaks here
Issue-to-bill reconciliation. A consumable leaves the store, reaches the patient, and never reaches the bill, and the store and the billing counter each hold half the evidence. Forge locks what was ordered, Vault raises the charge when the order is placed rather than when someone remembers, and the dispense event closes the loop against the order that caused it.
Protocols
The standards this class speaks
Each one is described in full on the standards register, at the anchor named here.
- HL7 v2The dominant hospital messaging standard. orophin sends and receives ADT, ORM / OMG, ORU, DFT, MDM, and SIU. India’s EHR Standards name v2.8.2.
- FHIR R4Modern REST / JSON resources: Patient, Encounter, Observation, ServiceRequest, DiagnosticReport, Claim, Coverage. Pensieve speaks FHIR R4 for record exchange, ABDM linkage, and NHCX claims.
- MLLP transportThe TCP framing HL7 v2 rides on. A start block, the message, an end block and a carriage return, over a socket. orophin’s MLLP adapter is the transport under every HL7 v2 connection.
- CSV / flat fileThe fallback for a system with no live interface. orophin watches a drop folder for scheduled exports and reads each file once.
- DB polling / CDCRead-only polling of a legacy database or a view, where no messaging exists at all. orophin reads; it never writes back into someone else’s schema.
- mTLS WebSocket bridgeThe single outbound, mutually authenticated link orophin opens to the Pensieve backend. Both ends verify a certificate, nothing listens on the hospital side, and every row in this register rides it.
- OIDC SSOOpenID Connect sign-in for a hospital identity provider.
Members
Systems in this class
6 entries on the register, each at its own anchor.
- Generic PIS via HL7HL7 v2 over MLLP. Out: medication orders. In: dispense and inventory.
- Marg pharmacyCSV, DB polling. In: dispense, inventory, and stock movements.
- RelyMedHL7 v2, REST / FHIR R4. In: dispense and inventory.
- Visual PharmaCSV, DB polling. In: dispense and inventory.
- Dispensing-cabinet feedHL7 v2 / device feed. In: dispense events matched against the order.
- e-pharmacy APIREST / FHIR R4, OIDC SSO. Out: e-prescription. In: fulfilment status.
What a name in this register means
Compatibility only. Pensieve connects to systems in this class over the protocol they speak. Naming a system describes the connection Pensieve is built to make; it implies no partnership, no certification, and no existing deployment.