Systems
EMR
Encounters, results, and documents exchanged over the standards an EMR speaks.
What this class of system is
An EMR holds the clinical record for a practice or hospital: encounters, problems, results, and documents.
orophin speaks HL7 v2 and FHIR R4. In/out: encounters, problems, results, and documents. Atlas and Forge 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
An ambulatory EMR is usually happier over FHIR R4 than over a socket: Patient, Encounter, Condition, Observation and DocumentReference, fetched or subscribed to over REST. The older installations emit ORU^R01 for a result and MDM^T02 for a signed document, and both carry the coding the practice actually uses rather than the coding the standard suggests.
What breaks here
Free text. A problem list typed as prose is not a problem list, and a discharge summary held as a scanned PDF is a document rather than a record. Pensieve resolves what it can to ICD-11 and SNOMED CT on the way in and keeps the original text beside the code, so nothing is silently rewritten and nothing is silently lost.
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.
- 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.
- SAML SSOEnterprise sign-in for a hospital with an existing SAML identity provider.
- OIDC SSOOpenID Connect sign-in for a hospital identity provider.
- ICD-11 terminologyWHO diagnosis coding: the primary diagnosis coding surface in Atlas and at the medical-records desk.
- SNOMED / LOINC feedsClinical-term and laboratory / observation coding. An investigation resolves to LOINC and a clinical term to SNOMED CT, which is what makes two analysers comparable.
Members
Systems in this class
8 entries on the register, each at its own anchor.
- Meditech ExpanseFHIR R4, HL7 v2, SAML SSO. In/out: encounters, results, and documents.
- Veradigm (Allscripts)HL7 v2, FHIR R4, OIDC SSO. In/out: results and documents.
- athenahealthFHIR R4, OIDC SSO. In/out: encounters and results.
- NextGenFHIR R4, HL7 v2, OIDC SSO. In/out: encounters and results.
- eClinicalWorksFHIR R4, HL7 v2, OIDC SSO. In/out: encounters and results.
- DrChronoFHIR R4, OIDC SSO. In/out: encounters and results.
- Practo RayHL7 v2 / REST API, OIDC SSO. In: appointments and demographics.
- HealthPlixHL7 v2 / REST API, OIDC SSO. In: encounters and prescriptions.
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.