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
Our demo website should have formatted data. To do this we can write a zambda that every day will create appointments for patients. To start with we can:
Call the create-appointment zambda with a test name that can be randomly generated
Some of the example appointments should fill out paperwork. We don't need to upload files for now.
The start time for prebooks should be random
Create appointments with different types
It's ok if they all share an account, but the problem is that we need to create appointments with a user account and the authorization for a user will stop working after ~1 day. To work around this, we can use a website that receives text messages and write code that will log in the user as well. We have some sample code for other projects that do this.
Since this is separate from the ottehr code, please put it in a new package.
The text was updated successfully, but these errors were encountered:
The issue was initially completed by implementing a zambda function that successfully created sample appointments for the demo environment. However, the function relied on a hardcoded token for authentication, which was a temporary solution.
To address the need for a more secure and sustainable authentication method, work on this task was paused. The new plan is to use a button from the provider chart to populate the necessary data, replacing the previous approach (see #316)
Our demo website should have formatted data. To do this we can write a zambda that every day will create appointments for patients. To start with we can:
The text was updated successfully, but these errors were encountered: