Overview
The Parachute Health + NikoHealth integration enables a seamless flow of patient and order data between platforms, reducing manual entry and improving order accuracy.
To setup the integration, there are three key processes to work through:
Product mapping
Payer mapping
Activating the integration within NikoHealth
After setting up the integration, review how information is transmitted between the two systems and how to the integration impacts data and workflow processes.
Setup 1- Product Mapping
Product mapping ensures alignment between the DME Supplier’s catalog and the products available in Parachute Health.
Export Your Product Catalog
Export your product catalog from NikoHealth to align products with those in Parachute Health. Follow the below steps and provide this to your Parachute contact.
Navigate to: Management > Data Transfer > Export > Export Product Catalog
This export includes the necessary Reference Product IDs for mapping.
Setup 2- Payer Mapping
During onboarding, payer mapping must be completed to align the DME Supplier’s payer library with the payers in Parachute Health. This includes verifying that the unique NikoHealth Reference Payer IDs are correctly matched to the corresponding payers in Parachute Health.
Generate a Report
You'll align your payer library with the payers in Parachute Health by generating a report in NikoHealth. Follow the below steps and provide this to your Parachute contact.
Navigate to: Reports > Payers > Payer/Payer Plan Detail
Before running the report, be sure to select Unique Payer ID under the Show/Hide Filters section. This will ensure the exported report includes the necessary identifiers for accurate mapping.
Setup 3- Activating the Integration with NikoHealth
Activate the Parachute Health integration in NikoHealth by navigating to: Management > Application Setting > Integrations > Parachute Health
Enter the Client ID and Client Secret provided by Parachute Health to complete the activation.
Integration Details
When integrating NikoHealth and Parachute Health, it's important to understand how patient and order information is transmitted and managed between the two systems.
Order Acceptance and Transmission
DME suppliers will log into the Parachute Health platform to review and accept new orders. Once an order is accepted, the patient and order details are automatically sent to NikoHealth.
Patient Creation and Matching
If the patient does not already exist in NikoHealth, a new patient record will be created. NikoHealth first attempts to match based on the Parachute Health ID, which will be saved in the patient’s custom field labeled “Parachute Health ID.”
If a patient already exists with the same first name, last name, and date of birth, the order will not be created. Instead, an internal note will be added to the Activity Feed to alert the supplier of the duplicate.
Patient Information Transferred
When a new patient is created, the following information is populated in NikoHealth:
First and Last Name
Gender
Date of Birth
Height and Weight
Billing Phone Number (stored as "Cell")
Delivery Phone Number (stored as "Other")
Delivery Address
Emergency Contact
Billing Address (stored as "Patient Address")
Diagnosis (stored in the medical record)
Service Location
NikoHealth matches the service location using either the Supplier System ID or the Legal Entity NPI number from Parachute Health. If neither can be matched and only one service location exists in NikoHealth, it will default to that. If a match cannot be made, an internal comment will notify the supplier. NikoHealth Service Location IDs can be provided upon request for mapping.
Insurance Record Handling
When a new patient is added, insurance information is imported, including:
Payer
Policy Number
Payer Level (Primary, Secondary, etc.)
Policy Holder (defaults to "Self")
We recommend verifying this insurance information within NikoHealth. If a patient already has insurance on file, it will not be overwritten. An internal comment will be added to the activity feed in these cases.
Order Creation in NikoHealth
The following data is used to create an order in NikoHealth:
Order Scheduled Date: Based on the "Accepted At" date in Parachute Health. If not available, today’s date is used.
Referral Date: Pulled from "Last Signed At" when available.
Delivery Type: Defaults to “Home Delivery.”
Service Location: Matched as outlined in the Patient Information section.
Referring Provider: Matched by NPI. If the provider does not exist in NikoHealth, an internal comment will be posted, and the order will proceed without one.
Identifiers Stored as Custom Fields:
Parachute Health Order ID
Parachute Health Fulfillment ID
Prescription and Order Items
A prescription is created for each item, including the Length of Need and Diagnosis. The diagnosis is global and applied to all items. If item-specific diagnoses are required, the supplier should update those directly in NikoHealth.
If a product cannot be matched using the established client mapping, it will be added as a generic item using the HCPCS code. The unit of measure is matched using NikoHealth’s Base Unit Name or Related Unit Name. If no match is found, the base unit of measure is used.
Document Handling
Any documents available within the Parachute Health order are transferred to NikoHealth and stored within the patient record. They are also attached to the relevant order and labeled with the document type “Parachute Health.” If documents are added in Parachute Health after the order is accepted, they will still be pulled into NikoHealth and attached appropriately.
Fulfillment Status Updates
As the order status updates in NikoHealth, Parachute Health will be automatically updated to reflect the new status:
NikoHealth Status | Parachute Health Fulfillment Status |
In Progress | Ready for Delivery |
Ready to Fulfill | Ready for Delivery |
Canceled | Canceled |
Hold | Pending Further Review |
Completed | Completed |
We recommend verifying this insurance information within NikoHealth. If a patient already has insurance on file, it will not be overwritten. An internal comment will be added to the activity feed in these cases.