CREATIVITY
EXPERTISE
Health Business Services
Tobacco Reporting in the Department of Health, Disability & Ageing
4
User journeys prototyped
8
Months, from conception to launch
2
Components designed
8
Components documented with governance
Digitising how business partners interact with the department.
The Department of Health, Disability and Ageing (DoHDA) does business with internal business areas, industry health partners, other Australian Government departments, regulatory agencies, pharmaceutical companies, medical device manufacturers, tobacco companies amongst many other partners. As you might imagine, there are a lot of points of contact and so many services that these partners would need access to.
It’s through the Health Business Services Portal (HBSP) - a transactional site which all these organisations interact with us. It serves as a secure, single-entry point for industry partners to access multiple services across the department.
The UX/UI team in our section designs all the services within the HBSP, including:
Hearing Services Online
Office of Drug Control
Therapeutic Goods Administration
Tobacco Reporting (TR), which is designed by me
TR provides a collaborative reporting tool for the industry and the department on tobacco-related products.
scope & definition
I had ownership over the design for TR, where I had the joy of:
creating all the wireframes
liaising with the client, business and a team of developers and business analysts.
designing and completing the governance for a number of components in the HBS design system.
The platform provides the following:
Prevention & Early intervention: TR helps to keep the tobacco products supplied to Australians regulated and safe.
Built for sustainability: Delivering a platform for tobacco compliance that is flexible allows for future legislative changes and requirements.
Engage our people: TR platform engages and empowers the delivery team and stakeholders to deliver a robust and fit-for-purpose system in alignment with relevant legislation.
Data interoperability, sharing & exchange: Facilitating exchange of data between external entities and the department.
Uploading reports & viewing submissions
Information Architecture & Wireframes
Based on this, I began creating a set of wireframes using the components made by fellow designers thus far, as well as the patterns and layouts they established in other services.
As part of the Public Health (Tobacco and Other Products) legislation, some tobacco manufacturers and importers are required to report yearly on product ingredients, volumes and marketing spend.
Therefore, the TR service needs a function where users can submit reports. My BA laid out the general requirements, and I worked with her to give shape to the following user journey:
Signing into the portal
Viewing all linked and available services
TR Home
Record of all previous submissions and drafts, and option to create new
Report submitted
Registering an organisation
Based on this, I began creating a set of wireframes using the components made by fellow designers thus far, as well as the patterns and layouts they established in other services.
Reports are uploaded on behalf of an organisation. Therefore, there needs to be a process to register an organisation for the TR service, from which one can meet their reporting obligations. I worked with my BA to create a user flow meeting all the needs and requirements of the business.
TR Home
User clicks 'create organisation account', to begin a multi-step form
User begins form
Platform connects to RAM to verify user's relationship to the organisation.
Details retrieved
User works their way through multi-step form.
User reaches end of form.
Request is sent to the administrator.
Manage organisation members & details
The TGA service already defined some patterns for organisation, contact and address management.
Naturally, I followed the same patterns for consistency and adjusted based on TR business’ specific needs and requirements.
User selects 'My organisation'
User can manage contacts and addresses (editing only for administrators) and view their details
Addresses
Contacts
Personal details
Components I designed - Blob storage
When submitting a report, users need to upload files. Whilst all other services in HBSP use a Sharepoint storage component, TR alone uses Microsoft Azure storage instead. This is because the service needs to support up to 3 files greater than 150mb, due to the hefty templates used for report submissions.
This brought about a new technical challenge however, as the Azure storage file plugin is made in a way where two discrete components, stacked directly on top of each other yet don’t communicate with each other in the Out-of-the-box design. This is represented below as ‘Uploaded files’ and ‘upload files’ in the image below.
Design system and UI
Based on this, I began creating a set of wireframes using the components made by fellow designers thus far, as well as the patterns and layouts they established in other services.
I was fortunate to join the team when the foundations for the HBS design system had more or less been established. Colours, fonts, buttons and most of the other atoms and molecules had already taken shape, and so my responsibilities fell more so in giving definition to the organisms, templates, pages and creating prototypes