A log is a step-by-step record of what data was exchanged, including the request, operation, and payload details. You can view and search successful, failed, or pending logs in the Redox dashboard from the last 60 days. Learn more about logs.
Search for a specific log or use the log filters to narrow down the list of logs.
This article describes how to search for logs in the Redox dashboard. To search for logs via API, use these Redox Platform API endpoints instead:
While you can search log metadata or payloads via API, you won’t receive log payloads in the responses. You can only review log payload contents in the Redox dashboard.
- Any user can search and view log metadata. However, a user must be assigned to a support or an engineer role to search and view log payloads.
- Log in to the Redox dashboard.
- From the navigation menu, click the Logs page.
- By default, the logs search bar and filters display, along with any logs for the last 7 days. Use search terms, filters, or a combination of both to search for logs.
- For search filters, select options from any of these drop-down fields:
- Connection
- Sources / destinations
- Date range (use start date, end date, or both)
- Data model
- Event type (only enabled if the Data model filter is populated)
- Type
- Status
![Log filters Log filters]()
Log filters Extra search filtersDepending on the setup of your Redox organization, you may see extra log filters.
- Multi-region organizations have a Region filter with options for your relevant cloud provider region.
- Organizations with backfill data have a Database filter for searching historical or production logs.
- For search terms, review our searchable fields at the end of this article. Then, enter any of these values into the search bar based on the supported searchable fields:
- metadata identifiers (This is the only search term option available to users assigned to observer roles.)
- patient ID or namePatient name tips
Patient name must be in either FirstName LastName or LastName format.
For FHIR® logs, you can only search by patient name in these resources: FHIR® Patient or FHIR® Practitioner.
No fuzzy matchingLog searches are case-insensitive but use exact terms. In other words, we don’t support fuzzy matching, and we don’t correct typos in a search string. If you type “Jane Gibons” but meant to search for “Jane Gibbons”, Redox strictly searches for and returns results for “Jane Gibons.”
- provider ID
- visit number or ID
- record (i.e., any other ID value specific to a data model)
- After entering search criteria, the list of search results display on the left side of the page. Each log entry shows the status of the log. Learn about log statuses.
- Click on any of the results to view the log details. Click any log processing stage to view the details or the payload (if applicable).
![A user scrolls through the log processing stages and details. A user scrolls through the log processing stages and details.]()
Log details Operation details in logsIf a log has used any custom operations, you can view the related operation details when you click the related processing stage. Learn about data operations and:
- If you want to share a log with a team member, click the copy link icon next to the log ID.
![The copy icon appears to the right of the log ID. The copy icon appears to the right of the log ID.]()
Share a log
We support searching for terms in specific fields for a given Redox data model or Redox FHIR® resource / notification. That means if you try to search for a keyword that would exist in a different field than one listed below, we won’t return any matching logs.
Review searchable fields by data model type.
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Batch[*].Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Batch[*].Patient.Demographics.FirstName Batch[*].Patient.Demographics.LastName |
Provider | Claims[*].Providers[*].ID BillingProvider.ID Batch[*].Claims[*].Providers[*].ID Batch[*].BillingProvider.ID |
Record | Transaction.ID Subscriber.ID Claims[*].ID Claims[*].ReferenceNumbers[*].ID Batch[*].Transaction.ID Batch[*].Subscriber.ID Batch[*].Claims[*].ID Batch[*].Claims[*].ReferenceNumbers[*].ID |
Visit | Claims[*].Visit.Number Batch[*].Claims[*].Visit.VisitNumber Claims[*].Visit.Location.Facility Claims[*].Visit.Location.Department |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Header.Patient.Identifiers[*].ID Header.Patient.Demographics.FirstName Header.Patient.Demographics.LastName |
Provider | Header.Document.Author.ID Header.PCP.ID Documents[*].Author.ID |
Record | Header.Document.ID Documents[*].ID Document.ID |
Visit | Header.Document.Visit.VisitNumber Header.Document.Visit.Location.Facility Header.Document.Visit.Location.Department Visit.VisitNumber Documents[*].Visit.ID |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.ReferringProvider.ID Visit.ConsultingProvider.ID Visit.Procedures[*].Performers[*].ID Transactions[*].Performers[*].ID Transactions[*].OrderingProviders[*].ID Procedures[*].Performers[*].ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName Transactions[*].Performers[*].FirstName Transactions[*].Performers[*].LastName |
Record | Transactions[*].ID Transactions[*].Department.Code Transactions[*].OrderID |
Visit | Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Media[*].Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Media.Provider.ID Media.Authenticator.ID Media.Provider.FirstName Media.Provider.LastName |
Record | DocumentIDs[*] Media.DocumentID Media.OriginalDocumentID Media.Notifications[*].ID Media[*].DocumentID |
Visit | Visit.VisitNumber VisitNumbers[*] Media[*].Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.ReferringProvider.ID Order.Provider.ID Order.Provider.NPI Order.EnteredBy.ID Order.VerifiedBy.ID Administrations[*].AdministeringProvider.NPI Administrations[*].AdministeringProvider.ID Administrations[*].OrderedBy.ID Administrations[*].VerifiedBy.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName Order.Provider.FirstName Order.Provider.LastName |
Record | Order.ID Administrations[*].Medication.Order.ID |
Visit | Visit.VisitNumber Visit.Location.Facility Visit.Location.Department |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Notes[*].Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Note.Provider.ID Note.Authenticator.ID Note.Provider.FirstName Note.Provider.LastName |
Record | DocumentIDs[*] Orders[*].ID Note.DocumentID Note.OriginalDocumentID Note.Notifications[*].ID Notes[*].DocumentID |
Visit | Visit.VisitNumber VistNumbers[*] Notes[*].Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Orders[*].Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Order.Provider.ID Order.Provider.NPI Orders[*].Provider.NPI Orders[*].Provider.ID Visit.AttendingProvider.ID Visit.ReferringProvider.ID Visit.ConsultingProvider.ID Order.Provider.FirstName Order.Provider.LastName Orders[*].Provider.FirstName Orders[*].Provider.LastName Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName |
Record | Order.ID Order.Procedure.Code Order.ApplicationOrderID Orders[*].ID Orders[*].ApplicationOrderID Orders[*].Procedure.Code OrderIDs[*] Order.ClinicalInfo[*].Value Orders.ClinicalInfo[*].Value |
Visit | Visit.VisitNumber VistNumbers[*] Orders[*].Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Patient.PCP.NPI Patient.PCP.ID Visit.AdmittingProvider.ID Visit.AttendingProvider.ID Visit.ReferringProvider.ID Visit.ConsultingProvider.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName |
Visit | Patients[*].Visits[*].VisitNumber Patients[*].Visits[*].Location.Facility Patients[*].Visits[*].Location.Department Visit.VisitNumber VisitNumbers[*] Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.ReferringProvider.ID Visit.ConsultingProvider.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName |
Record | Education[*].InstanceID |
Visit | Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName |
Provider | Referrals[*].Providers[*].ID Referrals[*].Providers[*].FirstName Referrals[*].Providers[*].LastName Referral.Providers[*].ID Referral.Providers[*].FirstName Referral.Providers[*].LastName |
Record | Referral.ID Referral.Authorization.Number Referrals[*].ID Referrals[*].Authorization.Number |
Visit | Visit.VisitNumber Referral.Visit.VisitNumber Referrals[*].Visit.VisitNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patients[*].Identifiers[*].ID Orders[*].Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName Visit.ReferringProvider.ID Orders[*].Provider.ID Orders[*].Provider.NPI Orders[*].Results[*].PrimaryResultsInterpreter.ID Orders[*].Results[*].PrimaryResultsInterpreter.NPI Orders[*].Results[*].Producer.ID Orders[*].Results[*].Performer.ID Orders[*].ResultCopyProviders[*].ID Orders[*].Provider.FirstName Orders[*].Provider.LastName |
Record | Orders[*].ID OrderIDs[*] Procedures[*].Code Orders[*].Procedure.Code |
Visit | Visit.VisitNumber Orders[*].Visit.VisitNumber Visit.Location.Facility Visit.Location.Department |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Visit.Patients[*].Identifiers[*].ID Visits[*].Patient.Identifiers[*].ID Visits[*].Patient.Demographics.FirstName Visits[*].Patient.Demographics.LastName Patient.Demographics.FirstName Patient.Demographics.LastName Patients[*].Demographics.FirstName Patients[*].Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName Visit.ReferringProvider.ID Visit.ConsultingProvider.ID Visit.VisitProvider.ID Visit.VisitProvider.FirstName Visit.VisitProvider.LastName Visit.AttendingProviders[*].ID Visit.AttendingProviders[*].FirstName Visit.AttendingProviders[*].LastName Visits[*].AttendingProvider.ID Visits[*].AttendingProvider.FirstName Visits[*].AttendingProvider.LastName Visits[*].ConsultingProvider.ID Visits[*].ReferringProvider.ID Visits[*].VisitProvider.ID Visits[*].VisitProvider.FirstName Visits[*].VisitProvider.LastName Slots[*].Provider.ID AvailableSlots[*].Provider.ID |
Record | Slots[*].ID AvailableSlots[*].ID |
Visit | Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.Locations[*].Facility Visit.Locations[*].Department Visits[*].VisitNumber Visits[*].Location.Facility Visits[*].Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName |
Provider | Visit.AttendingProvider.ID Visit.AttendingProvider.FirstName Visit.AttendingProvider.LastName SurgeryStaff[*].ID |
Record | Procedures[*].Code SurgicalCase.Number |
Visit | Visit.VisitNumber Visit.Location.Facility Visit.Location.Department Visit.AccountNumber |
Category | Searchable fields |
|---|---|
Patient | Patient.Identifiers[*].ID PotentialMatches[*].Identifiers[*].ID Patient.Demographics.FirstName Patient.Demographics.LastName PotentialMatches[*].Demographics.FirstName PotentialMatches[*].Demographics.LastName |
Provider | Patient.PCP.NPI Patient.PCP.ID Vaccinations[*].Provider.ID Vaccinations[*].Order.Provider.ID Vaccinations[*].Order.Provider.NPI PotentialMatches[*].PCP.NPI PotentialMatches[*].PCP.ID |
Record | Vaccinations[*].Order.ID |
Visit | Visit.VisitNumber Visit.AccountNumber |
Review the list of supported searchable fields by FHIR® resource type. Keep in mind that only some FHIR® interactions or operations are searchable. Learn about FHIR® interactions and operations.
For all of these fields, we only index the patient id value. For example, for Patient/123, you can only search for the 123 value.
FHIR® | Log type | Searchable fields |
|---|---|---|
read | RESPONSE | identifier[].value code.coding[].code subject.reference |
_search | REQUEST | patient[*] |
_search | RESPONSE | entry[?(@.resource.resourceType== "DiagnosticReport")].resource.subject.reference entry[?(@.resource.resourceType== "Patient")].resource.id entry[?(@.resource.resourceType== "Patient")].resource.identifier[*].value entry[?(@.resource.resourceType== "DiagnosticReport")].resource.subject.identifier.value |
$diagnosticreport-* | REQUEST | identifier[].value code.coding[].code |
All Document notifications | REQUEST | All fields listed above |
For all of these fields, we only index the patient id value. For example, for Patient/123, you can only search for the 123 value.
FHIR® | Log type | Searchable fields |
|---|---|---|
read | RESPONSE | masterIdentifier.value subject.reference |
_search | REQUEST | patient[*] |
_search | RESPONSE | masterIdentifier.value entry[?(@.resource.resourceType== "DocumentReference")].resource.subject.reference entry[?(@.resource.resourceType== "Patient")].resource.id entry[?(@.resource.resourceType== "Patient")].resource.identifier[*].value entry[?(@.resource.resourceType== "DocumentReference")].resource.subject.identifier.value |
$documentreference-* | REQUEST | masterIdentifier.value |
For all of these fields, we only index the patient id value. For example, for Patient/123, you can only search for the 123 value.
FHIR® | Log type | Searchable fields |
|---|---|---|
read | RESPONSE | identifiers[].value subject.reference |
_search | REQUEST | patient[*] |
_search | RESPONSE | identifiers[].value entry[?(@.resource.resourceType== "Encounter")].resource.subject.reference entry[?(@.resource.resourceType== "Patient")].resource.id entry[?(@.resource.resourceType== "Patient")].resource.identifier[*].value entry[?(@.resource.resourceType== "Encounter")].resource.subject.identifier.value |
$encounter-* | REQUEST | identifiers[].value |
All PatientAdmin notifications | REQUEST | All fields listed above |
For all of these fields, we only index the patient id value. For example, for Patient/123, you can only search for the 123 value.
FHIR® | Log type | Searchable fields |
|---|---|---|
read | RESPONSE | subject.reference |
_search | REQUEST | patient[*] |
_search | RESPONSE | entry[?(@.resource.resourceType== "Observation")].resource.subject.reference entry[?(@.resource.resourceType== "Patient")].resource.id entry[?(@.resource.resourceType== "Patient")].resource.identifier[*].value entry[?(@.resource.resourceType== "Observation")].resource.subject.identifier.value |
FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.


