21st & 22nd September for the next hackathon on Identity

Helen Can you post the Hack twitter handle-thanks

Twitter Handle #FHIRHack2020

Does this rely on the EPMA system defining AMP?

Bye all-Thanks for contributi

I'm not going to be able to present or create slides as I need to run but I have got a video of the result.https://www.awesomescreenshot.com/video/407847?key=3a63964879895ccd164f4a3bfa9a163aUsing NHS login then pulling down meds from the orion consolidated record and presenting to patient as a list that can be edited (mark medicines as inactive / add comment).

Thanks Matt for being part of the event and leaving your video

Thanks Matt, great to see our new API being used!

How long do messages stay on a queues?

^Kafka

@kevin

It is configurable, - by default 7 days

Or infinite - it’s a log rather than a queue

we are thinking along the lines of Kafka topics being the longitudinal record

Thanks. The Manchester LHCRE FHIR Server has similar topology. We don't use an external queuing engine at the mo but planning too.

One of the benefits of kafka is the connector ecosystem so you can push data into and out of kafka into the tools that best suit the proble you are trying to solve

What happens after the end of that time period in Kafka? Does the data get persisted anywhere?

You have different options - so you can persist it for long lengths of time - moving it into cheaper tiered storage and/or you can move it into different data stores or both

Its for queuing/streaming though, not for persistence.

The multiple consumers may be very useful.

Apologies everyone but I am going to have to leave the demo. I will video the presentation and share. Some really great stuff happening here!

Hi RobI've just seen your slides and added you to the list. There will be time if you want to share your hack. We're just running a little tight on time but sure we'll be okay.

One of the things you need to consider is if you need to preserve the historic state of the data in order to rebuild information - this can be useful if you want to recreate datastores after schema changes as you can rebuild the database rather then mutate (update it). Generally Kev is right you don't look to hold forever for most use cases

At the top of the call View Options - Select Mark Hunt

Mike, what we have at the mo is on this url.basically it's Apache Camel+HAPI going via queue to HAPI JPA FHIR Server.Having kafka in between the two would probably work

https://project-wildfyre.github.io/careconnect-messaging-r4/

Camel is doing the transforms

Thanks Kevin that's a perfect paring!

One of the things we think will be helpful is to use CADE to help model future APIs quickly or to model non FHIR flows as this will help us understand how to handle a mixed economy of interoperability standards

Is CADE open source?

Thank you everyone! This has been so educational (and a little bit fun). But I have a kid who needs picking up!

Hi Steve - the CADE engine is not open source, but the configuration files, pathways and generated outputs are…

:)

the CADE engine is (and will remain) available for free use as long as the config files are kept open

Brilliant!

I think Better use Kafka from memory. Would be good to confirm

I wish I had Better.care available as a test environment! Looks awesome

Sorry I mean OpenEP

It is really good set of products to work with and a great team too!

yep

:D no problem

Thank you though, I appreciate it!

I wanted to give David Beaumont a vote too :)

As did I

David Beaumont you would have got my vote also. Great to see

Ditto, David Beaumont you would have got my vote too. :)

Is this where we all network and drink free wine at the end :) ?

Thanks very much for the vote of confidence of getting social care involved with meds in the NHS. If anyone knows how we can overcome the network/IG issues I’d really appreciate it :)

..so would the other social care systems providers (and the social care providers themselves)

Thanks everyone for sharing and it was very inspiring ! Great event :)

thankyou everyone and particularly to the all of those who have shared their expertise. Thanks to the NHSD team who have supported as well. A real demonstration of collaboration

Thank you all. Thank you Helen.

My first hackathon and fabulous to see what multiple perspectives and expertise across the sector

Thanks everyone!!!! Can't wait for the next one :)

Thank you! See you at the next one!

Thanks everyone