Review data transfers yourself.
We are opening SILD to selected pilot customers. The goal is for your team to review an agreed data transfer in your own test environment and repeat the review after changes.
The results show which information reached the target, where a difference is evidenced, and where missing data or documentation leaves a question open. The review uses matched source and target data and rules agreed in writing.
Paid pilot engagement · scope and price agreed before commissioning · initially a test environment with synthetic data
A complete demo path through to AION.
On our demo server we have built an end-to-end path with handoff to AION. The current technical build accepts HL7 v2 (ER7), FHIR R4 (JSON/XML), LDT 3.2.20 and GDT 2.1/3.5, and outputs FHIR R4 (JSON/XML). We assess your exact variant against your specification and suitable test cases.
The demo path establishes a technical workflow. It does not grant general approval for customer production use. KDL and openEHR are not currently committed standard interfaces.
From interface description to your own review run.
Describe the path
Identify source and target, message or resource type, versions, profiles, mapping and expected values. Complete documentation and synthetic examples let us assess technical fit in writing first.
Agree the scope
We define the information to review, permitted transformations, the test environment and the expected outputs. Missing interface documentation is treated as separate discovery work.
Try independent use
After technical acceptance, your team should be able to start and repeat the review. Installation, handoff, support and fees are agreed for each pilot engagement.
Tell us about your data path.
To start, send system names, formats and versions, available interface documentation and a short description of what you want to review. Please do not send patient data at this stage.
The existing SILD audit is a review performed by ISCaD with a report. The customer pilot aims at independent use by your team.