General Information
| Plan Report ID Number: | [For ONC-Authorized Certification Body use only] |
|
Developer Name: |
EDENLAB OÜ |
| Product Name(s): | Kodjin FHIR Server |
| Version Number(s): | Version 3 |
| Certified Health IT Product List (CHPL) Product Number(s): | 15.04.04.3148.Kodj.03.00.0.230330 |
| Developer Real World Testing Plan Page URL: | https://kodjin.com/real-world-test-plan/ |
| Developer Real World Testing Results Report Page URL [if different from above] | https://kodjin.com/cy-2025-real-world-testing-results-report-for-kodjin/ |
Summary of Testing Methods and Key Findings
The Real-World Testing (RWT) methods were designed to evaluate the performance, interoperability, and usability of the certified Kodjin FHIR Server in real-world settings. These methods focused on ensuring the product meets the requirements of the ONC Health IT Certification Program.
Testing was conducted throughout the calendar year 2025 across multiple healthcare settings. Data collection was facilitated through Kodjin FHIR server services, leveraging tools like Prometheus, Grafana, Loki stack, and specialized Kodjin FHIR server metrics designed to capture relevant performance and operational information.
The findings indicate that the Kodjin FHIR Server performed as expected under real-world conditions, meeting ONC certification standards for interoperability and usability.
The certified capabilities demonstrated successful deployment and availability for providers to use at their discretion in live settings. Identified areas for improvement will guide future updates to enhance system performance and the end-user experience.
Standards Version Advancement Process (SVAP) Updates
Indicate as to whether optional standards, via SVAP and/or USCDI, are leveraged as part of the certification of your health IT product(s).
- [ ] Yes, I have products certified with voluntary SVAP or USCDI standards. (If yes, please complete the table below.
- [X] No, none of my products include these voluntary standards
Care Settings
The Kodjin FHIR Server is not limited to specific care settings; it can be used across various healthcare practices.
Metrics and Outcomes
The testing was conducted throughout the calendar year 2025 across multiple healthcare settings. Data collection was facilitated through Kodjin FHIR server services, leveraging tools like Prometheus, Grafana, Loki stack, and specialized Kodjin FHIR server metrics designed to capture relevant performance and operational information.
Measure 1
Measurement / Metric:
FHIR REST API Interactions by SMART on FHIR Applications
Measure Description:
Usage of the FHIR API by SMART on FHIR applications demonstrates compliance with responding to requests for a single patient’s data according to the specification and §170.315(g)(10) requirements.
Associated Criteria:
- 170.315(g)(10) Standardized API for patient and population services
Outcomes:
Review of audit logs of requests by smart apps showed that users did not use smart apps
during the gathering period.
Observations:
Similar to 2024, it was noted that this functionality is not yet widely used by our clients.
Challenges Encountered (if applicable):
No challenges were discovered during testing.
Measure 2
Measurement / Metric:
Count of the bulk export requests and error rate
Measure Description:
Using bulk export operation demonstrates compliance with responding to requests for multiple patients data as a group according to the specification and §170.315(b)(10) requirements.
Associated Criteria:
- 170.315(b)(10) Electronic Health Information Export
Outcomes:
The measured error rate was 0%, indicating that all requests were successfully processed.
Observations:
Throughout the measurement period, users did not report any issues related to this functionality. The bulk export feature performed reliably across all tested scenarios.
Challenges Encountered (if applicable):
No challenges were discovered during testing.
Measure 3
Measurement / Metric:
Authentication flow with Patient Selection
Measure Description:
- Number of requests for a patient ID or token
- Number of requests that provided sufficient information to generate a valid response
- Number of follow-up requests made using the provided patient ID or token
Associated Criteria:
- 170.315(g)(7) Application access — patient selection
Outcomes:
- 4745 – requests for a patient ID or token
- 1095 – requests that provided sufficient information to generate a valid response
- 58035 – follow-up requests made using the provided patient ID or token
Observations:
Throughout the measurement period, users did not report any issues related to this functionality.
Challenges Encountered (if applicable):
No challenges were discovered during testing.
Attestation
This Real World Testing results report is complete with all required elements, including measures addressing all certification criteria and care settings. The information presented is up to date and fully meets the health IT developer’s Real World Testing requirements.
Authorized Representative Name: Svitlana Vedmed
Authorized Representative Email: [email protected]
Authorized Representative Signature: Svitlana Vedmed
Date: 20/01/2026
