A team to develop, in house, open-source tools for the NHS

open forum
41

Hi @james.roberts I didn’t have anything in my diary for today, and I’m unavailable I’m afraid.
I’ll have a look through the documents you’ve shared and comment back here.

42

How doo! @james.roberts and I had a good call. I’m on board too!

We talked about

…and keeping this regular to get some momentum! See you in 2 weeks for the next one!

43

Can we set up some kind of recurring invite so that people know about it?

Sadly calendar invites is one thing that Discourse is just really bad at doing, I have raised it as an issue with the Discourse people.

44

if it’s not too noisy, how about we manually make a new thread / top post that we can attach event info to for each call? that way we can insert some suggested direction for the next call and link back to the previous call and notes can be added about that call to the thread.

manually doing ensures someone takes ownership of coordinating and promoting the next call, but its easy for someone else to step in later.

45

Great to meet you @olizilla and thank you for answering the call. Really good to see the shared enthusiasm and recognition of this being an important direction of travel for how we move to the next iterations of these systems.

Agreed we need to set up a regular meeting. Fortnightly on thursday evenings 18:30-19:30 seems right at present. Happy for people to drop in when able. We can use @pacharanero Jitsi suggestion as this allows a persistent meeting room that people can save and use at other times on a regular link. I will set up a new post for the next meeting to make it easier for people to find - that way people can bring any ideas or discussion points prior to the meeting and might be helpful if they are unable to attend.

The task I have set myself for the next meeting is to establish the fundamental requirements of an EHR for the various users - clinicians, patients, healthcare organisations. I will produce the draft paper and welcome collaboration, improvements and suggestions. Once this has been defined we can look at what ‘building blocks’ would allow a system to meet these requirements.

Keen for any thoughts/suggestions.

See you all soon!

James

46

Great work putting my cube in a visual - love it!

47

Sorry I missed the last call. So will the teams link at the top now work every 2 weeks?

I might not be able to get on the next call due to an important family birthday but will be there for the next ones.

48

Thanks all. Yes I will start a new thread if that’s ok so it keeps ideas together and avoids confusion.

49

Thanks

I wonder if we need to look at how we organise ourselves. Although we often start from the same place (patient pathway), we are likely to have diverged already. For example.

  • I am mostly focused on automating the patient pathway → I am process/enterprise engineering focused e.g. lab orders, data or document sharing, discharge reports, care coordination, etc. It is aligned to NICE, GIRFT, etc pathways.
  • Others will be clinical informatics focused. This tends to lead to data engineering around EHR’s. Processing engineering tends to treat data models from here as logical and implements them on the patient pathway often using different standards (e.g. define in openEHR/FHIR profiles and implement in HL7 v2, DICOM, FHIR, XDS, etc)
  • Others will be focused on applications on that pathway application design and service design.

I"m not saying we should group this way, just we have different perspectives. We need to be conscious of

people + process + technology