Aaron Lim

Lyrebird Scribe Integration

Outcomes

  • Released one of the first AI scribe integrations within the GP practice management system community

 

  • Integration provided single sign on functionality and the ability to write back notes and observations from Lyrebird into the consult in Bp Premier

 

  • Providers reporting benefits from reduced time in note taking through the integration, allowing them to focus more on patient care

 

  • Integration user base has grown from launch up to over 1000 practices currently

 

  • The integration gained exposure and curiosity for the business and AI in Clinical IT

Timelines

  • October 2023 - November 2023
    • Design and reviews
  • November 2023 - January 2024
    • Development and testing
  • February 2024 - May 2024
    • Beta testing
  • May 2024
    • Production release

Role

  • Product owner
  • Product designer

Context

In 2023, advancements in AI resulted in high quality scribing tools being developed. Our team was tasked with developing an integration with Lyrebird Scribe, an upcoming clinical notetaking scribe. The goal was to create a workflow where a doctor could easily launch out to Lyrebird during a consult and have it listen and produce a summary of notes back into Bp.

 

Reducing the number of clicks and manual copying and pasting a doctor would currently do between the platform would save time and money, and ultimately allow the provider to focus on the patient with them.

Analysis and design

We had been tasked to get a first phase out as soon as possible, and to achieve that our thoughts were to reuse existing flows and functionality as much as we could and avoid reinventing the wheel.

 

As the functionality had been implemented in our different products in the past we knew was feasible from technical standpoint and development could reference it to make their work quicker.

 

  • API Keys for SSO

As more complex authentication methods would take time from both Lyrebird and as, we referenced a recent integration we built with Physitrack.

 

API keys could be generated for users in Physitrack which were then recorded in the user settings of the integrating platform. This key was used as part of the SSO authentication process when launching Physitrack from our applications.

 

It was a more manual process for the user to generate and store keys, but it could be quickly implemented to assist SSO authentication..

 

  • Browser window

Bp Premier had an in-built chromium browser so it was viable option to launch Lyrebird within this.

 

Having the browser attached to Bp Premier allowed us to have greater control over data being passed back and forth and the number of Lyrebird sessions open to prevent the user from cluttering and losing track of clinical data that had not been saved. This also avoided any issues with the browser the user might have installed on their maching.

 

These designs and workflows were present to multiple product teams, along with internal and external clinical advisors to gather feedback and refine items.

Initial mockups for storing the Lyrebird API Key, the Lyrebird launch button and the internal browser running Lyrebird during a consult

Lyrebird API key storage

For the SSO process, users would generate a unique API Key and save it to their account in Bp Premier. This key is encrypted and securely stored in the database.

 

This encrypting key is used during the Lyrebird launching process to quickly log into their account, so they can jump into transcribing sooner.

Launching Lyrebird in a consult

Lyrebird can be launched through the main taskbar in the consult window. A quick launch button makes it easier for the provider to access it during a patient consult.

Patient matching

SSO occurs on launching Lyrebird from a consult and an API is stored for the provider. Lyrebird runs in the internal browser, and the session is populated with the patient’s details and is ready to record patient consent and begin transcribing.

Writing back of Lyrebird notes

Once the transciprtion is ready, the provider can review the notes generated and add observations before sending the data back to the consult in Bp Premier through a click of a button.

During the rollout process I performed multiple internal training session for teams such as sales and support to educate them on the upcoming Lyrebird feature. I also assisted with demonstrating the integration to external stakeholders as part of different review processes.

 

As the first phase of this project wrapped up I moved to a UX role in a different product team. With this I mentored a product owner and business analyst on the feature and feedback we had gathered so they could continue the next phase of the integration. This integration has continued to improve it’s functionality and stability upon the first phase that was implemented.

Conclusion

What went well:

  • Teams were excited to be creating an integration with new technology that could really change how our providers work day to day, and the experience that patients receive

 

  • Feedback from many testers was invaluable as we had a working version of the first phase

 

  • Aiming to reuse workflows and functionality drawn from within our own applications and inspired by others allowed us to get the first phase designed quickly and with confidence that it was achievable

What I would improve:

  • Being prepared with better methods of collating and managing beta feedback - it was a bit chaotic receiving feedback from users through emails, teams, via colleagues they were interacting with etc. It was difficult to keep track of everything being collated, which team should be looking at it and updates on it

 

  • A single form or portal could have been a one stop shop where the data could then land in one location and be sorted.

Key takeaways:

  • Drawing on existing workflows from internal and external timeframes

 

  • User feedback is better than anything you could try to predict or assume
Aaron Lim

