Skip to main content
POST
Resolve Unmatched Result

This feature is in closed beta.Interested in this feature? Get in touch with your Customer Success Manager.

Authorizations

x-vital-api-key
string
header
required

Vital Team API Key

Path Parameters

raw_result_id
string<uuid>
required

Body

application/json
action
enum<string>
required

ℹ️ This enum is non-exhaustive.

Available options:
reject,
unsure
note
string | null

Response

Successful Response

id
string<uuid>
required
status
enum<string>
required

ℹ️ This enum is non-exhaustive.

Available options:
matched,
pending_customer_review,
pending_ops_review,
resolved
decision_code
enum<string>
required

ℹ️ This enum is non-exhaustive.

Available options:
match_sample_id,
match_completed,
match_cancelled,
wrong_collection,
wrong_lab,
multiple_demo_match,
match_sample_id_mismatch_demo,
match_demo,
no_match
reason
string
required
lab
MatchReviewLab · object
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
sub_reason_codes
enum<string>[]

ℹ️ This enum is non-exhaustive.

Available options:
lab_account_mismatch
patient
MatchReviewPatient · object | null
markers
MatchReviewMarker · object[]
interpretation
enum<string> | null

ℹ️ This enum is non-exhaustive.

Available options:
normal,
abnormal,
critical,
unknown
result_status
enum<string> | null

ℹ️ This enum is non-exhaustive.

Available options:
final,
partial
note
string | null
allowed_actions
enum<string>[]

ℹ️ This enum is non-exhaustive.

Available options:
accept,
reject,
unsure
candidate_groups
MatchReviewCandidateGroup · object[]
reviewed_at
string<date-time> | null