No-Code Automation Connectors
Using our healthcare-specific integration and automation Connectors, organisations working with healthcare apps and clinical systems are able to easily add API's endpoints into workflows that make automating processes and integrating systems simply a matter of drag and drop. Say goodbye to bespoke API development and reduce dependency on RPA screen recording.
Alphabot
Alphabot for Teams
Use Teams on smartphone or PC to get medical alerts, on/offboard staff, retrieve/update info any of your connected systems or trigger a workflow automation.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Alphabot for Teams or any other connected system (Actions)...
New command
Real-time
New command to Workbot for Teams
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Custom action
Custom action in Workbot for Microsoft Teams (Custom)
Post message
Post message as Workbot
Post reply
Post reply as Workbot
Post simple message
Post simple message as Workbot
Post simple reply
Post simple reply as Workbot
Clinical Systems
Cerner
Receive - Px Medication History
Send - Drug Chart Update
Automate Example - Triggers Pharmacy inventory to add drug qty to reordering
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Cerner or any other connected system (Actions)...
Launching soon!
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Account
A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.
AllergyIntolerance
Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.
Appointment
A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).
Basic
It is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification.
Binary
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.
CapabilityStatement
A Capability Statement documents a set of capabilities (behaviors) of an FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
28 more..
CarePlan
Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
CareTeam
The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.
Condition
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
Consent
A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
Coverage
Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.
Device
A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.
DocumentReference
A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), clinical notes, scanned paper, and non-patient specific documents like policy text.
Encounter
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
FinancialTransaction
The Financial module covers the resources and services provided by FHIR to support the costing, financial transactions and billing which occur within a healthcare provider as well as the eligibility, enrollment, authorizations, claims and payments which occur between healthcare providers and insurers and the reporting and notification between insurers and subscribers and patients.
Goal
Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
Immunization
Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.
Location
Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.
MedicationRequest
An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
NutritionOrder
A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident.
Observation
Measurements and simple assertions made about a patient, device or other subject.
OperationDefinition
A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).
Organization
A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.
Patient
Demographics and other administrative information about an individual or animal receiving care or other health-related services.
Person
Demographics and administrative information about a person independent of a specific health-related context.
Practitioner
A person who is directly or indirectly involved in the provisioning of healthcare.
Procedure
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.
Provenance
Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies.
RelatedPerson
Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
Schedule
A container for slots of time that may be available for booking appointments.
ServiceRequest
A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
Slot
A slot of time on a schedule that may be available for booking appointments.
StructureDefinition
A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types.
Epic
Observations updated in Epic > automatically update patient via Push Notifications in NHS App > Alert an MDT of Px record update.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Epic or any other connected system (Actions)...
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
AdverseEvent
Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death.
AllergyIntolerance
Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance.
Binary
A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc.
CarePlan
Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions.
CareTeam
The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.
Condition
A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
25 more..
Consent
A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
Coverage
Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.
Device
A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.
DiagnosticReport
The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports.
DocumentReference
A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text.
Encounter
An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
Endpoint
The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information.
ExplanationOfBenefit
This resource provides the claim details, adjudication details from the processing of a Claim, and optionally account balance information, for informing the subscriber of the benefits provided.
Goal
Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
Immunization
Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.
Location
Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.
Medication
This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.
MedicationRequest
An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.
MedicationStatement
A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.
Observation
Measurements and simple assertions made about a patient, device or other subject.
Organization
A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.
Patient
Demographics and other administrative information about an individual or animal receiving care or other health-related services.
Practitioner
A person who is directly or indirectly involved in the provisioning of healthcare.
PractitionerRole
A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time.
Procedure
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy.
RelatedPerson
Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
ResearchStudy
A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects.
ServiceRequest
A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.
ValueSet
A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements.
Allscripts
Build your drag-and-drop process automation recipes on Workato by connecting triggers with actions across any connected app.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Allscripts or any other connected system (Actions)...
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Patient
The Patient resource is used to retrieve a specific patient's information (DAF Patient) including the patient's ID which can be used for other FHIR actions.
Condition
The Condition resource is used to retrieve a specific patient's conditions (DAF Condition). Conditions include problems and diagnoses.
Immunization
The Immunization resource is used to retrieve immunization events for a patient (DAF Immunization). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
MedicationStatement
The MedicationStatement resource is used to retrieve medication statements for a patient (DAF MedicationStatement). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
AllergyIntolerance
The AllergyIntolerance resource is used to retrieve a list of adverse reactions to a substance (DAF AllergyIntolerance). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
Observation
The Observation resource is used to retrieve patient observations (DAF Observation). These can include such items as smoking status, vital sign readings, and laboratory result observations. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
9 more..
MedicationOrder
The MedicationOrder resource is used to retrieve medication orders for a patient (DAF MedicationOrder). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
Procedure
The Procedure resource is used to retrieve a specific patient's procedures (DAF Procedure). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
CarePlan
The CarePlan resource is used to retrieve a specific patient's care plans (DAF CarePlan). This can include the patient's care team and the patient's assessment and plan for treatment. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
DiagnosticOrder
The DiagnosticOrder resource is used to retrieve requests for diagnostic investigations on patients (DAF DiagnosticOrder). These are also referred to as "diagnostic services." These investigations will later lead to diagnositic report. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
DiagnosticReport
The DiagnosticReport resource is used to retrieve diagnostic reports for a patient (DAF DiagnosticReport). Diagnostic reports include a combination of requested information, atomic results, images, interpretation, and formatted reports. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
Goal
The Goal resource is used to retrieve a specific patient's goals and objectives (DAF Goal). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
Device
The Device resource is used to retrieve a specific patient's manufactured or implantable devices (DAF Device). The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
DocumentReference
The DocumentReference resource is used to retrieve a specific patient's CCDA documents. The logical ID of the patient is passed as part of the URL. The logical ID is found as the result of a patient search.
Digital Health Citizen Apps
NHS App
Coming Soon...
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in NHS App or any other connected system (Actions)...
Launching Soon!
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Launching Soon!
Back Office
Oracle
Data flows easily across applications and databases in the healthcare ecosystem, plug into Oracle's comprehensive suite of application and database services.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Oracle or any other connected system (Actions)...
New row
New row in a table in Oracle
New rows
Batch
New batch of rows in a table in Oracle
New/updated row
New/updated row in a table in Oracle
New/updated rows
Batch
New/updated batch of rows in a table in Oracle
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Delete rows
Delete rows in a table in Oracle
Execute stored procedure
Execute stored procedure in Oracle
Export query result
Bulk
Export result of custom SQL in Oracle
Insert row
Insert row in a table in Oracle
Insert rows
Batch
Insert batch of rows in a table in Oracle
Run custom SQL
Run custom SQL in Oracle
7 more..
Select rows
Select rows in a table in Oracle
Select rows using custom SQL
Select rows using custom SQL in Oracle
Update rows
Update rows in a table in Oracle
Update rows
Batch
Update batch of rows in a table in Oracle
Upsert row
Upsert row in a table in Oracle
Upsert rows
Batch
Upsert batch of rows in a table in Oracle
ServiceNow
Submit Leaver Request in MS Teams > log required Incident details in ServiceNow > autonomously deprovision accounts in all clinical and back-office systems.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in ServiceNow or any other connected system (Actions)...
New record
New record in a table in ServiceNow
New record
Real-time
New record in a table in ServiceNow
Scheduled record search
Batch
Scheduled record search using query in ServiceNow
New/updated record
New/updated record in a table in ServiceNow
New/updated record
Real-time
New/updated record in a table in ServiceNow
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Custom action
Custom action in ServiceNow (Custom)
Create record
Create record in a table in ServiceNow
Create record using a template
Create record in a table using a template in ServiceNow
Search records
Search for records in a table in ServiceNow
Search records using query
Search for records using query in a table in ServiceNow
Update record
Update record in a table in ServiceNow
2 more..
Update record using a template
Update record in a table using a template in ServiceNow
Okta
AlphaBot-for-Teams triggers user/group updates in Okta including automated Active Directory user and group changes > update all Okta-synchronised systems.
›
AVAILABLE TRIGGERS AND ACTIONS
Triggers
Use these in your "recipe" to make an event happen elsewhere, whether in Okta or any other connected system (Actions)...
New events
Triggers when a new event is created in Okta
New events
Real-time
Triggers immediately when a new event is created in Okta
Scheduled event search using filter
Batch
Scheduled event search using filter in Okta
Actions
Insert these as a step in your "recipe" and they will happen automatically following a Trigger from elsewhere in Cerner or any other System...
Custom action
Custom action in Okta (Custom)
Activate user
Activate user in Okta
Add user to group
Adds an existing user to a group in Okta
Create user
Create user in Okta
Deactivate user
Deactivate user in Okta
Delete user
Delete user in Okta
10 more..
Get group members
Retrieves the list of members of a group in Okta
Get groups by name
Retrieves groups by name in Okta
Get user by ID
Get user by ID in Okta
Get user groups
Get user groups in Okta
Get recent log on events by IP address
Get recent log on events by IP address in Okta
Get recent log on events by user
Get recent log on events by user in Okta
List applications assigned to user
List applications assigned to user in Okta
Remove user from group
Removes an existing user from a group in Okta
Update user
Update user in Okta
Event-based automation at a software level that streamlines healthcare workflow
Alphalake APIdirect provides a gateway between systems used across healthcare and modern drag and drop process workflow builders that we call recipe builders.
By converting healthcare API's into No-Code "Connectors" analysts and process stakeholders working across healthcare are able to quickly and easily design process workflows using any automation and integration platform that supports the Alphalake APIdirect technology, joining up processes and improving information flow across healthcare.
By converting healthcare API's into No-Code "Connectors" analysts and process stakeholders working across healthcare are able to quickly and easily design process workflows using any automation and integration platform that supports the Alphalake APIdirect technology, joining up processes and improving information flow across healthcare.
By adding APIdirect as a bolt-on license to our healthcare digital assistant, Alphabot-for-Teams, workflows can be designed so that users in Microsoft Teams can trigger automations that run through multi-step processes on an unlimited number of systems, enabling semi-autonomous healthcare operations.
More info
Example workflow recipes for healthcare
backoffice
This automated workflow enables a user to instruct Alphabot for Teams™ to trigger an end-to-end process that will remove the user from Active Director and/or Okta, Telephony systems and Payroll. All without a human needing to be involved, driving rapid efficiency and time to value.
Leaver Request (Offboarding) submitted in Teams, ticket logged in ServiceNow, User deprovisioned in Active Directory / Okta / Telephony System.
New Team Member (Onboarding) submitted in Teams, ticket logged in ServiceNow, User deprovisioned in Active Directory / Okta / Telephony System.
This automated workflow enables a user to instruct Alphabot for Teams™ to trigger an end-to-end process that will remove the user from Active Director and/or Okta, Telephony systems and Payroll. All without a human needing to be involved, driving rapid efficiency and time to value.
