Getting started
NEEV is Lenia Health's health data fabric. It receives clinical messages from the systems you work with, checks and converts them, delivers them to where they need to go, and keeps a readable record of every step.
Connect a sender
Bring messages in over MLLP, a webhook, an SFTP or FTP folder, or a database table.
Design the route
Route each feed to the right Project and destination, test it end to end, then save it to go live.
Change the mapping
Edit how HL7 fields become FHIR, test the draft, promote it and roll back if needed.
Find a message
See every message in plain English: where it came from, what it became and where it went.
Watch the feeds
Health, field watch and alerts tell you when traffic, delivery or a field changes.
Ask Neev
Describe a route or a conversion in a sentence and Neev builds it, then shows what changed.
How a message travels
- It arrives. A sending system connects to a source: an MLLP listener, a webhook, an SFTP or FTP folder, or a database table. HTTP and MLLP feeds can also be sent to directly.
- It is acknowledged. The sender gets an answer straight away: an HL7
ACK (
AA,AEorAR) over MLLP, or an HTTP status over HTTP. - It is converted. The feed's pipeline validates the message and converts it, for example HL7 v2 ADT into a FHIR R4 Bundle. The mapping decides which field goes where.
- It is delivered. The result goes to each destination on the route. Failed deliveries are retried; a message that keeps failing goes to the queue.
- It is recorded. Messages shows the message in plain English with its whole story, and Logs lists each event without any message content.
- It is watched. Health shows traffic and delivery, field watch notices when a field stops arriving, and alerts email the right people.
The Health page: traffic, delivery and alerts in one place
Before you begin
- You need a NEEV account in your organisation's workspace. Ask your workspace administrator for an invitation.
- What you can change depends on your role. See Roles and permissions.