Working Alongside Your Existing Systems

Kora recognises that animal management doesn't happen in isolation. You already use accounting software tracking finances. Spreadsheets contain years of historical data. Laboratory systems provide test results. Government portals require regulatory submissions. Research databases support scientific collaboration. Kora doesn't replace these tools. Kora works alongside them.

This chapter explains Kora's integration philosophy and shows practical patterns for data exchange, system coordination, and workflow integration across diverse contexts. Integration supports your existing investments while gaining Kora's specialised animal management capabilities.

Understanding Integration in Kora

Integration means different things in different contexts:

For farmers - Export animal sales data to accounting software (Xero, QuickBooks, MYOB). Share inventory usage with financial systems. Submit regulatory reports to government portals. Provide traceability documentation to buyers.

For conservationists - Export population data to research databases. Share studbook information with partner organisations. Provide CITES documentation to regulatory authorities. Publish monitoring data to scientific repositories.

For veterinarians - Receive laboratory test results from diagnostic labs. Share health certificates with regulatory authorities. Provide treatment histories to referring veterinarians. Export AMR data for stewardship reporting.

For researchers - Export systematic observation data to statistical software (R, SPSS, Python). Share GPS coordinates with GIS platforms. Provide population trend data to academic collaborators. Submit research data to institutional repositories.

For regulatory authorities - Export compliance matrices for government reporting. Share traceability chains with food safety investigators. Provide jurisdiction statistics to policy makers. Submit enforcement data to oversight bodies.

Kora provides comprehensive data export capabilities supporting these integration needs. Your data remains accessible, portable, and under your control.

Kora's Integration Philosophy

Unopinionated design extends to integration. Kora doesn't dictate your complete workflow. You choose which systems handle which functions. Kora excels at animal management, biosecurity, traceability, and health tracking. Other systems may excel at accounting, inventory procurement, or laboratory analysis. Use both.

No vendor lock-in. Kora uses open standard formats (JSON, CSV, Excel, PDF). Export your complete dataset anytime. Move to different systems if needed. Your data belongs to you.

Single-tenant architecture protects integration. Each organisation's Kora instance remains isolated (Chapter 27). Integration happens on your terms. Share what you choose, when you choose, with whom you choose.

API-first foundation. Kora's Knowledge API (Chapter 4) demonstrates successful external integration. Disease intelligence flows from global sources into your daily workflows. This model extends to other integration patterns.

Data Export Capabilities

Kora provides comprehensive export across data types and formats:

Export Data Types

Individual animals - Complete animal profiles including: identification details, health observation histories, treatment records, movement timelines, weight measurements, reproductive records, pedigree information, photos and documents, traceability events, current location and status.

Animal mobs (groups) - Population demographics, group-level observations, mob treatments, movement histories, location assignments, formation and splitting events.

Tasks - Task details and status, assigned personnel, due dates and completion, recurring task patterns, associated animals or locations, task completion histories.

Locations - Farm/reserve/facility boundaries, subdivision hierarchies (paddocks, enclosures, zones), GPS coordinates and polygons, location features (water points, gates, infrastructure), biosecurity zone definitions.

Traceability chains - Complete event timelines (birth through current status), cryptographic hash verification data, attached evidence documents, movement histories with GPS verification, compliance scoring, parent-child chain relationships.

Export Formats

JSON format - Comprehensive structured data. Machine-readable for software integration. Preserves complete data relationships. Nested structure maintains parent-child links. Ideal for: system-to-system integration, custom software development, backup and archival, data migration preparation.

CSV format - Spreadsheet-compatible tabular data. Opens directly in Excel, Google Sheets, LibreOffice. Simple structure for manual analysis. Ideal for: financial data import to accounting software, basic statistical analysis, manual data review, sharing with non-technical collaborators.

Excel format - Pre-formatted workbooks with multiple sheets. Professional presentation with headers and formatting. Calculated fields and summaries included. Ideal for: executive reporting, regulatory submissions requiring specific formats, multi-sheet data analysis, presentations to stakeholders.

PDF format - Print-ready reports with professional layout. Immutable document format for official records. Digital signatures supported (where implemented). Ideal for: regulatory authority submission, legal proceedings documentation, official record archival, client-facing reports.

Regulatory Export Capabilities