Lyrebird Scribe Integration

Outcomes

  • Released one of the first AI scribe integrations within the GP practice management system community

 

  • Integration provided single sign on functionality and the ability to write back notes and observations from Lyrebird into the consult in Bp Premier

 

  • Providers reporting benefits from reduced time in note taking through the integration, allowing them to focus more on patient care

 

  • Integration user base has grown from launch up to over 1000 practices currently

 

  • The integration gained exposure and curiosity for the business and AI in Clinical IT

Timelines

  • October 2023 - November 2023
    • Design and reviews
  • November 2023 - January 2024
    • Development and testing
  • February 2024 - May 2024
    • Beta testing
  • May 2024
    • Production release

Role

  • Product owner
  • Product designer

Context

In 2023, advancements in AI resulted in high quality scribing tools being developed. Our team was tasked with developing an integration with Lyrebird Scribe, an upcoming clinical notetaking scribe. The goal was to create a workflow where a doctor could easily launch out to Lyrebird during a consult and have it listen and produce a summary of notes back into Bp.

 

Reducing the number of clicks and manual copying and pasting a doctor would currently do between the platform would save time and money, and ultimately allow the provider to focus on the patient with them.

Analysis and design

We had been tasked to get a first phase out as soon as possible, and to achieve that our thoughts were to reuse existing flows and functionality as much as we could and avoid reinventing the wheel.

 

As the functionality had been implemented in our different products in the past we knew was feasible from technical standpoint and development could reference it to make their work quicker.

 

  • API Keys for SSO

As more complex authentication methods would take time from both Lyrebird and as, we referenced a recent integration we built with Physitrack.

 

API keys could be generated for users in Physitrack which were then recorded in the user settings of the integrating platform. This key was used as part of the SSO authentication process when launching Physitrack from our applications.

 

It was a more manual process for the user to generate and store keys, but it could be quickly implemented to assist SSO authentication..

 

  • Browser window

Bp Premier had an in-built chromium browser so it was viable option to launch Lyrebird within this.

 

Having the browser attached to Bp Premier allowed us to have greater control over data being passed back and forth and the number of Lyrebird sessions open to prevent the user from cluttering and losing track of clinical data that had not been saved. This also avoided any issues with the browser the user might have installed on their maching.

 

These designs and workflows were present to multiple product teams, along with internal and external clinical advisors to gather feedback and refine items.

Initial mockups for storing the Lyrebird API Key, the Lyrebird launch button and the internal browser running Lyrebird during a consult

Lyrebird API key storage

For the SSO process, users would generate a unique API Key and save it to their account in Bp Premier. This key is encrypted and securely stored in the database.

 

This encrypting key is used during the Lyrebird launching process to quickly log into their account, so they can jump into transcribing sooner.

Launching Lyrebird in a consult

Lyrebird can be launched through the main taskbar in the consult window. A quick launch button makes it easier for the provider to access it during a patient consult.

Patient matching

SSO occurs on launching Lyrebird from a consult and an API is stored for the provider. Lyrebird runs in the internal browser, and the session is populated with the patient’s details and is ready to record patient consent and begin transcribing.

Writing back of Lyrebird notes

Once the transciprtion is ready, the provider can review the notes generated and add observations before sending the data back to the consult in Bp Premier through a click of a button.

During the rollout process I performed multiple internal training session for teams such as sales and support to educate them on the upcoming Lyrebird feature. I also assisted with demonstrating the integration to external stakeholders as part of different review processes.

 

As the first phase of this project wrapped up I moved to a UX role in a different product team. With this I mentored a product owner and business analyst on the feature and feedback we had gathered so they could continue the next phase of the integration. This integration has continued to improve it’s functionality and stability upon the first phase that was implemented.

Conclusion

What went well:

  • Teams were excited to be creating an integration with new technology that could really change how our providers work day to day, and the experience that patients receive

 

  • Feedback from many testers was invaluable as we had a working version of the first phase

 

  • Aiming to reuse workflows and functionality drawn from within our own applications and inspired by others allowed us to get the first phase designed quickly and with confidence that it was achievable

What I would improve:

  • Being prepared with better methods of collating and managing beta feedback - it was a bit chaotic receiving feedback from users through emails, teams, via colleagues they were interacting with etc. It was difficult to keep track of everything being collated, which team should be looking at it and updates on it

 

  • A single form or portal could have been a one stop shop where the data could then land in one location and be sorted.

Key takeaways:

  • Drawing on existing workflows from internal and external timeframes

 

  • User feedback is better than anything you could try to predict or assume
Aaron Lim

Lyrebird Scribe Integration

