Digital Health is used more and more. We don’t want nurses and doctors to retype information or get lost in all their healthcare apps. And we want patients to have the best experience, using the apps they already love. Therefore with Luscii Integrations we offer developers LusciiKit HCP and LusciiKit PAT so they can embed our best in class remote patient monitoring capabilities in their own applications using open standards such as HL7 FHIR and Snomed. As a developer you will find all technical information on this page.
This table describes several frequently used terms and their definitions that are relevant.
| Name | Example | Definition |
|---|---|---|
| External Company | EPIC / Cerner / Meditools | A company working in the healthcare ecosystem that may have several External Products in the market. |
| Partner | ChipSoft / BeterDichtbij | An External Company with whom Luscii has a Partnership agreement. |
| External Product | EPIC on FHIR / MediKit (from Meditoosls) | An application or service of an External Company that our (future) Customers are using in the healthcare ecosystem. |
| Connected Product | Zorgplatform (from ChipSoft) | An External Product with which Luscii has an Integration with. |
| Integration | Zorgplatform Integration | A verified service that Luscii can provide to enable Luscii and a Connected Product to work functionally together for a Customer. |
| Customer | OLVG / JBZ | A hospital that uses Luscii. |
| Implemented Integration | Zorgplatform Integration for JBZ | An available Integration that is enabled for a Customer. |
Luscii has an open architecture based on HL7 FHIR. Here you can find more on our open architecture as well as the Integration process for validating new integrations.
Luscii - how to integrate explaned.pdf
Luscii Integration Architecture 🚧
<aside> 🚧 Under Construction
</aside>
<aside> 🚧 Under Construction
</aside>
<aside> 🚧 Under Construction
</aside>
<aside> 🚧 Under Construction
</aside>