Skip to content

medxchange/MedXChangeIntegrationAPIDocumentation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MedXChange Integration (MI) API

MedXChange provides programmatic access to case data and media items. The API is refered to as MIAPI, which stands for MedXChange IntegrationAPI.

The API is a REST API. All request/response formats are JSON.

SDK

  • TBD

Authentication

Before you can access any endpoint, you must first have a valid username and password setup on the device you are connecting with. Consult the manual for your MedXChange device to create a user that will be used for remote access to the device.

Every endpoint defined requires authentication, unless stated otherwise. A valid username and password must be provided to the [AUTHENTICATE] (endpoints/misc/authenticate.md) endpoint to retrieve a valid authentication token to use for each subsequent HTTP request. You must add the token to the header of each HTTP request being made to the device.

token: {your authentication token here}

If your authentication token is invalid, you will receive a HTTP 401 response with the following JSON response.

{
  "TokenStatus" : 2,
  "ErrorMessage" : "Your authorization token is invalid."
}

Request Headers

Since this is a json service, all requests headers should indicate that you are sending JSON data in the request and are expecting JSON data in the response.

Use these headers for every JSON request made to the device.

Content-Type: application/json; charset=utf-8
Accept: application/json

Endpoints

Miscellaneous

Cases

MediaItems

Physicains

Patient Fields

FAQ

  • TBD

What do I need to know before I start using the API?

Got rust on your skills? No worries. Here are the docs you might need to get started:

About

MedXChange Integration API Documentation

Resources

Stars

Watchers

Forks

Packages

No packages published