Open Imaging Reporting SDK
A software development kit named in the January 2026 status deck as the third strategic pillar’s centerpiece: “Applications: Open Imaging Reporting SDK (vendor-driven innovation),” alongside demo applications such as an Imaging Problem List browser and early draft-generation tools. The deck’s call to action names a vendor reporting SDK as an example of the vendor-driven work it hopes to enable.1
No artifact exists. There is no repository, package, specification, or issue for it in any OIDM repository read for this knowledgebase. It appears only as stated direction.
The idea has precedent in the project’s own history. The About page states planned multi-language SDKs in TypeScript, Python, and C#, and a 2023 post proposed a plugin-container architecture for reporting-tool assistance applications.23 The libraries that do exist, findingmodel, anatomic-locations, and med-ontology-lookup, cover parts of the same ground for the semantic foundation but are not presented as this SDK.
Synonyms and near-synonyms
- Reporting SDK is the short form used in the deck.
- OIDM SDK and multi-language SDK refer to the older, broader plan from the About page.
- Reporting assistance framework is the 2023 proposal, a plugin architecture rather than a library.
- The existing OIDM Python packages are libraries for the semantic foundation, not this.
Identifier form
None.
Where it is used
Reporting SDK and Roadmap 2026. This knowledgebase records it as stated direction with no artifact, and says so wherever it appears.