MDR: Platform API

The Platform API is your primary way to access the Medical Guidance Platform (MGP), an Infermedica product that supports patients and healthcare providers throughout the entire primary care journey—from symptom to outcome.

The Medical Guidance Platform and its modules are certified as Class IIb medical devices under the EU's Medical Device Regulation (MDR). This certification signifies our adherence to the highest standards of safety, quality, and clinical validation.

MDR Compliance Requirements

To use the MGP's medical certification, implementations based on the Platform API must be aligned with our interview types and undergo a post-implementation audit by our team.

For further details, please reach out to our team.

Certification Information Endpoint

The Platform API provides an /info endpoint that returns certification and device information required for MDR compliance. This endpoint can be used to display certification details in your application.

Endpoint

GET /api/mgp/v1/info

This endpoint does not require authentication and can be called without an access token.

Example Request

cURL

curl "https://api.infermedica.com/api/mgp/v1/info" \
  -X "GET" \
  -H "Instance-Id: <INSTANCE_ID>-mgp"

Response

A successful response returns a 200 OK status code with the following information:

JSON

{
  "version": "v6.15.0",
  "release_date": "2025-10-27",
  "medical_device": {
    "udi": "(01)05904610848036(11)251027(8012)6.15.0"
  },
  "manufacturer": {
    "name": "Infermedica Sp. z o.o.",
    "address": {
      "street": "ul. Plac Solny 14/3",
      "postal_code": "50-062",
      "city": "Wrocław",
      "country": "Poland"
    }
  },
  "instruction_url": "https://static.infermedica.com/mgp-statics/instructions/mgp/en/instruction.pdf",
  "snomed_ct_version": "http://snomed.info/sct/900000000000207008/version/20260501"
}

Response Fields

Field	Type	Description
`version`	string	The current version identifier of the Platform API
`release_date`	string	The release date of the current version in YYYY-MM-DD format
`medical_device`	object	Medical device certification information
`medical_device.udi`	string	Unique Device Identifier (UDI) as required by MDR
`manufacturer`	object	Information about the device manufacturer
`manufacturer.name`	string	Legal name of the manufacturer
`manufacturer.address`	object	Manufacturer's registered address
`manufacturer.address.street`	string	Street address
`manufacturer.address.postal_code`	string	Postal code
`manufacturer.address.city`	string	City
`manufacturer.address.country`	string	Country
`instruction_url`	string	URL to the instructions for use document
`snomed_ct_version`	string or `null`	The SNOMED CT release/version used for the SNOMED CT mappings, expressed as a SNOMED CT version URI. It is `null` when the version is unavailable (e.g. the Engine returns no version or an error occurs) or when the SNOMED CT feature is not enabled for your `app_id` / `app_key`.

ℹ️

/info does not require an access token, but it is scoped to your instance through the Instance-Id header (shown in the request above). Because your instance is provisioned against your app_id / app_key, the returned snomed_ct_version reflects your instance's configuration. This makes /info a quick way to check SNOMED CT availability. A non-null value means SNOMED CT data is present and tells you which version is in use. A null value means it is not available, and the snomed_ct fields will be absent from the other endpoints. See Enabling SNOMED CT mappings.

Usage

The information from this endpoint should be displayed in your application to meet MDR compliance requirements. This typically includes showing the UDI, manufacturer information, and providing access to the instructions for use.