Conclusion

Introduction
Request
Response
Definitions

Introduction

Once you've reached the end of your traversal - indicated by the empty node array on the response - you may call the conclusions endpoint (ReDoc).

This is a simple GET request to .../api/v2/{tenantId}/Traversals/{traversalId}/conclusions, and will return an array of Conclusion objects, shown below.

Note: if you're using the Online triage (aka Symptom Assessment) you may want to call the Conclusion Report, which will be ordered and categorised in a more meaningful way for you.

Request

1curl ".../api/v2/{tenantId}/Traversals/{traversalId}/conclusions" \
2  -X "GET" \
3  -H "Authorization: Bearer ACCESS_TOKEN" \

Response

1[
2  {
3    category1: "string",
4    subCategory: "string",
5    category2: "string",
6    title: "string",
7    moreDetail: "string",
8    priority: int,
9    propertyPriority: int,
10    information: boolean,
11    categoryTypeId: int,
12    silent: boolean,
13    data: {},
14    algoId: int,
15    nodeId: int,
16    assetId: int,
17    groupId: int,
18    displayText: "string",
19    clinicalText: "string",
20    counter: int,
21    nextNodeId: int,
22    explanation: "string",
23    bullets: [
24      {
25        data: {},
26        bulletId: int,
27        bulletUniqueId: int,
28        conclusionId: int,
29        priority: int,
30        displayText: "string",
31        category2: "string",
32      },
33    ],
34    truncated: "string",
35  },
36];

Definitions

Category1 : ...

Subcategory : ...