User Persona – Integration Engineer
Bio
‘As an Integration Engineer I work in both technical and support roles. I’m often working at a desk with multiple screens, either in the office or at home, working on multiple projects at once. The main goal within my job is to improve the workflow of data that feeds the Shared Care Record (ShCR). Some weeks I’m working on the ShCR, other weeks I don’t access it at all. In my role I can face many different problems when dealing with different data providers, as I do not always have one point of contact. I aim to streamline the data provision process, and often find satisfaction in problem solving any issues I have.’
Quotes
“You’ve got to log in, and you’ve got to get a text message. There’s no guarantee the text message will ever appear… There’s four pages you’ve gone through now, and you still haven’t got to where you want to get.”
“The console is a bit random as to how you get to places, and also my access seems to vary… I’ve got access to loads of organisations that I’ve got no interest in.”
“I would like to be part of a developer community if that were possible.”
“There’s nice, bright colours which I like… It’s distinctive. It does the job, it’s good.”
Goal and motivations
- My primary goal is to ensure the process of feeding Provider data into our FHIR store, and then into the Shared Care Record, is smooth and efficient.
- I emphasize rigorous data validation, using various test methods to confirm that the data meets required standards, is fit for purpose, and is displayed accurately and safely within the Portal.
- Ultimately, my motivation is driven by the practical impact of my work, aiming to enhance the user experience of the Shared Care Record.
Challenges
I face several challenges, which effect and complicate project requirements and workflows, including:
- Usability issues in portals, such as slow logins and complex navigation, further hinder my work
- Scalability concerns arise from managing large volumes of data
- Inconsistent data management across different Providers, systems, and locations
- Slow login process to the Portal that delays work, causing frustration in daily routines
- A lack of clear specifications and documentation re how the transformation of the data should work
- Error management by the Console. When something within the data feed is incorrect the feedback given is confusing and unhelpful
Opportunities
I believe that improving documentation, error management, usability, and communication among teams is essential for more effective workflows and successful integration solutions. More specific opportunities include:
- Improving the login speed and authentication process for test data
- Improving the documentation / language for error messages
- Enabling customisation of the Portal / Console, to suit individual user / Job Role needs
- Clearer / less technical signposting of documentation for the data mapping process from the start