Regulatory traceability exports (Chapter 23) provide specialized formatting:

Advanced filtering - Export specific compliance score ranges. Filter by verification status, jurisdiction codes, date ranges. Include only chains meeting specific criteria.

Customizable field selection - Choose which data fields to include. Export basic identifiers only or complete event histories. Tailor exports to recipient requirements.

Summary statistics - Exports include: total chains exported, compliance score distribution, verification percentage, event type breakdowns.

Audit trail metadata - Export timestamp, requesting user, filter criteria applied, data provenance information.

Practical Integration Patterns

Real-world integration spans diverse use cases:

Financial System Integration

Farm accounting workflow:

1. Export animal sales - When animals sold, export: animal identifiers, sale dates, sale prices (if tracked), buyer information, movement documentation.

2. Import to accounting software - Open CSV export in Excel. Format for accounting system import (Xero, QuickBooks, MYOB). Map Kora fields to accounting categories (asset sales, inventory reduction).

3. Maintain dual records - Kora tracks animal histories, health records, traceability. Accounting software tracks financial transactions, depreciation, tax reporting. Both systems serve their purpose.

Inventory cost tracking:

Export medication usage and feed consumption from Kora. Import to accounting as operating expenses. Reconcile inventory valuations between systems quarterly.

Laboratory System Integration

Veterinary diagnostic workflow:

1. Record observation in Kora - Animal shows symptoms. Veterinarian records observation (Chapter 10). Samples sent to diagnostic laboratory.

2. Laboratory conducts tests - External laboratory performs diagnostic tests (haematology, serology, bacteriology, virology).

3. Receive results via email - Laboratory emails PDF test results or provides laboratory portal access.

4. Attach to Kora observation - Upload laboratory PDF to original observation as document attachment. Document hash calculated automatically. Test results become part of permanent health record.

5. Record treatment based on results - Veterinarian prescribes treatment based on confirmed diagnosis. Treatment record references laboratory results.

Research laboratory coordination:

Conservation organisations conducting genetic analysis export DNA sample metadata from Kora. Share with genetics laboratory via CSV. Laboratory returns results spreadsheet. Import key findings (inbreeding coefficients, genetic diversity metrics) to breeding programme records (Chapter 16).

Government Portal Integration

Regulatory submission workflow:

1. Export compliance data - Use regulatory search (Chapter 23) to filter relevant chains. Export compliance matrix showing verification status. Generate PDF summary report.

2. Submit to government portal - Upload exported files to regulatory authority portal (TRACES for EU, NLIS for Australia, USDA systems for USA). Provide as evidence during inspections.

3. Reference in official correspondence - Traceability chain identifiers from Kora reference specific animals in regulatory communications.

Export certification preparation:

Export complete animal history (birth, movements, health certificates, quarantine records). Print PDF documentation. Attach to export permit applications. Government veterinarian references Kora records during pre-export inspection.

Research Database Integration

Scientific publication workflow:

1. Export systematic observation data - Conservation researchers export wildlife sighting data (GPS coordinates, species identifications, observation timestamps, environmental conditions).

2. Import to statistical software - Open CSV in R, SPSS, or Python pandas. Conduct statistical analysis (population trends, habitat use patterns, seasonal distribution).

3. Generate publication figures - Create maps showing observation locations. Plot population trends over time. Analyse habitat selection.

4. Cite data provenance - Research publications cite Kora as data management system. Complete audit trail supports peer review.

Data repository submission:

Academic institutions require data archival. Export complete research dataset from Kora as JSON. Submit to institutional repository (Dryad, Figshare, Zenodo). Assign DOI for citation. Published papers link to archived dataset.

Spreadsheet Workflow Integration

When spreadsheets make sense:

Some workflows work better in spreadsheets. Kora supports this:

Budget planning - Export historical inventory usage and animal numbers. Build budget forecasts in Excel considering: seasonal variation, anticipated growth, expected procurement costs.

Custom reporting - Export animal data to Excel. Create custom pivot tables and charts. Generate stakeholder reports with organisation-specific formatting.

Temporary analysis - Export current population demographics. Conduct "what-if" scenarios in spreadsheet. Explore breeding programme options before committing to decisions.

Data verification - Export recently entered data. Review in spreadsheet format. Identify data entry errors or inconsistencies. Correct in Kora based on spreadsheet review.

