Aaron Lim

Patient record export

Outcomes

  • Created a patient export tool that will generate a PDF export of selected demographic and clinical data of the patient

 

  • Developed a document template for the export, mapping of all the different data point within each category

 

  • Functionality to email the password protected export to the user and create an audit trail record for added security

Timelines

  • April 2025 - June 2024
    • Designs and reviews
  • September 2024
    • Development commenced

Roles

  • Product Designer

Context

I led the design of the patient export tool in our cloud product Omni. Working alongside a Product Owner, this feature would allow staff at a practice to export the full record of a patient from their practice database. This might occur if the patient wanted a copy for themselves, if they were moving to a different practice or if the data had been subpoenaed by court.

 

As part of the requirements, the tool developed needed to reflect existing functionality in the patient export and subpoena tools in Bp Premier as users would need a consistent feel to using it. This was an opportunity to combine two tools into one and refine their flows, whilst adding the new Omni look and feel to it.

 

With many aspects of both clinical and administrative data contained in the export, this project was just as much about creating an intuitive interface as it was creating a document that would be digestible for those viewing it.

Analysis and design

Exploration was first conducted on the two existing tools in Bp Premier. Despite having different layouts, there was consistent functionality between the two such as the data type selection and filtering on dates. Some slight differences were noted where the user can drill down to select specific records in the subpoena tool along with differences in the export types available

 

Working with the product owner we confirmed what the first phase of work would consist of. For the first phase, the plan was to build out a modal with core functionality to select whole categories and filter on dates and confidential records.

 

The first phase would require a lot of work in the backend to link up all the relevant data for the export and ensure the performance of the export was still acceptable. Features such as being able to select specific records within a category and other export formats could added in future once the core functionality was in.

 

An important component of this work was the actual document itself. An existing clinical export template was used as a point of reference for the document. It provided a general consistent format for where the headers, subheadings and dates would show but mapping was still required for each categroy to ensure the required data was being extracted correctly

The export patient and subpoena tool in Bp Premier

Example of mapping done between export template and the fields in Omni

Impleme

There were many rounds of iterating and reviews with other product designers before landing on a design we were happy with

 

  • There was key functionality it had to support such as the the filtering of data by date, filtering confidential records and also the clinical and demographic data categories
  • The thought process and workflows of the user impacted the order of information presented in the modal - would they want to filter the date at the start or the end? Can we group the data categories and how do we easily allow them select and unselect each of them?
  • Even ‘smaller’ items such as the positioning of the checkboxes next to the grid items or on the end of each row was assessed for ease of use and understanding
  • During iteration, a breakthrough was implementing a two column approach for the demographic and clinical data sections. This reduced the footprint module and allowed the filtering options to live at the top of the modal, which is naturally where it that functionality lives in Omni

Iteration process exploring layouts and options. Initial options to the final design on the right

What we released

Patient export modal

The patient export modal supports selecting demographic and clinical data categories along with filtering by date and confidential records. The modal can be used throughout Omni and launched from required locations.

Patient export document template

The export document template was developed to support exporting based on the user selection in the modal. Consistent data mapping was done throughout the template so it was digestible for the user and can be reused for extra data categories in future.

 

Clinical documents within the patient record are included as attachments to the PDF generated.

Email delivery of patient export document

On generating the export the user will receive an email wth the password protected PDF export attached. This offers privacy and security with the document as it is provided to the appropriate parties.

Patient audit log

A new patient audit log was created to record details of the export generated. This new log can beexpanded and used for future auditing purposes.

The patient export tool is currently still in development as due to changes in resourcing and priority causing delays.

 

It is nearing completion and will be out to beta testing soon.

Conclusion

What went well:

  • Working alongside developers in evolving the template was a great experience as it was no small task trying to map so much patient data. Mapping the data with their familiarity of the backend helped validate the decisions we were making were possible and they helped highlight areas that were issues or could be improved.

 

  • The module created was a great fusion of existing component features in Omni with nods to the tools that exist in Bp Premier. It has the ability to be expanded in future to support things such as additional data categories and the option to select export types and methods.

What I would improve:

  • The export document needs continual review to tidy up the format - things such as fonts and spacing need to be checked as different sections can contain data that is exported a bit differently.

Key takeaways:

  • It is possible to create a feature that is familiar to users with a nod to existing utilities whilst bringing it into a modern era and design system.

 

  • Continual development input where possible brings confidence in whether designs are achievable and can generate even better solutions through discussions.
