Skip to main content

​
Implementation and Configuration

Email support@omniloy.com with your company name, project description, and expected usage. The Omniloy team will provide your apikey, baseurl, and wssurl for both sandbox and production environments. Typical response time is 1-2 business days. See the Quickstart for full details.
  • Sandbox: Testing environment with simulated data, ideal for development and integration. No usage-based billing. AI responses may use sample data.
  • Production: Real environment with full medical AI processing and usage-based billing. Requires valid SSL certificate and production API key.
The only code change needed is swapping baseurl, wssurl, and apikey values. See How do I migrate from sandbox to production? below.
Yes, simply omit the template and templateid properties. SofIA will automatically operate in chat-only mode without the generate button. Ideal for text-based queries or integrations with existing systems.
  1. Update baseurl and wssurl to production endpoints
  2. Replace the apikey with your production credentials
  3. Validate configuration with a test query
  4. Implement appropriate monitoring and logging

​
Data and Integration

SofIA does not persist clinical data. The generated report is delivered through the handleReport callback and it’s your application’s responsibility to store it in your EHR or management system.
  • Include url fields in patient_medical_notes entries to reference external records instead of embedding the entire history (see Patient Data)
  • Include only information relevant to the current consultation
  • Segment data by specialty or time period
Schemas must follow JSON Schema Draft-07. Always include:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "diagnosis": { "type": "string" }
  },
  "required": ["diagnosis"]
}

​
Clinical Coding

Automatic clinical coding (ICD-10, SNOMED CT, LOINC) is available through the SofIA API (Codify). In the SDK, you can enable coding references in your template schema using the source property — see Clinical data schemas for details.
Yes. In the SDK, add a source property to schema fields to specify the coding system (e.g., "ICD10", "cie_latam"). See Clinical data schemas for the full list of supported sources. In the API, pass the desired terminology in your request payload — see the API overview.
  • Always implement medical review for critical codes — AI-generated codes should be verified by a clinician before submission
  • Configure "required" fields in your JSON Schema to ensure key codes are always present
  • Use the handleReport callback to run custom validation logic before persisting to your EHR
  • Enable debug="true" during development to inspect the full report payload

​
Performance and Scalability

  • Maximum payload: 100 KB for template and 100 KB for patientdata
  • Simultaneous sessions: Depends on your subscription plan — contact support@omniloy.com for details
  • Rate limiting: Configured per API key based on your contract. If you receive HTTP 429 responses, you’ve exceeded your rate limit
  • Use concise and specific JSON schemas
  • Reduce the size of template and patientdata to minimize processing time
  • Use debug="true" to identify bottlenecks in the browser console
  • Pre-load relevant data when possible

​
Technical Support

SofIA is compatible with modern browsers that support WebRTC and WebSockets:
  • Chrome 80+
  • Firefox 75+
  • Safari 13+
  • Edge 80+