Case study: BMJ Best Practice, Knowledge Base
BMJ is a healthcare knowledge provider that advances healthcare worldwide by sharing knowledge and expertise to improve experiences, outcomes and value.
BMJ’s leading clinical decision support tool, BMJ Best Practice, is used by clinicians at the point of care in many countries. Offering advice on symptom evaluation, test ordering and treatment approaches for over 800 conditions in 30 specialties, BMJ Best Practice provides a rich source of expertise that healthcare professionals rely on every day.
BMJ wanted to innovate their product and user experience in line with clinicians’ needs and expectations for concise evidence-based information within the clinical setting. But the content was being created, stored and presented as long form articles typically extending to thousands of words. This made it difficult to improve the user interface and limited BMJ’s ability to offer content slices to third parties for integration into granular software systems, particularly EHR (Electronic Health Record) systems. The underlying editorial production system was reaching end of life and as such was slow use to and hard to maintain.
BMJ therefore took a strategic decision to build a completely new editorial production system, and crucially, to change the underlying data structure of the content to make it more granular. This would enable the company to satisfy current market demands, create new market opportunities and provide a springboard for further product innovation.
BMJ asked 67 Bricks to develop “Knowledge Base”, a bespoke editorial production system designed to be flexible enough meet BMJ’s needs, both now and in the future. 67 Bricks conducted a preparatory workshop with BMJ stakeholders to explore the ambition for the system and how best to work together to achieve it. The project was run on agile principles in two phases: elaboration and build. It was a big project with a limited timescale and so careful planning was essential. Key factors included:
- Strong prioritisation. This was critically important. BMJ adopted the ‘pragmatic marketing’ product development framework: this ensured that all the features built were based on external requirements.
- Prototyping. Shortlisted technologies including the data store and the XML editor were prototyped with real data so that stakeholders could see what it would mean for them in their daily activities.
- Co-development. BMJ’s and 67 Bricks’ developers worked together as one co-development team, but in different locations. This was facilitated through heavy use of online communication channels, in this case Slack and Trello, combined with daily joint stand-ups. There was reciprocal code review. The team were able to talk openly about how to implement features, and there was real trust. A shared understanding of the business drivers meant that everyone on the team was working towards a common goal. Co-development ensured maximum knowledge transfer to BMJ’s developers who now continue to maintain and extend the system to meet future needs.
- Content model. The new model, composed of individually referenceable fragment types (e.g. assessment, diagnosis), was refined iteratively throughout the project. More standardised than the old model, it provides the scope to slice up content, reuse content, work with partners, feed the product website and innovate.
- Meeting current needs. As well as providing for the future, it was essential to replicate current data outputs, to ensure no disruption in service to existing products and partners.
- Driving the BMJ Best Practice website. The development of Knowledge Base was undertaken in tandem with a separate project to redevelop the customer-facing product website. Therefore a Knowledge Base API was built to allow the new website to retrieve and use the content to power innovative front-end features.
- Content enrichment. Entity recognition was used to identify drug names and diagnoses within the editorial system. These enhanced terms are made available through the API and are retrieved by the new BMJ Best Practice website which can then use this information to deliver an enhanced search capability. The enriched terms also provide a basis for further innovation.
Using the new interface (Figure 1) editors are able to make changes to the relevant content fragments only and no longer need to read a long document in order to pinpoint the place(s) that needs updating.
Figure 1: Knowledge Base editorial search screen
Much of the content is available in several languages and so when a fragment is updated, only that fragment needs to be sent for re-translation, saving on time and expenditure.
Where needed, e.g. when an update is reviewed by an external expert, the system is able to reconstruct the long form version of the content so that the expert can see the change in context. A full audit trail is also available showing all changes and who made each one.
BMJ now have much improved ability to take advantage of new business opportunities, are currently prototyping or piloting new feeds and products, and are well-placed to pursue future partnerships. Some partnerships have come up for tender with new integration requirements that BMJ would not have been able to fulfil before.
“This has been a successful, incredibly complex project delivered in a short period of time. It has given us the foundations to support our product development strategy, innovation and partnerships that were impossible before.”
Louise Crowe, Director of BMJ Knowledge.
“67 Bricks helped a lot with scoping. We welcomed their technical expertise, advice and their ability to deal with complex content. It was important to have an external voice. Their level of project planning, engagement and support was fundamental to the overall project success.”
Yen Chau, Business Solutions Architect.
“For us, being able to work together with 67 Bricks in creating the new editorial tool, was essential. As an engineering team, being able to support and enhance our key products ourselves is a very important part of the value we bring to BMJ. The 67 Bricks team worked with BMJ as one integrated team with shared deliverables, responsibilities, design and decision making. We could not have delivered our project without them.”
Rex Cooper, Chief Technology Officer.
The BMJ Best Practice website is available at bestpractice.bmj.com