Aaron Lim

Patient record export

Outcomes

  • Created a patient export tool that will generate a PDF export of selected demographic and clinical data of the patient

 

  • Developed a document template for the export, mapping of all the different data point within each category

 

  • Functionality to email the password protected export to the user and create an audit trail record for added security

Timelines

  • April 2025 - June 2024
    • Designs and reviews
  • September 2024
    • Development commenced

Roles

  • Product Designer

Context

I led the design of the patient export tool in our cloud product Omni. Working alongside a Product Owner, this feature would allow staff at a practice to export the full record of a patient from their practice database. This might occur if the patient wanted a copy for themselves, if they were moving to a different practice or if the data had been subpoenaed by court.

 

As part of the requirements, the tool developed needed to reflect existing functionality in the patient export and subpoena tools in Bp Premier as users would need a consistent feel to using it. This was an opportunity to combine two tools into one and refine their flows, whilst adding the new Omni look and feel to it.

 

With many aspects of both clinical and administrative data contained in the export, this project was just as much about creating an intuitive interface as it was creating a document that would be digestible for those viewing it.

Analysis and design

Exploration was first conducted on the two existing tools in Bp Premier. Despite having different layouts, there was consistent functionality between the two such as the data type selection and filtering on dates. Some slight differences were noted where the user can drill down to select specific records in the subpoena tool along with differences in the export types available

 

Working with the product owner we confirmed what the first phase of work would consist of. For the first phase, the plan was to build out a modal with core functionality to select whole categories and filter on dates and confidential records.

 

The first phase would require a lot of work in the backend to link up all the relevant data for the export and ensure the performance of the export was still acceptable. Features such as being able to select specific records within a category and other export formats could added in future once the core functionality was in.

 

An important component of this work was the actual document itself. An existing clinical export template was used as a point of reference for the document. It provided a general consistent format for where the headers, subheadings and dates would show but mapping was still required for each categroy to ensure the required data was being extracted correctly

The export patient and subpoena tool in Bp Premier

Example of mapping done between export template and the fields in Omni

Impleme

There were many rounds of iterating and reviews with other product designers before landing on a design we were happy with

 

  • There was key functionality it had to support such as the the filtering of data by date, filtering confidential records and also the clinical and demographic data categories
  • The thought process and workflows of the user impacted the order of information presented in the modal - would they want to filter the date at the start or the end? Can we group the data categories and how do we easily allow them select and unselect each of them?
  • Even ‘smaller’ items such as the positioning of the checkboxes next to the grid items or on the end of each row was assessed for ease of use and understanding
  • During iteration, a breakthrough was implementing a two column approach for the demographic and clinical data sections. This reduced the footprint module and allowed the filtering options to live at the top of the modal, which is naturally where it that functionality lives in Omni

Iteration process exploring layouts and options. Initial options to the final design on the right

What we released

Patient export modal

The patient export modal supports selecting demographic and clinical data categories along with filtering by date and confidential records. The modal can be used throughout Omni and launched from required locations.

Patient export document template

The export document template was developed to support exporting based on the user selection in the modal. Consistent data mapping was done throughout the template so it was digestible for the user and can be reused for extra data categories in future.

 

Clinical documents within the patient record are included as attachments to the PDF generated.

Email delivery of patient export document

On generating the export the user will receive an email wth the password protected PDF export attached. This offers privacy and security with the document as it is provided to the appropriate parties.

Patient audit log

A new patient audit log was created to record details of the export generated. This new log can beexpanded and used for future auditing purposes.

The patient export tool is currently still in development as due to changes in resourcing and priority causing delays.

 

It is nearing completion and will be out to beta testing soon.

Conclusion

What went well:

  • Working alongside developers in evolving the template was a great experience as it was no small task trying to map so much patient data. Mapping the data with their familiarity of the backend helped validate the decisions we were making were possible and they helped highlight areas that were issues or could be improved.

 

  • The module created was a great fusion of existing component features in Omni with nods to the tools that exist in Bp Premier. It has the ability to be expanded in future to support things such as additional data categories and the option to select export types and methods.

What I would improve:

  • The export document needs continual review to tidy up the format - things such as fonts and spacing need to be checked as different sections can contain data that is exported a bit differently.

Key takeaways:

  • It is possible to create a feature that is familiar to users with a nod to existing utilities whilst bringing it into a modern era and design system.

 

  • Continual development input where possible brings confidence in whether designs are achievable and can generate even better solutions through discussions.
