# Best Practices

> **Quick tips:**
- Use clear, well-lit photos of the device screen — avoid glare and blur
- If the extracted data looks wrong, try retaking the photo with better lighting
- If your device image shows multiple readings (e.g. blood pressure and pulse), JondaX returns each one as a distinct item with units



## Image quality

- Use a clear, well-lit, straight-on photo of the device display.
- Avoid glare, blur, or partial cropping of the screen.
- Ensure the device reading is fully visible and in focus.


## Handling device responses

Each extraction result in `extractions[]` contains an `items` array representing the detected device(s) and their measurements:

```js
const result = response.data.extractions[0].result;

if (result.success && Array.isArray(result.items)) {
  result.items.forEach(item => {
    console.log(`Device: ${item.deviceType}`);
    console.log('Measurements:', item.data);
  });
}
```

## General

- Validate file size (max 25 MB) and format (JPEG, PNG, GIF, WEBP) on the client side before uploading.
- Store the API key securely and never expose it in client-side code.
- Handle unknown `deviceType` values and dynamic `data` keys gracefully — new device types are added over time.


## Rate limits

No published per-second or daily rate limits. For high-volume integrations, contact [support@jonda.health](mailto:support@jonda.health) to discuss capacity planning.

## Data retention

Medical Device extraction records are stored and accessible via the transformation history endpoint (`GET /api/master/transformations?module=medical`) and the file retrieval endpoint (`GET /api/master/medical/:id`). There is no `uploadId` for medical device uploads — use the `id` returned in the transformation history to retrieve specific records.

## Environments

There is currently no separate sandbox or test environment. Use your production API key against the live endpoint. Test with sample device images before going live.