# File Record API (Partner APIs) Data format and display order

**URL:** <https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808>\
**Category:** API Platform\
**Tags:** testing, api, integration, emis\
**Created:** [23 September 2025 10:15 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808 "2025-09-23T10:15:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ali.musa](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@ali.musa](https://developer.community.nhs.uk/u/ali.musa)\
**Post date:** [23 September 2025 10:15 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808/1 "2025-09-23T10:15:31Z")

</div>

Hi all,

I wanted to check if there’s a way to control the display order in the File Record API. For example, I’d like **History** to appear at the top, followed by **Message** , and then **Comment,** and at the end document.

I also wanted to ask if it’s possible to format the data (e.g., bold text, line breaks, etc.) when displaying through the Partner File Record API.

Additionally, I’ve attached a screenshot for your reference (test instance with test data).

@navin.bose

 ![image](https://europe1.discourse-cdn.com/nhsdigitaldeveloper/original/1X/02e540a606ff527c2cc61420526be69714733b1c.png)

Thanks!

---

<div class="post-metadata">

**Author:** ![Bhargav\_V](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bhargav\_V](https://developer.community.nhs.uk/u/Bhargav_V)\
**Post date:** [23 September 2025 11:39 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808/2 "2025-09-23T11:39:18Z")

</div>

Hi. you can very well control the order of the display. Not sure about formatting of data. To control the order of the display, use Consultation Element Tag and insert data the order in which you want it to appear in EMIS

---

<div class="post-metadata">

**Author:** ![ali.musa](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@ali.musa](https://developer.community.nhs.uk/u/ali.musa)\
**Post date:** [24 September 2025 08:42 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808/3 "2025-09-24T08:42:22Z")

</div>

Thank you for your response.

I think you might be referring to the **DisplayOrder** key. I tried setting this from 0 to 3 (0 for History, 1 for Message, 2 for Comment, and 3 for Document), but it didn’t work; the records are still not displayed in that sequence.

---

<div class="post-metadata">

**Author:** ![Bhargav\_V](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bhargav\_V](https://developer.community.nhs.uk/u/Bhargav_V)\
**Post date:** [24 September 2025 09:13 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808/4 "2025-09-24T09:13:38Z")

</div>

Hi. No not like that. I am talking about Consultation Element tag itself not the display order inside it. While attaching the xml, eg

 ![image](https://europe1.discourse-cdn.com/nhsdigitaldeveloper/original/1X/7c96089d0f4737228c2d377644d7226495acbc6b.png)

Try and let me know. We do this often in our solution and we face no issues.

---

<div class="post-metadata">

**Author:** ![ali.musa](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@ali.musa](https://developer.community.nhs.uk/u/ali.musa)\
**Post date:** [24 September 2025 10:53 UTC](https://developer.community.nhs.uk/t/file-record-api-partner-apis-data-format-and-display-order/7808/5 "2025-09-24T10:53:28Z")

</div>

I tried implementing this, but it still isn’t working as expected.