Outcomes

  • Released one of the first AI scribe integrations within the GP practice management system community

 

  • Integration provided single sign on functionality and the ability to write back notes and observations from Lyrebird into the consult in Bp Premier

 

  • Providers reporting benefits from reduced time in note taking through the integration, allowing them to focus more on patient care

 

  • Integration user base has grown from launch up to over 1000 practices currently

 

  • The integration gained exposure and curiosity for the business and AI in Clinical IT

Timelines

  • October 2023 - November 2023
    • Design and reviews
  • November 2023 - January 2024
    • Development and testing
  • February 2024 - May 2024
    • Beta testing
  • May 2024
    • Production release

Role

  • Product owner
  • Product designer

Context

In 2023, advancements in AI resulted in high quality scribing tools being developed. Our team was tasked with developing an integration for our on premise PMS application Bp Premier with Lyrebird Scribe, an up and coming web based clinical note taking scribe.

 

The goal was to create a workflow where a doctor could easily launch out to their Lyrebird account during a consult. Lyrebird would then listen and generate a transcription which we would need to write back into the consult in Bp Premier.

 

Reducing the number of clicks and manual copying and pasting between the two systems would save the provider time and money, and ultimately allow them to better focus on their patients.

Analysis and design

We had been tasked to get a first phase out as soon as possible, and to achieve that our thoughts were to reuse existing flows and functionality as much as we could and avoid reinventing the wheel.

 

As the functionality had been implemented in our different products in the past we knew was feasible from technical standpoint and development could reference it to make their work quicker.

 

API Keys for SSO

As more complex authentication methods would take time from both Lyrebird and as, we referenced a recent integration we built with Physitrack.

 

API keys could be generated for users in Physitrack which were then recorded in the user settings of the integrating platform. This key was used as part of the SSO authentication process when launching Physitrack from our applications.

 

It was a more manual process for the user to generate and store keys, but it could be quickly implemented to assist SSO authentication..

 

Browser window

Bp Premier had an in-built chromium browser so it was viable option to launch Lyrebird within this.

 

Having the browser attached to Bp Premier allowed us to have greater control over data being passed back and forth and the number of Lyrebird sessions open to prevent the user from cluttering and losing track of clinical data that had not been saved. This also avoided any issues with the browser the user might have installed on their machine.

 

These designs and workflows were present to multiple product teams, along with internal and external clinical advisors to gather feedback and refine items.

Initial mockups for storing the Lyrebird API Key, the Lyrebird launch button and the internal browser running Lyrebird during a consult

What we released

Lyrebird API key storage

For the SSO process, users would generate a unique API Key and save it to their account in Bp Premier. This key is encrypted and securely stored in the database.

 

This encrypting key is used during the Lyrebird launching process to quickly log into their account, so they can jump into transcribing sooner.

Launching Lyrebird in a consult

Lyrebird can be launched through the main taskbar in the consult window. A quick launch button makes it easier for the provider to access it during a patient consult.

Single Sign On and session prepopulation

SSO occurs on launching Lyrebird from a consult and an API is stored for the provider. Lyrebird runs in the internal browser, and the session is populated with the patient’s details and is ready to record patient consent and begin transcribing.

Writing back of Lyrebird notes

Once the transpiration is ready, the provider can review the notes generated and add observations before sending the data back to the consult in Bp Premier through a click of a button.

During the rollout process I performed multiple internal training session for teams such as sales and support to educate them on the upcoming Lyrebird feature. I also assisted with demonstrating the integration to external stakeholders as part of different review processes.

 

As the first phase of this project wrapped up I moved to a UX role in a different product team. With this I mentored a product owner and business analyst on the feature and feedback we had gathered so they could continue the next phase of the integration. This integration has continued to improve it’s functionality and stability upon the first phase that was implemented.

Conclusion

What went well:

  • Teams were excited to be creating an integration with new technology that could really change how our providers work day to day, and the experience that patients receive

 

  • Feedback from many testers was invaluable as we had a working version of the first phase

 

  • Aiming to reuse workflows and functionality drawn from within our own applications and inspired by others allowed us to get the first phase designed quickly and with confidence that it was achievable

What I would improve:

  • Being prepared with better methods of collating and managing beta feedback - it was a bit chaotic receiving feedback from users through emails, teams, via colleagues they were interacting with etc. It was difficult to keep track of everything being collated, which team should be looking at it and updates on it

 

  • A single form or portal could have been a one stop shop where the data could then land in one location and be sorted.

Key takeaways:

  • Drawing on existing workflows from internal and external timeframes

 

  • User feedback is better than anything you could try to predict or assume