Noa Notes Integration (v1)

Welcome to the Noa Notes Integration REST API!

This API is used to integrate Noa Notes with your existing systems. It allows you to create sessions, retrieve session statuses, and summaries.

Here is the available OpenAPI that you can import to Postman: noa_notes_integration.postman_collection.json.

Authentication

Authentication is based on clients of the API. The new client is set up by the Docplanner Team and provided to the development team of the client.

Sign In

Authenticates a client and returns an access token.

A client is a service that wants to use the Noa Notes API.

Authorizations:
Bearer
Request Body schema:
clientId
string <uuid>
secret
string or null

Responses

Request samples

Content type
{
  • "clientId": "5e505642-9024-474d-9434-e5a44f505cc5",
  • "secret": "string"
}

Response samples

Content type
No sample

Consumers

A consumer is an external system that consumes the Noa Notes Integration API.

Each client is meant to be a separate consumer.

The default configuration of the business logic for the other endpoints (e.g. default WebHook, Language, Speciality, Template) is being configured on the consumer level.

Get Current Consumer

Retrieves information about the currently authenticated consumer.

Authorizations:
Bearer
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

Create Session

Creates a new session.

In this endpoint, episodeId, doctorId, and facilityId are IDs coming directly from your software. We consider them as external IDs on our side.

If a session already exists for the given episodeId, doctorId, and facilityId tuple, and its status is not a final nor an error one, the existing session will be returned. It can allow you to resume a session UI-wise in the widget.

Authorizations:
Bearer
query Parameters
api-version
string
Request Body schema:
episodeId
required
string or null
doctorId
required
string or null
webhookUrl
string or null
object or null
visitType
string or null
Enum: "FirstVisit" "FollowUpVisit" null
  • FirstVisit - First visit for a patient
  • FollowUpVisit - Next visit for a patient
object or null
facilityId
string or null
language
string or null
Enum: "en-US" "pl-PL" "pt-BR" "pt-PT" "es-MX" "es-ES" "es-AR" "es-CO" "es-CL" "es-PE" "it-IT" "de-DE" "cs-CZ" "tr-TR" null
speciality
string or null

Responses

Request samples

Content type
{
  • "episodeId": "episode-123",
  • "doctorId": "doctor-456",
  • "template": {
    • "value": {
      • "Personal Information": "Include patient demographics and insurance information",
      • "Reason for the Visit": "Detailed description of the presenting problem"
      }
    },
  • "visitType": "FirstVisit",
  • "metadata": {
    • "key1": "value1",
    • "key2": "value2"
    },
  • "facilityId": "facility-789",
  • "language": "en-US",
  • "speciality": "psychiatrist"
}

Response samples

Content type
No sample

Get Session Summary

Retrieves the summary of a specific session. Returned data contains the content of the summary and information if a doctor approved its content in the Edit/Confirm Summary page.

Authorizations:
Bearer
path Parameters
sessionId
required
string <uuid>
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

Recover session summary

Recover the original summary content from the recorder. The completion of the recovery will be notified via webhook. Recovered summary needs to be verified again.

Authorizations:
Bearer
path Parameters
sessionId
required
string <uuid>
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

Regenerate session summary

Regenerate the original summary content from the recorder. The completion of the regeneration will be notified via webhook. Regenerated summary needs to be verified again.

Authorizations:
Bearer
path Parameters
sessionId
required
string <uuid>
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

ConsumerSessions

A session is meant to serve as a single usage of Noa Notes with a specific expiration time. The client needs to create a new session to receive a Noa Notes Recorder URL enabling the doctor to open the Noa Notes Recorder. The result of a session is a summary of the appointment, which should be used to populate EHR data in the client application.

Each session can be created with specific optional parameters, if not provided then default configuration from the consumer configuration will be applied.

Metadata parameters may contain any additional data that you want to share.

Get Session

Retrieves information about a specific session.

Authorizations:
Bearer
path Parameters
sessionId
required
string <uuid>
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

Get Session Status

Retrieves the status of a specific session.

This endpoint might be used proactively by the client to check statuses of a given session. An alternative scenario is for the client to expose a webhook that will be used by the Noa Notes Integration API to notify about status changes of the sessions.

Authorizations:
Bearer
path Parameters
sessionId
required
string <uuid>
query Parameters
api-version
string

Responses

Response samples

Content type
No sample

ExternalDoctors

/api/v1/facility/{externalFacilityId}/doctors

Authorizations:
Bearer
path Parameters
externalFacilityId
required
string

Responses

Response samples

Content type
No sample

/api/v1/facility/{externalFacilityId}/doctors

Authorizations:
Bearer
path Parameters
externalFacilityId
required
string
Request Body schema:
name
required
string or null
externalDoctorId
required
string or null

Responses

Request samples

Content type
{
  • "name": "string",
  • "externalDoctorId": "string"
}

Response samples

Content type
No sample

/api/v1/facility/{externalFacilityId}/doctors/{externalDoctorId}

Authorizations:
Bearer
path Parameters
externalFacilityId
required
string
externalDoctorId
required
string
Request Body schema:
name
required
string or null

Responses

Request samples

Content type
{
  • "name": "string"
}

Response samples

Content type
No sample

/api/v1/facility/{externalFacilityId}/doctors/{externalDoctorId}

Authorizations:
Bearer
path Parameters
externalFacilityId
required
string
externalDoctorId
required
string

Responses

Response samples

Content type
No sample