Aaron Lim

Patient record export

Outcomes

  • Created a patient export tool that will generate a PDF export of selected demographic and clinical data of the patient

 

  • Developed a document template for the export, mapping of all the different data point within each category

 

  • Functionality to email the password protected export to the user and create an audit trail record for added security

Timelines

  • April 2025 - June 2024
    • Designs and reviews
  • September 2024
    • Development commenced

Roles

  • Product designer

Context

I led the design of the patient export tool in our cloud product Omni. Working alongside a Product Owner, this feature would allow staff at a practice to export the full record of a patient from their practice database. This might occur if the patient wanted a copy for themselves, if they were moving to a different practice or if the data had been subpoenaed by court.

 

As part of the requirements, the tool developed needed to reflect existing functionality in the patient export and subpoena tools in Bp Premier as users would need a consistent feel to using it. This was an opportunity to combine two tools into one and refine their flows, whilst adding the new Omni look and feel to it.

 

With many aspects of both clinical and administrative data contained in the export, this project was just as much about creating an intuitive interface as it was creating a document that would be digestible for those viewing it.

The export patient and subpoena tool in Bp Premier

Example of mapping done between export template and the fields in Omni

Analysis and design

Exploration was first conducted on the two existing tools in Bp Premier. Despite having different layouts, there was consistent functionality between the two such as the data type selection and filtering on dates. Some slight differences were noted where the user can drill down to select specific records in the subpoena tool along with differences in the export types available

 

Working with the product owner we confirmed what the first phase of work would consist of. For the first phase, the plan was to build out a modal with core functionality to select whole categories and filter on dates and confidential records.

 

The first phase would require a lot of work in the backend to link up all the relevant data for the export and ensure the performance of the export was still acceptable. Features such as being able to select specific records within a category and other export formats could added in future once the core functionality was in.

 

An important component of this work was the actual document itself. An existing clinical export template was used as a point of reference for the document. It provided a general consistent format for where the headers, subheadings and dates would show but mapping was still required for each category to ensure the required data was being extracted correctly.

Iteration

There were many rounds of iterating and reviews with other product designers before landing on a design we were happy with

 

  • There was key functionality it had to support such as the the filtering of data by date, filtering confidential records and also the clinical and demographic data categories
  • The thought process and workflows of the user impacted the order of information presented in the modal - would they want to filter the date at the start or the end? Can we group the data categories and how do we easily allow them select and unselect each of them?
  • Even ‘smaller’ items such as the positioning of the checkboxes next to the grid items or on the end of each row was assessed for ease of use and understanding
  • During iteration, a breakthrough was implementing a two column approach for the demographic and clinical data sections. This reduced the footprint module and allowed the filtering options to live at the top of the modal, which is naturally where it that functionality lives in Omni

Iteration process exploring layouts and options. Initial options to the final design on the right

What we released

Patient export modal

The patient export modal supports selecting demographic and clinical data categories along with filtering by date and confidential records. The modal can be used throughout Omni and launched from required locations.

Patient export document template

The export document template was developed to support exporting based on the user selection in the modal. Consistent data mapping was done throughout the template so it was digestible for the user and can be reused for extra data categories in future.

 

Clinical documents within the patient record are included as attachments to the PDF generated.

Email delivery of patient export document

On generating the export the user will receive an email wth the password protected PDF export attached. This offers privacy and security with the document as it is provided to the appropriate parties.

Patient audit log

A new patient audit log was created to record details of the export generated. This new log can be expanded and used for future auditing purposes related to patients

The patient export tool is currently still in development as due to changes in resourcing and priority causing delays.

 

It is nearing completion and will be out to beta testing soon.

Conclusion

What went well:

  • Working alongside developers in evolving the template was a great experience as it was no small task trying to map so much patient data. Mapping the data with their familiarity of the backend helped validate the decisions we were making were possible and they helped highlight areas that were issues or could be improved.

 

  • The module created was a great fusion of existing component features in Omni with nods to the tools that exist in Bp Premier. It has the ability to be expanded in future to support things such as additional data categories and the option to select export types and methods.

What I would improve:

  • The export document needs continual review to tidy up the format - things such as fonts and spacing need to be checked as different sections can contain data that is exported a bit differently.

Key takeaways:

  • It is possible to create a feature that is familiar to users with a nod to existing utilities whilst bringing it into a modern era and design system.

 

  • Continual development input where possible brings confidence in whether designs are achievable and can generate even better solutions through discussions.