Knowledge API as Integration Example

The Knowledge API (Chapter 4) demonstrates successful external integration:

Global disease intelligence integration:

Kora connects to centralized disease knowledge base containing: 100+ emergency animal disease profiles, epidemiological transmission rates, outbreak tracking data, authority emergency contacts.

When veterinarian diagnoses disease in Kora, system automatically:

• Retrieves disease transmission rate and incubation period
• Calculates quarantine duration recommendations
• Identifies exposed animals via contact tracing
• Suggests health monitoring frequency
• Provides biosecurity protocol guidance

Benefits of integrated knowledge:

You don't maintain disease database manually. Knowledge updates automatically from central source. Veterinary best practices flow directly into daily workflows. Biosecurity responses use current scientific evidence.

This integration model extends:

Future integrations could provide: weather data influencing animal health predictions, market price data supporting sales decisions, breeding recommendations from genetic databases, regulatory requirement updates from government sources.

Data Ownership and Portability

Single-tenant architecture guarantees ownership. Each organisation's Kora instance operates independently (Chapter 27). Your data resides in your database. No multi-tenant mixing with other organisations.

Complete data export prevents lock-in. Export your entire dataset anytime. JSON format preserves all relationships. Includes: all animals (individual and mob), complete health histories, all movements and locations, traceability events with cryptographic hashes, tasks and workflows, team member information, configuration and settings.

Data protection regulation compliance. Export capabilities support GDPR "right to data portability" and similar regulations globally. Individuals (veterinarians, staff) can request their associated data. Organisations control data access and sharing.

Migration preparation. If transitioning to different software, complete export provides starting point. JSON format includes all necessary relationships. Technical teams can build import scripts using structured data.

Backup and Data Recovery

Data protection requires systematic backup beyond integration:

Database Backup Capabilities

Automated backup scheduling - System administrators configure backup frequency (Chapter 27). Daily, weekly, or custom schedules. Backups stored securely outside production database.

Point-in-time recovery - Restore database to specific timestamp if data corruption occurs. Minimal data loss (only changes since last backup).

Disaster recovery preparation - Backup copies stored off-site. Protects against: hardware failure, natural disasters, ransomware attacks, accidental deletion.

Export as Backup Strategy

Periodic comprehensive exports - Schedule quarterly or annual complete data exports. Store JSON exports securely: external hard drives, cloud storage, secure archives.

Critical data exports - Before major system changes (software updates, configuration changes, data migrations), export complete dataset. Provides rollback option if issues occur.

Archival requirements - Regulatory or institutional policies may require long-term data retention. Periodic exports create permanent snapshots meeting compliance requirements.

Export plus backup strategy - Database backups (fast recovery, short-term). Data exports (long-term archival, migration preparation). Combined approach provides comprehensive protection.

Working with External Consultants

Integration supports collaboration with external experts:

Veterinary consultants - Export specific animal health histories for specialist consultation. Veterinarian consultant reviews exported PDF. Provides recommendations. Primary veterinarian implements recommendations in Kora.

Genetic consultants - Export breeding programme data (pedigrees, genetic diversity metrics) for expert analysis. Consultant provides breeding recommendations. Update breeding plans in Kora (Chapter 16).

Biosecurity consultants - Export biosecurity assessment data and protocol execution records. Consultant reviews compliance patterns. Recommends improvements. Implement enhanced protocols in Kora (Chapter 11).

Financial consultants - Export animal inventory values and transaction histories. Accountant reconciles with financial records. Identifies tax optimisation opportunities. Integration maintains data consistency.

API Access for Custom Integration

Kora.API provides programmatic access (development phase, not production-ready). When production-ready, API will enable: automated data synchronization between systems, custom dashboard development, mobile application integration, third-party service connections.

Current integration approach: Use data export for system-to-system integration. Schedule periodic exports. External systems import exported files. Suitable for: daily/weekly synchronization needs, one-way data flows (Kora to external system), scenarios where real-time sync unnecessary.

Future API capabilities (when production-ready): Real-time bidirectional synchronization, webhook notifications for event triggers, fine-grained access control for external applications, rate limiting for API stability.

Context-Specific Integration Examples

Commercial Livestock Farm

Systems integrated:

