# Eyes on openEHR **Category:** [Clinical](https://discourse.openehr.org/c/clinical/5) **Created:** 2024-12-06 07:01 UTC **Views:** 941 **Replies:** 37 **URL:** https://discourse.openehr.org/t/eyes-on-openehr/6003 --- ## Post #1 by @varntzen Starting this discussion here, as there are an ongoing thread about collaboration in the Highmed openEHR symposium https://discourse.openehr.org/t/highmed-openehr-symposium-31-1-25/5311?u=varntzen . Please use this thread instead. @Lars_Fuhrmann @SevKohler @Paulmiller @ian.mcnicoll @Kanthan_Theivendran @Koray_Atalag @Eugene_Kolah --- ## Post #2 by @Lars_Fuhrmann Thank you for the announcement! Ophthalmologist in training and complete openEHR-Newbie here, I'll be at the symposium to learn more about it. side note: I'm trying to push for better interoperability in ophthalmology - at the moment mostly based on FHIR, but I'm wondering whether we should think about about coherence between information models and terminology between OpenEHR and future ophthalmic FHIR IGs early on, as lots of challenges may overlap. So if there is anyone out here, who is interested (or already working) in the domain of ophthalmology please feel free to get in touch, at the symposium or whenever! --- ## Post #3 by @SevKohler https://discourse.openehr.org/t/openeyes-on-openehr/1187 @ian.mcnicoll maybe know more :) --- ## Post #4 by @Paulmiller In NHS Scotland we are deploying OpenEyes nationally under the technical leadership of my day job's organisation, NHS Education for Scotland Technology Service. We investigated, and Apperta did some modelling, the feasibility of creating openEHR compositions alongside OpenEyes own data but we have not implemented this. At the time our platform maturity was not there. It is better now but there is no priority / use case at the moment for doing this. I think it may come, for example visual acuity and partially sighted status are two OpenEyes data items that could be generally useful in a shared record / patient oriented record. Right now, however, we have other things being prioritised so when we will hit this requirement is uncertain. Hopefully when it does we will be able to handle it as a fairly routine integration piece. Hopefully.. --- ## Post #5 by @ian.mcnicoll @David-Jobling probably has more insight, though his work with openEYES. We have had a few efforts to map openEyes components to openEHR but it is a scarily detailed area. See an earlier effort in the PDF Green = match Yellow = match but needs change Red = new archetype required Grey = out of scope [Examination event.pdf|attachment](upload://s857EluhI5FmAiNYuLDwVOtvj9G.pdf) (3.0 MB) @bna -might have some insight from DIPS work in this area. --- ## Post #6 by @Lars_Fuhrmann Dear Ian and Paul, Thank you both, I have to admit that was not awaye of OpenEyes, what a fascinating project! From the project's website I gather it's mostly implemented in the UK? I would love to learn more as I see a real need for open ophthalmic EHRs with good data models in Germany. It's a shame that implementing it over here would propably be an utterly herculean task, both in terms of language and MDR approval/regulatory aspects.. @ian.mcnicoll "scarily detailed" rings true, but from what I can tell by the UI OpenEyes has not been scared off from modelling in a highly granular fashion, which is great, thank you for sharing! @Paulmiller National deployment sounds like FHIR-based data exchange might not be as necessary for you as it is in Germany, where the EMR market is highly fractioned. Are you aware of any efforts to exchange data stored in openEHR or OpenEyes data models using FHIR? I have this though stuck in my mind that the (relative) immaturity of ophthalmic data modelling in both FHIR IGs and openEHR may turn out be a blessing in disguise, as it may allows for some mutual flexibility and synergies in trying to develop them in tandem.. It may be really difficult to build a team around a common use case for this, but if openEHR architecture for ophthalmic data were aligned with (future) FHIR IGs, then openEHR may be seen as the go-to model to store ophthalmic data in a structure that is easily mappable to FHIR. Or maybe I'm wrong? I would be really interested to hear your thoughts on this! If you are interested, I've done some [experimental profiling FHIR ressources for visual acuity data](https://larfuma.github.io/fhir-eyecare-ig/StructureDefinition-observation-visual-acuity-version-three.html) with emphasis flexible recombination of simple SNOMED/LOINC concepts within the resource to reflect many clinically relevant test variants, including complicated things like [contact lens overrefraction](https://larfuma.github.io/fhir-eyecare-ig/Observation-va-measurement-example-patient-1-with-overrefraction-v3.html) or [binocular tests with monocular correction.](https://larfuma.github.io/fhir-eyecare-ig/Observation-va-measurement-example-patient-2-bino-50cm-with-od-contactlens.html) which are not supported by most EMRs at the moment. I'm writing about it one the [FHIR Zulip Channel for Opththalmology](https://chat.fhir.org/#narrow/channel/238885-Opthalmology), which sadly isn't very active. Sorry for derailing the symposium announcement by the way! Shall we move our discussion to the "OpenEyes on openEHR" thread or something? --- ## Post #7 by @Kanthan_Theivendran Hi Lars, It may be worth getting in contact with Peter Coates from the The Apperta Foundation who I'm sure you will be interested in talking to as they own the largest Ophthalmology EPR/EMR called openEYES in the UK and they are currently re-platforming to openEHR.: https://openeyes.apperta.org/ --- ## Post #8 by @ian.mcnicoll Lars - perhaps we can move this topic to a clinical modelling channel, where it might get more visibility? --- ## Post #9 by @Eugene_Kolah I have been a member of the openeyes community before it ran out of funds and I'm particularly keen on the use of similar capability in other clinical context outside opthamology. But I wonder if their resources are open. The apperta ckm was shutdown, luckily the github mirror is there, but it's a little bit difficult implementing or even tinkering with the spec since the documentation is locked. How do we get access to the confluence pages... otherwise i suspect interested persons will have a difficult time utilising/exploring this great spec. --- ## Post #10 by @Kanthan_Theivendran Some interesting work going on with AWS and openEYES and openEHR. Peter Coates (peter.coates@Apperta.org) could fill you in. I think a collaborative approach with Ophthalmology clinical modelling could be mutually beneficial. --- ## Post #11 by @bna Yes we have work in opthalmologi in Norway. It's an initiative lead by the hospital in TromsĂž (north in Norway) with support from all the other hospitals. We have deployed an application for retinopathy screening/controls. The clinical models are here: https://github.com/bjornna/eyecare_retinopaty The goal is to support all use-cases related to opthalmologi. Have a look at the archetypes here: https://github.com/bjornna/eye_care There is still lots of modeling work to do. And we should do international review of the archetypes since most of them are for common clinical concepts around the world.. --- ## Post #13 by @lars.lindskold Fully agree, but i don't know how to do 🙂 --- ## Post #14 by @lars.lindskold Now i see Ian , that you were pointing at another Lars :-) --- ## Post #15 by @ian.mcnicoll Too many Lars ... :rofl: --- ## Post #16 by @Olha_Nikolaieva Our team in Switzerland has recently developed an archetype for the Contrast sensitivity test as part of a specific project. This archetype has been submitted to the international CKM under reference RP-357. Although I lack formal expertise in ophthalmology, this archetype was developed based on extensive research and literature review. I welcome feedback and insights from professionals in the field to ensure its accuracy and applicability. --- ## Post #17 by @Lars_Fuhrmann Hello BjĂžrn, I'm very glad to hear about your work and its broad scope, thank you for sharing. I will try and understand your archetypes, but as I am new here will take me a bit of time to get into the openEHR environment and get used to the tooling. If you have any recommendations which software tools may work well for me please do let me know. As you mentioned that there is a lot to do and international review makes sense, i feel like getting those who are trying to model ophtalmology in FHIR (like me) to also consider your archetypes in their process may be a good idea. Maybe we coulde even see how we can get some Archetype/Composition <-> FHIR mapping going? I am thinking about Visual acuity and intraocular pressure for example? Terminologically, do you come across a lot of gaps in SNOMED CT/LOINC as well? If you do maybe it make sense to compare and discuss before we request. I will get back to you once I have better understanding of your archetypes, thank you for your work! --- ## Post #18 by @johngrant4est [Eyes on FHIR](https://confluence.hl7.org/pages/viewpage.action?pageId=82914199) looks to have stalled. Coincidentally, I recently discovered the [FHIR Vision Prescription](https://build.fhir.org/visionprescription.html) resource (maturity level 3) which was used in a #nhshackday project in London in October '24. I've been dipping into the [Patient Care](https://confluence.hl7.org/display/PC/Patient+Care) FHIR WG recently and would be happy to ask the question - is there scope for a collaborative group to bring together the two ophthalmology modelling communities. --- ## Post #19 by @Lars_Fuhrmann Dear Kanthan, sorry for the delay in getting back to you, I'm interested, and I'll reach out to you and Peter Coates shortly. --- ## Post #20 by @Lars_Fuhrmann Yes, unfortunately Eyes on FHIR is inactive at the moment, and judging from the Zulip channel there is not much of an active ophthalmic FHIR community right now. I'm in contact with Ashley Kras, who was the project lead of Eyes on FHIR, we both want to get this ball rolling again because we are sure sure there is plenty of interest for FHIR moddeling in the ophthalmic sector. This is still in a very early planning phase, and I think there is a big need for community building at the FHIR side. I would be very interested in see if if there are EHRs or other stakeholders who want to use both an openEHR architecture for storage and FHIR for exchange for ophthalmic data? At the moment it seems to me that some regions emphasize interoperability by widespread use of openEHR implementations (UK/Scandinavia?) and others by FHIR-based exchange. So I'm not sure who currently has the need to use both, but I figure this is a question of time? For the moment I'll try and gain a better understanding of both openEHR and FHIR while Ashley and I explore whether we can get a FHIR-focused working group together to continue the the work of Eyes on FHIR. But as I am also really interested about the idea of a collaborative FHIR-openEHR Group, maybe it makes sense first try and experimentally start out such a collaboration on a really small, proof-of concept scale? For example, the Information model of my Visual Acuity Observation Profile in FHIR ist not that dissimilar to the Visual Acuity Test Result Archetype (Eye Examined <-> Observation.BodySite, components for distance, chart type and correction etc.) Is there anyone here who would like to collaborate with me to try and make openEHR <-> FHIR mapping work *just for Visual Acuity Data* at first? VA data is as difficult as it is indispensable, so i think it would be great point to start and build experience at collaberative FHIR-openEHR development in this area? If we succeed this could make it quite a bit easier to estimate the challenges that would be faced when trying to cover other parts of ophthalmology. --- ## Post #21 by @johngrant4est My knowledge of ophthalmology is based on anesthetizing eye patients for common operations such as cataract etc, and also the referral process from optometrist to hospital eye service in NHS Scotland. The VA assessment seems like a good starting point - I'm happy to set up a zoom call for interested parties. I'm in the UK but if you want to join, let know time zone and hopefully we can get a convenient time. --- ## Post #22 by @Lars_Fuhrmann That sounds great, thank you! And no worries about ophthalmic knowledge, i guess technical expertise is much more important for now. I like to think that I have reasonably good overview of VA testing from the clinical side. Plus I have a bit of a collection of (fictional but realistic) VA testing scenarios of varying complexity from very kind colleagues in different countries, which which can be helpful to check which in which models they do or do not "fit". thank you for offering to set up a zoom call, i think that's a good idea. I'm in Germany so GMT+1 but generally flexible. Anyone else interested? --- ## Post #23 by @heather.leslie Hi Lars, Have you seen the [Ophthalmology project in CKM](https://ckm.openehr.org/ckm/projects/1013.8.24) which has more archetypes that may be of use to your work. You will also see that the '[Visual acuity test result archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.1291) has been undergoing a [review](https://ckm.openehr.org/ckm/archetypes/1013.1.1291/reviewscontent), but this appears to have stalled way back in 2013 with a second review round unresolved. Remember that the FHIR profile will be based on the underlying Observation FHIR resource and that adds additional content that may not be required for the visual acuity use case, whereas the archetype will possibly be much leaner and utilise the underlying openEHR reference model attributes as necessary. That said, we would welcome alignment where possible. I'd like to volunteer @varntzen as CKA lead, at least to coordinate efforts so that we can bring it back to the community via CKM, and possibly myself if we can manage time zones - I'm in Melbourne, AU which unfortunately adds an extra layer of complexity in coordinating meeting times. @ian.mcnicoll initiated the last review round and may recall why the review was abandoned. --- ## Post #24 by @heather.leslie @Lars_Fuhrmann There is also a new proposal for '[Contrast sensitivity test](https://ckm.openehr.org/ckm/archetypeproposals/1013.38.357)' which you may be interested in. --- ## Post #25 by @ian.mcnicoll TBH I can't really recall why the original Visual Acuity review stalled. I don't recall that there was any particular major issue raised, just lack of time/ resource I think It was very much based on input from specialists at Moorfields Eye Hospital, particularly Bill Aylward who originated openEyes. I did get a little bit of feedback from on e of e openEyes developers who said that the archetype did not play as nicely as he had hoped in terms of visual acuity testing workflow e.g Pinhole testing then with visual aids, without aids etc, so that might be worth looking at again. I just watched a wee MedBlocks demo of an opthalmology solution they are developing https://youtu.be/ShCzrHlzmHo?t=1188 ![image|690x352](upload://wYBPsn5iwx2MSWdqZGVHiSfVWUK.jpeg) @Sidharth_Ramesh - how has the visual acuity archetype worked for you? My only advice would be to really keep the scope tight - Optom is highly specialised - stick to some common pathways - glaucoma, cataract to start with. --- ## Post #26 by @Sidharth_Ramesh Hey @ian.mcnicoll, yes, I can help provide the data models. @poorna can we provide a dump of all the archetypes and templates we're using? I know a lot of them aren't modeled perfectly, but at least we start a conversation around this. --- ## Post #27 by @Lars_Fuhrmann Thanks for pointing me to the Ophthalmology Project in the CKM, i will dive into the other Archetypes when I can . And many thanks for volunteering as CKA lead for the VA archetype! I already have ideas for things we could try and improve, i will write them down for discussion. In terms of time zones late evening or early morning German time would be OK for me, too at least to get things going. I have read through the Contrast sentitivity Archetype proposal from @Olha_Nikolaieva and offered my comments, we'll try and work together on this. But i do think it makes sense to consider the relationship between the Contrast Sensitivity and Visual Acuity Archetypes, as they are the two sides of the same coin do some degree. (there has to be contrast to resolve objects, and there have to be resolveable objects to measure contrast sensitivity). I think it would be very helpful for the CS Archetype if we improve the the VA Archetype first, because: 1. Lots of Items in the contrast sensitivity Archetype can be taken from the VA Archetype (Which eye, distance, Correction etc.), some of these require changes (for example the SNOMED-Codes For entire Right/Left Eye are inactive. Right/Left eye region may be better.), potentially the correction as well 2. The contrast sensitivity archetype proposal currently contains some methods which are actually "low contrast" Visual acuity tests (symbols get smaller and smaller under low contrast conditions). If we manage to model the contrast inside the Visual Acuity test ressource then these are actually more appropriate there. So i think it will be much easier to build the contrast Sensitivity Archetype based on an improved VA Archetype, and i hope we can do both. Please let me know if you have anything specific that I should look at or do to prepare. Hopefully today's course by @Sidharth_Ramesh will help me get me up to speed :) --- ## Post #28 by @Lars_Fuhrmann I think it very hard not to underestimate the complexity of even something as central to ophthalmology as Visual acuity Testing. VA testing is highly modular in real life as we are pretty free to combine things we put in front of patient's eyes (such as own glasses PLUS pinhole or contact lens PLUS trial Lenses) In FHIR this made me allow any number of component slices to specify a correction in front of a specified eye, such as contact lens plus trial lenses [here](https://larfuma.github.io/fhir-eyecare-ig/Observation-va-measurement-example-patient-1-with-overrefraction-v3.html) This could also be done for own Glasses or trial lenses PLUS pinhole, which is not that uncommon clinically, we do this to find out whether there is a component of irregular Astigmatism as it occurs in diseases like Keratokonus. So If we want to stay close to clinical reality specifying multiple type of corrections in front of each eye should be possible. I am extremely happy to see that @Sidharth_Ramesh and @poorna are working in Ophthalmology, that really is a great thing to happen to our field! Building a User-Friendly UI for highly granular data models in Ophthalmology is extremely challenging, but I'm hopefull that this will not scare you off and I'm happy to help if you want me to! Regarding the Scope: I agree about keeping it tight, think even pathway like cataract may be too large of a scope initially if we thing about everything that a patient getting cataract surgery goes through. I think it makes sense to focus on the very central, very basic clinical observations that are shared by pretty much all clinical pathways (such as VA testing), as the Ophthalmology Project in the CKM has done, and tackle these one by one before trying to model an entire pathway. --- ## Post #29 by @varntzen Hi all, There is an existing Ophthalmology collaboration incubator in the CKM, https://ckm.openehr.org/ckm/incubators/1013.30.95, dated back from 2021. It's empty by now. I suggest we use this incubator to upload archetypes that already exists locally. Some of them will eventually be moved to the Ophthalmology domain project . The incubator is per now private, which means users have to be named as Editor or Reviewer in order to enter. (Reviewer is misleading, it's not possible to run reviews from an incubator). The members per now are: ![image|519x381](upload://63hGtuZFnAGZLcaasSsaimLD5da.png) In addition, CKAs have access. Anyone else? All editors can add new members. We'll find a suitable time to meet virtually early next year. Until then, have a wonderful time off for those who celebrate Christmas or Solstice! --- ## Post #30 by @Lars_Fuhrmann Hello Everyone! I would like to invite you to a kick-off online meeting to discuss how we can pick back up on ophthalmic archetype development. I would suggest an initial focus on the Visual Acuity Archetype, because its review has been suspended since 2013 and it would absolutely be worth figuring out how openEHR and FHIR data models could align for this central observation. I would be very grateful if you could indicate your availabiliy if you are interested: https://rallly.co/invite/D51VBzboLl4f @SevKohler @johngrant4est @heather.leslie @Sidharth_Ramesh @varntzen @johngrant4est @Olha_Nikolaieva @bna @Kanthan_Theivendran @ian.mcnicoll I'll try and have draft revision of the Visual acuity Archetype ready by the time we meet, just as a basis for discussion/comparison. and I'll try to find some more ophthalmologists who may be interested in getting into openEHR. I'm very looking foward to our call! --- ## Post #31 by @e25cc02c Hi, could it be useful to present the way se have those documents in Finnish Kanta archive? Nice to know at least? If so, I could join. --- ## Post #32 by @Lars_Fuhrmann Hi Pirkko, Sure! Good idea, I think it would be great to get an overview of different models/archetypes, especially if they are currently in clinical use. Is here is anything I could have a look at ahead of time I think that may be useful ? Thanks! --- ## Post #33 by @e25cc02c To begin with here is the list of defined structures in Finland. The Finnish name has link to our code server with info in Swedish (except the ortoptic form)– in case it doesn’t open, I can pick the detailed documents. Are any of these on level of achitype or are they all templates, is a good question. --- ## Post #34 by @varntzen No link, Pirkko? --- ## Post #35 by @e25cc02c Optometri - Refraktionsmetod https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Observation of an eye https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Optometri/InformationsinnehĂ„ll - Strukturerad dokumentation inom optometri https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Ortoptic form (endast pĂ„ finska) https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Optometri/InformationsinnehĂ„ll - Tillpassning av kontaktlinser https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Refration https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Optometri/InformationsinnehĂ„ll - HĂ€lsokontroll av ögonen https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 Optometri/InformationsinnehĂ„ll - Fusion och ackommodation https://koodistopalvelu.kanta.fi/codeserver/pages/classification-view-page.xhtml?classificationKey=2286&versionKey=2546 --- ## Post #36 by @Lars_Fuhrmann Something that I wanted to add because it should not be overlooked: Aitor Eguzkitza has done a tremendous amount of modelling work in [this incubator](https://ckm.openehr.org/ckm/incubators/1013.30.6) approximately between the years 2014-2016 while at the universtity of Navarra. He has also written this article: [ Formalize clinical processes into electronic health information systems: Modelling a screening service for diabetic retinopathy](https://www.sciencedirect.com/science/article/pii/S1532046415001057), published it in the Journal of Biomedical Informatics. Can't believe 2015 is ten years ago, when it is the type of publications what we need in ophthalmological journals in 2025 (and in 2026, and in 2027.. ;) ) I will need to spend more time looking through this incubator to comprehend models, but I think we should take them into consideration going foward! And I'll try and reach out to him.. --- ## Post #37 by @Lars_Fuhrmann Hi everyone I wanted to let you know we’re **preparing a review round for the** [revised draft of the intraocular pressure archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.8097/mindmap)**. This means if you have eye care professionals in your network it might be a great time to reach out to them.** If you connect them with me to I will try and get them interested in becoming a reviewer (Bonus points if they work in countries other than Germany and the UK) . I like to think that we have gathered a little bit of momentum, in large part due to the unwavering patience of @heather.leslie @ian.mcnicoll and @siljelb , even during long discussions on the semi-quantitative evaluation of the squishiness (or non-squishiness!) of eyes on palpation. We have set up confluence pages for our “[Eye Care Archetype Modelling Collaboration](https://openehr.atlassian.net/wiki/pages/resumedraft.action?draftId=3017212009)” where you can keep track of our progress and discussions. As the Discourse thread on the visual acuity archetype filled up with technical discussions it became quite uninviting to clinical colleagues, so we have begun drawing a line between [clinical requirement discussions](https://openehr.atlassian.net/wiki/x/ggDttg) and [jira-based technical modelling discussions](https://openehr.atlassian.net/browse/CLINICAL-922). I also want to note that we have not given up on the visual acuity Archetype, but decided it may be best to first gather experience reviewing an Archetype that is a little bit simpler. A long-term record of IOP data is extremely important for glaucoma care, so this was an obvious choice Many thanks to everyone who has helped this effort so far, especially to: * The three mentioned above plus @arielyho for their help with our [Introduction to openEHR ](https://openehr.atlassian.net/wiki/x/AoBGvg) written specifically for eye care professionals in mind. * To Ian Rodrigues from the openEyes team for lending his expertise as a glaucoma consultant to the revision process. Please to get in touch if you are interested in doing anything with openEHR in the eye care domain in the future - *especially* if the Archetypes are not quite there yet for your use case. Our meeting times are on the landing page, feel free to drop in. --- ## Post #38 by @Lars_Fuhrmann I’m quite exited to announce that we have opened the first round of review for the [Intraocular Pressure Archetype](https://ckm.openehr.org/ckm/archetypes/1013.1.1369/mindmap). The deadline will be the 11th of January due to the holiday season, and because we are still working to invite more first time reviewers from the eye care professions. If you want to participate as a reviewer or know somebody know might be interested please don’t hesitate to get in touch. :slightly_smiling_face: Many thanks to everyone involved! --- ## Post #39 by @Lars_Fuhrmann Quick update: 1. We have completed the first review round of the Intraocular Pressure Archetype. With 21 reviewers from 9 different countries participating we got 6 votes to ‘Accept’ and 15 votes for ‘Minor Revision’. ^[More precisely they were 25 reviewers due to an extra review round in Norway facilitated by @siljelb .] I am exited to report that 15 eye care professionals lend their time and knowledge to this process, among which were experienced glaucoma experts. For 17 of the reviewers this was the first CKM review of their life, so congratulations and many thanks to them! 2. Even though we did not get any votes for a ‘Major revision’ we still made some significant changes based on the >100 comments we got from reviewers. So we angreed to have a second round, which is currently live. Please do get in touch if you want to participate! 3. Many thanks to @Pete_Bouvier for his help in designing a little logo for our open working group, which I think will be super-helpful as we try to engage colleagues to participate in our Archetype modelling efforts: ![image|690x172, 50%](upload://1sFTPFUbHE4rdXOZzsdO2k1qtWZ.png) and the new [banner for our confluence page:](https://openehr.atlassian.net/wiki/spaces/healthmod/pages/3017212009/openEHR+Eye+Care+Modelling+Collaboration) ![image|690x178](upload://bsviya53OaDFDWrKHfzMTAfFdxD.jpeg) Feedback/suggestions are appreciated. Out open working group still usually meets at the last Thursday of the month at 12:00 CET (except next week’s meeting will likely be rescheduled to the 5th of March). Feel free to say hello there! Many thanks to everyone involved, especially to @ian.mcnicoll, @heather.leslie and @siljelb , their guidance & unparralleled patience with us eye care professionals is absolutely essential to this effort! --- **Canonical:** https://discourse.openehr.org/t/eyes-on-openehr/6003 **Original content:** https://discourse.openehr.org/t/eyes-on-openehr/6003