Veradigm Unity

Connecting Veradigm is what turns prior authorization from something somebody remembers to do into something that is already in progress when the appointment is booked. We read the scheduled procedure, the diagnosis and the policy, and we write the answer back where a clinician will see it.

Veradigm is two products

The clinical order lives in the EHR. The payer and the member id live in Practice Management. An authorization needs both halves, so which ones you licence decides what we can do. You can connect either or both.

You have	We can	We cannot
Practice Management and EHR	Everything: find the work, build the request, attach clinical notes, write the result back	nothing is missing
Practice Management only	Find scheduled work and produce a complete authorization request	Attach clinical documentation. A payer that wants notes will pend the request, and we say so on the case rather than letting it look complete
EHR only	Read orders and clinical detail	Produce an authorization at all. The payer and member id are not in the EHR in the form a payer transaction needs, and we refuse rather than request against a guess

#Before you start

Your Unity endpoint address for each Veradigm product you licence.
A dedicated service account, not a personal login. A named clinician account would attribute our reads and writes to that clinician in your own audit trail.
Someone who can enable an application in your Veradigm environment.
Whoever manages your network, if Unity is not reachable from outside your building. This is the step that most often takes longer than expected.

#Steps

Enable our application in Veradigm
Your Veradigm administrator registers our application and gives it the actions we need. You are given an application name and an application user id.
Create a service account for it
A dedicated account with access to the scheduling, demographic, policy and clinical actions, and nothing more. Name it so it is obvious in your audit trail that it is an integration.
Make Unity reachable
Unity usually sits inside your network. If you allow traffic by address, allow ours. If you prefer a VPN or a reverse proxy, that works too. See below for the address.
Open Settings, then Connections
Choose Veradigm Unity. Enter the endpoint or endpoints, the application name and user id, and the service account username and password.
Name a worklist owner
Optional but recommended. When we raise a task and nobody is named on it, this is who receives it. Without one, an unassigned task is refused rather than sent somewhere nobody looks.
Save
We authenticate with your service account and run a connection test against each endpoint. If either step fails, nothing is stored and you are told which endpoint and which step.

#What we ask for

Field	Required	Stored as
Practice Management URL	at least one endpoint	readable
EHR URL	at least one endpoint	readable
Application name	yes	readable
Application user id	yes	readable
Service account username	yes	readable
Service account password	yes	encrypted, never displayed again
Authorization worklist owner	no	readable

#What we read, and what we never touch

We read	For
Scheduled procedures and orders	Knowing there is work before anyone asks
Patient name, date of birth and member id	The payer transaction cannot be built without them
Diagnosis and procedure codes	The payer decides on these
Insurance policy and payer	Knowing who to ask
Clinical notes and documents	Only for payers that will not decide without them

We never read or write billing, payments, refunds, batches, sliding-fee scales, employers, pharmacy, immunisations or vitals. Of the two hundred and fourteen actions Veradigm publishes, this platform binds thirty two by name. An action outside that list is not reachable even by mistake.

#What we write, and when

A note on the encounter: The payer status, in plain language, where a clinician will see it. Always marked as automated.
A task in a named person's inbox: When something needs a human: a payer wants more information, or an authorization is at risk of missing the service date. It goes to an inbox, not to the patient chart, because it needs somebody to act today. Bounded to forty per practice per hour, because burying a worklist is its own harm.
A referral carrying the authorization: Once an authorization is granted. This is a clinical record change, so a named licensed person releases it every time. Not at any autonomy level, not with any configuration.

Nothing is written until you allow it

Read access and write access are separate. Connecting Veradigm gives us read access only. Chart writes are refused entirely until you enable them, because a read connection is not consent to write into a patient record you own.

#Network access

If your firewall allows traffic by source address, allow this one. It is stable and it is ours:

text

3.211.193.114

If you would rather not open anything inbound, a VPN or an outbound reverse proxy works equally well. Tell us which you prefer and we will work to it.

#When it does not work

The endpoint could not be reached: Almost always a network rule rather than a wrong password. Unity sits inside your network and we are outside it. Check the address above is allowed, and that the endpoint is the external one rather than an internal hostname only your building can resolve.
It rejected the service account: The username, password or application name does not match what Veradigm expects. All three are checked together, so any one of them being wrong produces this.
It authenticated but refused a connection test: The application is registered but not entitled to the actions we need. Your Veradigm administrator grants those against the application name.
Cases appear without an NPI or a place of service: An order carries those as free text and a payer needs identifiers, so we resolve them from your Veradigm dictionaries. If a provider or location is missing from those, the case says exactly which value could not be resolved rather than sending an incomplete request.

#Before your first real patient

Veradigm publishes the list of actions but not the exact shape of every response. We record those shapes against your environment first and confirm them, so the first authorization we build for you is checked rather than assumed. This is a short step and we do it with you.

One rule that connecting never changes

No authorization reaches a payer and nothing reaches your clinical record without a named licensed person releasing that exact action. Connecting your systems makes the work appear and the answers arrive. It does not make anything happen on its own.