How did the @Data4Life_D4L frontend engineering team use Google’s #CoreWebVitals to improve user experience metrics? @__benlau explains what Cumulative Layout Shift (CLS) is, it’s importance, & how we improved our score here at Data4Life https://t.co/I1JVwWcm3F #SEO#UX#webperf
@pixenjoy Hello @pixenjoy, the static site generator is compatible with @getkirby v3.6. We are not aware of any breaking changes and have tested it using the starterkit. We plan to migrate our own setup to Kirby 3.6 in the next days.
My friends at @Data4Life_D4L are looking for a new Frontend Developer (remote in Germany).
It's such a lovely team! I worked with them last year and can highly recommend it. 👇
If you have questions, feel free to reach out to @Haeringer. 😊
https://t.co/nCSiEryuuX
And now 🎉we have a live demo where you can just paste (or type, we don't judge) your FHIR resources and see the validation result. 100% client-side. 🔥✅ https://t.co/hjnGVt3Gxi
Hey folks 👋 My team @d4l_engineering has just opened a position for a frontend engineer!
Our focus — accessible & performant solutions for medical & research orgs by leveraging the web platform features.
If that resonates with you, send me a DM or check https://t.co/PBlZTNuCp4
When delivering digital public #healthcare solutions, accessibility is a core responsibility. Our frontend engineer @radibit discusses #a11y success criteria for our web sites and progressive web apps https://t.co/J1LUNfkJDK
We wish all #MozillaLifeboat passengers a smooth voyage. If you’re looking for a safe ⚓️ harbor in digital health, we’re a Berlin-based nonprofit org looking for QA eng + full stack devs (on-site/ remote). Reach out 💌 to [email protected] or check https://t.co/R0HtH0ZhHt
And find out why we’re using @OHDSI’s #OMOP CDM and our own analytics platform to bring researchers and #healthdata together. https://t.co/I1QKrYOnDm 3/3
Thread: our analytics team has been busy and wrote about it! Here’s a short guide on how to add SAP’s powerful, in-memory database @SAPHANAWatch to the @OHDSI WebAPI. https://t.co/iHeg0Emr1r 1/3
But also, you want to be sure the data follows a common pattern! Well, here’s how Data4Life is working with the @OHDSI’s OMOP common data model for observational #healthdata research and data sharing. https://t.co/W53t55EGPi 2/3 #openscience#digitalhealth
Our engineer @Burtchen writes about how we optimised the #javascript performance for our symptom tracker with its various asynchronous calls. Read it here: https://t.co/0MdcPmNXcX
New blogpost: We published more information about the process behind our #FHIR resources, especially how we dealt with code systems such as #loinc and #snomed for them https://t.co/wXlCaTyu7Q
We are on simplifier now - find the definitions we use for our #coronavirus questionnaires at https://t.co/8ZEp1XKJOk - yes, the same ones our open-source covapp https://t.co/GvEpeC31BU generates. Many thanks to @ProfThun, @kainamti, @jul_sass, @ChariteBerlin and @molit_institut!
We’ve been busy in the last weeks, fixed some bugs, tweaked the copy - and now we even have Indonesian and Spanish copy out of the box. Thanks for all your PRs and suggestions! https://t.co/8WUEyhczZr
👋🏼😷Hello world! We’re excited that our covApp, a joint effort by Charité-Universitätsmedizin @chariteberlin and Data4Life to speed up decision-making, is now available as a public repo. Check it out (literally!) at https://t.co/koM5KrFCM7