You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 10, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: index.html
+74-12Lines changed: 74 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,7 @@ <h1>Getting Started</h1>
187
187
<divclass="row">
188
188
<divclass="col-6">
189
189
<p>
190
-
This document outlines the behaviors expected from Intake API Version 2 (V2). The Workpath REST API provides programmatic access to
190
+
This document outlines the behaviors expected from Workpath's API for creating intakes and appointments. In Workpath, intakes are pre-appointment requests - incomplete data objects, and appointments are data objects used to track logistics for the patient, specimen, and specialist. The Workpath REST API provides programmatic access to
191
191
Workpath data for use in client applications and partner integrations. This is a working document as we continue to update our API.
192
192
</p>
193
193
<p>
@@ -196,13 +196,12 @@ <h1>Getting Started</h1>
196
196
</p>
197
197
<h4>Information We Need</h4>
198
198
<p>
199
-
To start the appointment process, we require a certain amount of information from you about your patient, the provider of your
200
-
patient, what labs you are wanting to run, and insurance information (if applicable). See the sections below about our endpoints you
199
+
To start the appointment process, we require a certain amount of information from you to complete the appointment including contact and location information for your patient and what labs/tests you want to complete. In some cases, you may need to provide information on Providers, patient payment/insurance information, and other specimen-related data; if you think you may need assistance with this information, click <ahref="https://help.workpath.co/en/" target="blank">here</a>. See the sections below about our endpoints you
201
200
will need in order to create a full appointment.
202
201
</p>
203
202
<p>
204
-
Access to our Client Management Dashboard can be found
Access to our Client Management Dashboard where you can review your auth methods and keys can be found
204
+
<ahref="https://api.workpath.co/clients" target="blank">here</a> after we create your environment and accounts.
206
205
</p>
207
206
</div>
208
207
</div>
@@ -340,7 +339,7 @@ <h3>3. Create an Intake</h3>
340
339
<divclass="row">
341
340
<divclass="col-6">
342
341
<p>
343
-
Using the access token that you requested in step two, you will then be able to create what we can an Intake! An intake will, in turn, create an appointment once the patient has filled out all of the required fields and submitted their response.
342
+
Using the access token that you requested in step two, you will then be able to create what we call an Intake! An intake will, in turn, create an appointment once the patient or provider has filled out all of the required fields and submitted their response.
344
343
</p>
345
344
<p>
346
345
The Create Intake details, such as request attributes and response JSON objects, are located <ahref="#CreateIntake">HERE</a> in these docs.
The access token returned by the token exchanges listed above are used as the bearer token for all subsequent requests to the API in the form of an auth header (<code>Authorization: Bearer [access token]</code>). Subsequent requests made using an expired or invalid token will return a <code>401 - Unauthorized response code</code>.
These are the endpoints you will need to hit in order to create a Patient, Guarantor, and an Insured Person for the Insurance Object
1193
+
In most cases, you will create your patient when submitting an intake. If not, these are the endpoints you will need to hit in order to create a Patient, Guarantor, and an Insured Person for the Insurance Object
1181
1194
later on.
1182
1195
</p>
1183
1196
</div>
@@ -1864,7 +1877,7 @@ <h1>Payment Object</h1>
1864
1877
<divclass="row">
1865
1878
<divclass="col-6">
1866
1879
<p>
1867
-
If you do not know this information, simply send us an empty object and we will request the information from your patient directly.
1880
+
While we do not process payments through Workpath, we can pass that information to be included for a lab to review. If you do not know this information, simply send us an empty object and we will request the information from your patient. We will not ask for credit card or other ACH payment information from a patient, but can pass information like Insurance Group Number to a lab partner where needed.
1868
1881
</p>
1869
1882
</div>
1870
1883
</div>
@@ -2104,7 +2117,10 @@ <h1>Intakes</h1>
2104
2117
<divclass="row">
2105
2118
<divclass="col-6">
2106
2119
<p>
2107
-
The Intake is the starting point for a patient request. The initial call takes in certain parameters about the patient and the service being ordered and, depending on the Order Form that is specified, sends a request to the patient (via email and/or SMS) for additional information.
2120
+
The Intake is the starting point for an appointment, and will trigger a patient request and other validations for ensuring Workpath has all necessary information for your patient’s appointment. The initial call takes in certain parameters about the patient and the service being ordered and, depending on the Order Form that is specified, sends a request to the patient (via email and/or SMS) for additional information.
2121
+
</p>
2122
+
<p>
2123
+
Before you get started with sending your Intakes, make sure you work with Workpath’s Customer Success team to set up your mock input forms, fields, and expected behavior so we can simulate the request and process as close to the future state.
2108
2124
</p>
2109
2125
</div>
2110
2126
</div>
@@ -2128,10 +2144,10 @@ <h4>Patient Requests</h4>
2128
2144
</p>
2129
2145
<ulstyle="list-style-type: circle;">
2130
2146
<li>
2131
-
If the Order Form is set to <strong>Auto-Publish</strong>, the Intake will be automatically converted to an Appointment.
2147
+
If Workpath has set <strong>auto-convert</strong> for your organization, the Intake will automatically be converted to an Appointment and released to the Workpath Network.
2132
2148
</li>
2133
2149
<li>
2134
-
If not, the Intake will populate within the "New" tab of the <strong>Service Requests</strong>tab on the web app. An Office User can then verify the Intake and convert it to an Appointment.
2150
+
If not, the Intake will populate within the "Pending Patient Request" tab of the <strong>Pending Appointments</strong>page on the web app. Once the patient responds, an Office User can then verify the Intake and convert it to an Appointment for release.
<p>Apply note to an appointment. Requires “Update appointment details” permission.</p>
4349
+
<p>
4350
+
Apply note to an appointment. Requires “Update appointment details” permission. Workpath uses and displays different types of notes depending on the user, status, and context; work with our Workpath Customer Success team to identify the ideal note type and contents for your workflow.
0 commit comments