The platform is designed to develop and launch a comprehensive screening and management system for fertility candidates, including surrogates (gestational carriers), egg/embryo donors, and sperm donors. It empowers agencies, clinics, and psychologists with a unified, secure workspace to manage every step of the psychological evaluation process from intake and scheduling to assessments, reporting, and follow-up services supported by AI-assisted workflows.
Unlike today’s fragmented workflows across emails, spreadsheets, and manual coordination, the system streamlines:
•    Candidate intake and verification
•    Conflict checks and compliance
•    Proctored PAI assessments and interviews
•    AI-assisted report generation
•    Credit-based billing
•    Secure messaging and communication
By leveraging AI and automation, the platform ensures faster turnaround times, consistent and compliant psychological evaluations, and data-driven insights that help agencies make informed placement decisions improving candidate experience, reducing delays, and ensuring ethical practices.

The goal of Innoid is to create a centralized, HIPAA-compliant healthcare data warehouse that unifies clinical and operational data from multiple systems. The platform standardizes structured, semi-structured, and unstructured inputs into a single repository, enabling advanced analytics, business intelligence, and AI-powered insights. It directly tackles the challenge of disconnected healthcare data sources, giving organizations the ability to make faster, evidence-based decisions.

This Proof of Concept (POC) involves setting up a Mirth Connect integration to process HL7 messages for communication with the UAE government healthcare system. The workflow includes:

• Receiving a JSON request via an HTTP Listener.
• Converting JSON to HL7 format.
• Sending HL7 data to the UAE government endpoint.
• Handling real-time HL7 responses, converting them back to JSON, and sending the response to the HTTP requester.
• Implementing retry logic (configurable, e.g., 3 retries) in case the government server is unreachable.
• Ensuring nothing is hardcoded and using a config file for parameters like retry count.
• Supporting JWT Authentication for secure HTTP requests.
• Creating separate Mirth channels for each message type (ADT, ORM, etc.), starting with ADT messages.