📄️ Introduction
Automation plugins are modular components that allow the app to communicate with medical devices or software systems (such as EMRs, FHIR servers, or surveillance databases).
📄️ Devices
Each device plugin must export a start function that receives a context object. This context contains everything you need to:
📄️ Systems
System plugins allow Automation to exchange data with external platforms such as EMRs, national surveillance systems, DHIS2, and other databases that need structured medical device data.
📄️ Testing
When developing a plugin for Automation, you can run and test it locally without needing the full Automation stack.
📄️ Publishing
To make your plugin available in Automation, you must register on the Plugin Portal and submit it as an npm-compatible package using npm pack.
📄️ Documenting
Each plugin must include a README.md file written for users and integrators, not developers. It should provide practical, clear instructions on how to set up and use the plugin — based on the actions it supports.