> For the complete documentation index, see [llms.txt](https://spice.docs.medtroniclabs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spice.docs.medtroniclabs.org/overview/frequently-asked-questions-faqs.md).

# Frequently Asked Questions (FAQs)

## What is SPICE used for?

SPICE supports community and primary care: registering households and members, screening, assessment, referrals, medical review, dispensing and follow-up. It currently covers maternal and child health, non-communicable diseases such as hypertension and diabetes, and eye care. See [Capabilities](https://spice.docs.medtroniclabs.org/overview/capabilities.md).

## Is SPICE compatible with other health systems?

Yes. SPICE stores clinical data in the HL7 FHIR format, so it can exchange data with other FHIR-compatible systems such as electronic medical records, health information exchanges and national health databases. Data can also be prepared for aggregate reporting platforms such as DHIS2. See [FHIR & Standards](https://spice.docs.medtroniclabs.org/architecture/architecture/fhir-and-standards.md).

## Can SPICE be customised for my programme?

Yes. Administrators can configure the administrative hierarchy, facilities, users and roles, clinical workflows and forms, medication and lab-test catalogues, and the languages offered in the app. Clinical decision-support rules follow published guidance and are not changed from the admin portal; contact us if your programme needs different clinical logic. See the [Admin Guide](https://spice.docs.medtroniclabs.org/admin-guide/admin-guide.md).

## Can SPICE work without an internet connection?

Yes. The mobile app is offline-first. Registration, screening, assessment and follow-up can be done without connectivity. The app stores the data in an encrypted database on the device and uploads it when a connection is available. See [Working Offline & Sync](https://spice.docs.medtroniclabs.org/user-guide/offline-and-sync.md).

## Which languages does SPICE support?

The mobile app and web applications can be translated. See [Multi-Language Translation](https://spice.docs.medtroniclabs.org/admin-guide/multi-language-translation.md).

## How secure is the data stored in SPICE?

SPICE uses role-based access control, authenticated sessions, encryption of data on the device and encryption in transit. See [Data Privacy & Security](https://spice.docs.medtroniclabs.org/privacy-and-security/data-privacy-and-security.md).

## Where is SPICE hosted?

SPICE can run on a major cloud provider or on-premise. Medtronic LABS can also host it as a service for partners. See [Deploy](https://spice.docs.medtroniclabs.org/deploy/deployment-guide.md) or email <community@medtroniclabs.org>.

## How often is SPICE updated, and what does it cost to update?

SPICE is updated regularly with new features, performance work and fixes based on user feedback. For hosted implementations, updates are rolled out periodically at no extra cost. For self-hosted implementations, release notifications go to newsletter subscribers. See [Releases](https://spice.docs.medtroniclabs.org/product/releases.md) and [Support](https://spice.docs.medtroniclabs.org/community/support.md).

## What support is available?

Email <community@medtroniclabs.org>, start a discussion on GitHub, or raise an issue. See [Support](https://spice.docs.medtroniclabs.org/community/support.md).
