The Android FHIR SDK is a set of Kotlin libraries for building offline-capable, mobile-first healthcare applications using the HL7® FHIR® standard on Android.
APACHE-2.0 License
Published by Tarun-Bhardwaj about 3 years ago
This engine-0.1.0-alpha05
release contains the following enhancements and fixes
Enhancements:
Bugs:
None
Reference App (Enhancements):
Reference App (Bugs):
Published by Tarun-Bhardwaj about 3 years ago
This 0.1.0-alpha05
release of the data capture library adds support for choice and open-choice questions as well as handling ValueSets and ValueSet lookups within questionnaires. It also includes updates to existing features and bug fixes.
New features:
Bug fixes: (Includes bugs that may have been part of the earlier releases)
Published by jingtang10 about 3 years ago
This engine-0.1.0-alpha04
release contains the following enhancements and fixes
Enhancements:
Bugs:
Reference App:
Published by fredhersch about 3 years ago
This sdc-0.1.0-alpha04
release contains the following enhancements and fixes
Bug fixes:
New features:
Published by fredhersch over 3 years ago
The 0.1.0-alpha03
release of the FHIR Engine library adds additional features to the search, sync and data-access APIs
Search API
Sync API
Data access API
Published by fredhersch over 3 years ago
This 0.1.0-alpha03
release of the data-capture library will add in the additional features in line with the FHIR SDC Specification. The following items have been added:
Published by jingtang10 over 3 years ago
The 0.1.0-alpha02
release of the FHIR Engine library includes the following enhancements / fixes:
Published by jingtang10 over 3 years ago
The 0.1.0-alpha01
release of the FHIR Engine library allows Android developers to begin to develop offline capable native FHIR applications. The goal of this early release is to gather feedback from developers and identify critical issues that need to be addressed. As an early release APIs are subject to change.
The FHIR Engine Library provides a set of core features that are the foundation for a FHIR compliant Android application. These include SQLite database storage layer, data access APIs for interacting with the storage layer, search API for retrieving relevant resources and the sync API for communication between a FHIR server and the device.
When used together with the SDC Library, application developers are able to start to piece together an end to end FHIR compliant android client that can act as a stand-alone application or as part of a client-server architecture.
Please refer to the User's Guide of the wiki for relevant examples. The SDK is a community collaboration. To submit feature requests and suggestions about specific use cases, see Feedback. To contribute to the codebase, see Contributing.
SQLite database for FHIR resources
Supported functionality
Future work
Data Access APIs
Data access layer to interact with the SQLite database. Provides CRUD capabilities and support for synchronisation.
Current functionality
Future work (gathering requirements)
Search API
The on-device search API using Kotlin DSL allows applications to compose complex search queries to filter FHIR resources and build lists. Indexing all search parameters in the database for faster look-ups
Current functionality
Future work
Sync API
Allows developers to define the resources to be synchronized between a FHIR server and the local SQLite database.
Current functionality
Future work
Published by jingtang10 over 3 years ago
The 0.1.0-alpha02
release of the data capture library changes the underlying data model from FHIR Proto to HAPI Structures. The main reason behind this shift is developer familiarity and utilities available for the HAPI structures library.
Additionally, this release includes the following features and fixes:
Published by jingtang10 over 3 years ago
The 0.1.0-alpha01
release of the data capture library allows Android developers to use a FHIR questionnaire to create a fragment which captures the user's input and generates a FHIR questionnaire response.
Supported widget types:
Additional functionality:
Future work:
Known issues: