Organisation profiles
A profile holds your organisation's settings for one kind of conversion, for example the header values written on outbound HL7, or how local codes map to standard terminology. Pipelines use a profile instead of repeating the same settings in every Project.
You only need a profile where your organisation's policy changes what is sent. Inbound HL7 conversion, validation, de-duplication and analytics JSON work the same for everyone and need none.
Open Configure › Profiles in the left sidebar. The list on the left can be narrowed to one kind of profile:
| Kind | What its profile sets |
|---|---|
| Patient identity | How patient identifiers are matched and which one is preferred. |
| Clinical codes | Local codes to standard codes, for example SNOMED CT or laboratory codes. |
| Measurement units | Units of measure, normalised to UCUM. |
| Outbound HL7 interface | Outbound HL7: sending and receiving application and facility (MSH-3 to MSH-6), HL7 version, fallback ADT event and assigning authority. |
| Analytics JSON | The clinical JSON shape sent to API consumers. |
A Pipeline step set to Auto picks, for each message, the approved and enabled profile that best fits it, for example an admission or a laboratory result. To force a particular profile, choose it in the step's settings in the Project; that choice always wins. Profiles set how a message is converted, never where it is sent. Select How profiles work at the top of the page for a reminder.
Platform baselines
Every workspace starts with baseline profiles for each kind, marked BASELINE in the list. They are approved, used by default, and read-only.
To change a baseline's settings, open it and select Copy to custom. NEEV opens a copy named "… — custom", set to production and draft, with the baseline's settings filled in. Change what you need and select Create profile. The baseline itself never changes.
Profiles, with a read-only platform baseline open
Create a profile
- Select New profile, or Copy to custom on a baseline.
- Enter a Name, for example
Hospital PAS outbound ADT. - Choose the Transformer, the kind of profile. The settings below change to match it.
- Choose the Environment: test, staging or production.
- Choose the Approval: draft while you are preparing it, approved when it is ready. Only approved profiles can be picked by Auto.
- Fill in the Configuration. Fields marked
*are required; each has a short explanation under it. - Tick Enabled, and Organization default to make it your default for its kind. Only enabled, approved profiles can be the default.
- Select Create profile.
A new outbound HL7 profile for the hospital PAS
Saving an orchestration refuses Pipelines that use a test or staging profile, or an outbound receiver profile that is not filled in. Use test and staging profiles while you build, then switch to an approved production profile.
Try it before you save
Open the Test tab of any profile, including one you have not saved yet.
- Select Load sample admission or Load sample laboratory result, or paste your own FHIR message.
- Select Test conversion — no delivery.
NEEV runs the conversion with the settings on screen, including unsaved changes, and shows the result under After. Nothing is delivered, nothing is approved, and no live message is affected. Use synthetic or authorised data only.
Change a profile
Profiles are never edited in place. Each change is a new version.
- Select the profile in the list.
- Change its settings on the Settings tab. Discard changes puts them back.
- Select Create new version.
Saving a new version does not move the Pipelines already using the profile on to it: "Saving creates a new version; existing Pipeline bindings stay unchanged." The Usage tab shows where a profile is used, for example "Used by 3 node(s) across 2 Pipeline(s)". To adopt the new version, update the step's profile in each Project, save its Pipeline, then save the orchestration again.
Who can do what
| Action | Viewer | Member | Admin |
|---|---|---|---|
| See profiles, versions and where they are used | Yes | Yes | Yes |
| Test a conversion on the Test tab | Yes | Yes | |
| Create a profile, copy a baseline or create a new version | Yes | ||
| Change a platform baseline |