Dubai Healthcare Authority’s NABIDH FAQs

Do you have a question about our NABIDH integration offering? We’ve thought ahead and tried to answer some of your frequently asked questions! Check them out below, and as always, please reach out to us if you have any other questions.

Clinic: I have more than one branch in Dubai. How would the integration look there?

Nexusware: Each branch will have to be onboarded to DHA individually; Nexusware would have to connect to both branches to onboard them both individually. This would require a separate payment for each branch.

Clinic: Do you have a demo?

Nexusware: Yes absolutely, we have a recording of what the integration would look like. Would you like to see the technical process or the non-technical?

Clinic: Does our staff need training?

Nexusware: There is limited training. The requirements from DHA are specific, so whoever enters the information on your end must do so with little to no human-error; however, there won’t be much in terms of having to learn a new system or anything like that. If you have to use Nexusware Forms, they are very simple to use with an easy-to-navigate user interface.

Clinic: What if there is an error either during onboarding or after onboarding?

Nexusware: Thankfully, during the onboarding process, we are given ample time to stress test the connectors to ensure all data is sent properly. If there are any issues, then the Nexusware team will work to correct them as priority. This might require your team to adhere to any changes that would pacify any issues from the DHA, but those would be on a case-by-case basis. Essentially, we are given 30-60 days to onboard your clinic and make sure everything is working optimally (also note that we will do our best to onboard you in under 30 days). After onboarding, if there are any issues, you have the full support of the Nexusware team to correct anything as soon as possible. We remain by your side during the entire duration of the contract, and will provide you full support – of course, this is also included in the cost.

Clinic: How much does this cost?

Nexusware: We have a one-time setup fee, and two packages to choose from – monthly payments or one lump sum annual payment. Please reach out to us for further details on the pricing.

Clinic: How many users can I register?

Nexusware: As it currently stands, you can register as many users as you would like within your organization for no additional cost.

What Are Some Example Use Cases For Nexusware?

Healthcare and patient data can be massive, complex, and inconsistently structured. Manual interoperability integrations can be time-consuming and cumbersome for organizations. Our cloud-based no-code engine makes it easy to connect multiple systems and initiate downstream missions when they occur.

 Private Practice

Automating Workflows With Nexusware: Physicians can automate routine operations, improving staff productivity and lessening document burnout.

Referral Management: Connecting referral management software to a CRM, like Salesforce, to streamline and increase referral acceptance.  

Patient Intake, Transfer and Discharge: Never send or receive by fax again! Nexusware can connect with your patient’s last care facility and import the patient’s history directly into your native EHR. At discharge, send care instructions to the next facility with the touch of a button. And for recurring patients, create a mission that imports the patient’s latest records from the entire care team – and create a trigger so it automatically fetches that data on the day of their next appointment.

Technical Questions And Product Scope

How is the source sending values HIPAA compliant?

Nexusware encrypts patient data from beginning to end, and no data is ever saved, meaning the process is HIPAA compliant at all times and more secure than competitive solutions that rely on secondary databases which include another “point of attack”.

Have you done any system overload benchmarking?

Yes. Nexusware has been built for scale. The cloud system is only used to compute the internal messaging system and push data out, and we never carry backups on any internal database. This makes us more HIPAA compliant

What if the other receiving party is not available to receive live data?

Error handling is built into the system so if the receiving party is not ready to accept data an error message will appear, asking the sender to try again later or contact the receiver.

Can you plug into a message bus (e.g., Kafka) and subscribe to topics and then convert to API or is it mainly API to API?

Nexusware supports XML, RSS, and more. You can integrate triggers into the mission so when data changes, you can parse the mission to execute, manage and manipulate the data as it is fed out the other side. The mission can be executed  via API as well, with each mission assigned an API that can activate the mission on both sides.

In a proper implementation, would there be an exchange of public/private key to allow the transfer and it remain HIPAA compliant?

All that is required is the authentication method from each EHR implementation. Data is encrypted when it enters the Nexusware system, decrypted on exit, and no storage methods are involved, meaning Nexusware remains HIPAA compliant at every step.

Do I need to have my system interconnected with all hospitals and healthcare providers to be able to use Nexusware?

No. Authentication is required before Nexusware can parse information directly with an EHR, so communication between parties is required. However, authentication can be initiated on an as-needed basis. No pre-established link or network access is required. Clients can also utilize our built in “invite system” allowing other organizations the ability to send information without sharing sensitive authorization modules or private keys.