The MobileSmith platform uses RESTful web service calls for integration with data not hosted on a MobileSmith server – aka ‘remote data source’.
The REST service response must be in JSON format; we do not currently support XML responses.
The user’s device (containing the MobileSmith app) will communicate directly with the remote data source; MobileSmith server DOES NOT play ‘middle man’.
MobileSmith DOES NOT ever see/store data from remote servers.
HTTP and HTTPS requests are both supported.
Authentication - MobileSmith uses OAuth 2.0.
CRUD operations supported (Create, Read, Update, Delete).
Local data storage (caching) - The MobileSmith platform will obey the storage/caching rules specified in the JSON header returned from the REST service call. If the JSON header specifies “No Store” (for example), then the app will not store any data locally.
Pagination - The MobileSmith platform will allow the app creator to specify the “Next Page” URL from the JSON header in order to active pagination.
JSON Structures Supported
- Simple Object
- Simple Array (Array of Objects)
- Array of Primitives
- Primitives are currently displayed only in an app
- Primitives cannot currently be used for “Tap to call”, “Tap to email”, “Get directions”, or “Add to calendar”.
- Object containing an Array of Primitives
- FHIR HL7 support coming soon (MobileSmith is an active committee member)
JSON Structures NOT Supported
- An Array of Objects containing an Array of Objects – aka “Nested Object Arrays”
In the MobileSmith platform, every UI component (page) will have a specific REST Service URL to GET, PUT, POST, DELETE data. Common data fields (“id” for example) are used to pass arguments from one page to the next.