Build your own extension
Why an extension gets built, whether it should be public or private, and what needs installing to start.
Building an extension lets a care flow drive actions in a system Awell doesn't already connect to.
Proprietary apps and vendor tools
Proprietary apps. Where a customer runs its own patient app, care team portal, or homegrown electronic health record, a private extension lets non-engineer colleagues build care flows that drive actions in those apps from the no-code builder. The connector is written once, then used by clinical colleagues without coming back to engineering.
Vendor tools. Where care providers already use a vendor's tool, a public extension featured on the Marketplace means any Awell customer can build care flows that drive actions in it.
Public or private
| Public | Private | |
|---|---|---|
| Lives in | Awell's awell-extensions repository | The customer's own organization |
| Visible to | Every Awell customer, via the Marketplace | The organization that built it |
| Built by | Awell, or an outside contributor | The customer's own team |
A public extension goes in Awell's repository. Check it out locally to start contributing. See Contributing guidelines.
Prerequisites: Node, Yarn, TypeScript
Install Node and Yarn. Setup instructions for VS Code are in the repository.
Extensions are written in TypeScript, so this is engineering work, not configuration.
Next steps
Next: Create an extension.