• Kora: Animal health, movements, traceability
• Xero: Financial accounting, invoicing, payroll
• Excel: Budget forecasting, custom reports
• NLIS (Australia) or equivalent: Government regulatory submission

Integration workflow: Weekly export of animal sales from Kora to CSV. Import to Xero as income transactions. Quarterly export of traceability chains for NLIS compliance submission.

Zoo or Conservation Facility

Systems integrated:

• Kora: Individual animal management, studbook
• ZIMS (Zoological Information Management System): International zoo database
• ISIS (International Species Information System): Species survival plans
• Excel: Custom conservation metrics, donor reporting

Integration workflow: Monthly export of breeding programme data. Share with studbook coordinator via secure email. Coordinator updates international studbook. Results inform breeding recommendations in Kora.

Wildlife Research Project

Systems integrated:

• Kora: Wildlife sightings, GPS observations
• R or Python: Statistical analysis
• ArcGIS or QGIS: Spatial analysis and mapping
• Institutional repository: Research data archival

Integration workflow: Export GPS observation data to CSV at project completion. Import to R for population trend analysis. Export maps to GIS for habitat modeling. Archive complete dataset to repository with DOI for publication citation.

Veterinary Practice

Systems integrated:

• Kora: Patient records (animals served across multiple client farms)
• Veterinary diagnostic laboratory: Test result systems
• Practice management software: Appointment scheduling, billing
• Email: Client communication

Integration workflow: Record clinical examinations in Kora (Chapter 20). Laboratory emails test results as PDF. Attach PDF to Kora observation. Export treatment summaries to PDF. Email to animal owner for records.

Regulatory Authority

Systems integrated:

• Kora: Regulatory dashboard, traceability search (Chapter 23)
• Government compliance database: National animal identification systems
• Excel: Compliance analysis and reporting
• Internal databases: Inspection tracking, enforcement actions

Integration workflow: Conduct traceability searches via Kora regulatory dashboard. Export compliance matrices to Excel. Analyse jurisdiction-wide compliance trends. Submit summary reports to government compliance database.

Integration Best Practices

Plan integration workflows before starting. Identify: which systems handle which functions, how frequently data synchronization needed, who manages integration processes, what data validation occurs during transfer.

Start simple, expand gradually. Begin with single integration (e.g., animal sales to accounting). Verify workflow functions correctly. Add additional integrations incrementally.

Validate data after transfer. Spot-check exported data matches source records. Verify imported data makes sense in receiving system. Reconcile totals between systems periodically.

Document integration procedures. Create written instructions for: export procedures and frequency, data transformation steps, import procedures in receiving systems, troubleshooting common issues. Train staff on integration workflows.

Maintain both systems appropriately. Each system serves specific purpose. Don't duplicate all data everywhere. Use Kora for animal management, traceability, and health. Use accounting software for finances. Each system maintains its expertise domain.

Review integration effectiveness. Quarterly assessment: Are integrations saving time? Do data quality issues occur during transfer? Should integration frequency change? Are new integration needs emerging?

Desktop vs Mobile for Data Export

Desktop excels at:

• Configuring complex export filters
• Selecting multiple animals/tasks/locations for export
• Reviewing large export files before downloading
• Managing export file storage and organisation
• Coordinating with accounting or analysis software
• Scheduled periodic exports

Mobile works for:

• Quick single-animal export for email sharing
• Exporting current location for GPS verification
• Sharing recent observations with veterinarian
• Emergency document access during field visits

Most integration workflows happen at desktop where file management and multi-system coordination occur naturally.

Getting Started with Integration

New users establishing integration should:

1. Identify integration needs - Which external systems require Kora data? What frequency (daily, weekly, monthly, quarterly)? What format works best for each recipient?

2. Start with simplest integration - Export single animal to JSON. Open in text editor. Understand data structure. Export to CSV. Open in Excel. Verify readability.

3. Practice regulatory export - Use traceability export (Chapter 12 or 23). Generate PDF report. Review formatting and content. Understand what information exports provide.

4. Establish backup routine - Schedule quarterly complete data export. Store securely off-site. Test restoration process with sample data.

5. Document integration procedures - Write step-by-step instructions. Include screenshots if helpful. Train team members on established workflows.

6. Review and refine - After three months, assess integration effectiveness. Adjust frequency or format if needed. Add new integrations incrementally.