Hi again, I see from the list lots of people didn't get to read the actual article. I for some reason got a full text download for free, but I can see several of you didn't. Perhaps some sort of time limited offer after publication? I don't think it's easy to judge the article from the abstract, so I hope you can find a copy somewhere else. Perhaps a university library if you have access to one?
Regards, Silje -----Original Message----- From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Bert Verhees Sent: Friday, March 11, 2016 5:05 PM To: openehr-clinical@lists.openehr.org Subject: Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals How I see it, which is a very personal view, and very developer central, trying to think politically correct direction user. We can not live without users, not even in fantasy. So, we should always try to find users, an we should not start building an application before we found them. We can create tooling, that is all. I must also say that I did not read the paper, it is way too expensive to read it. 30 box, it must compete with a good wine, and then I am afraid, the paper will not win. There is nothing that rings alarm-bells saying I must read it. It are opinions. I have seen them come and go and I have seen them die and long ago I stopped asking why. Like Lucky Luke, I sing my "I am a poor and lonesome cowboy"-song. Independent developer, it is called. It has advantages, play chess with my horse. http://www.bendav.nl/gif/ebay10/107.jpg So, enough fun, now a more serious answer. Model Driven Development, on what level? Domain? You also have Domain Model Driven Modeling, first you have a RIM, then a DMIM and then a RMIM, Or first a Reference Model, then CKM, then a template-layer build on Contsys or something else. And from that we need to go to a nurse wanting to record the blood-pressure.. It has advantages for development, you know what to expect on specific situations, but the problem is that the domain experts go different directions then developers, and the models they create are in some detail terrible from developers point of view. I think this is mutually felt. But don't throw away the baby with the bathwater, there is always something good in it. That is the point, it is not a black and white question, trying to answer it in that way brings you to the same trouble as the domain model driven modelers bring you. Do you know, and this does not sound very scientific, but what we see a lot is: models, everywhere. Trying to capture life. Models for cities, models for the stock market, models for marriage, models for software domains, models for housing. Compare it with city-planning, as soon as there is an overall plan, it is very often doomed to fail. The strongest models are those which grow naturally, which evolve and evaluate constantly. Which give room for a bicycle-repair shop where no architect would ever plan it. We can draw some strong lines for the highways to avoid traffic-jam, that is it. We must learn to respect the micro-level, try not to solve other people's problems, don't be conceited, give problems time to solve themselves. First step in good software design is let go of the ego Listen to the nurse, on daily routine, does she/he take temperature before, or after she/he knows the patients-name? That is quite important to know, how many applications just assume something? There are models, Always look at them, and copy concepts, always learn from others. Contsys, HISA, smart thinking, but not holy grails. Keep your tooling/kernel flexible, keep everything flexible, have everything arranged so that flexibility remains possible on every level. Keep your database flexible, keep your queries flexible, keep your validation flexible And for that purpose, 2 Level Modeling is very good, an choose a good Reference Model, and why not OpenEHR if you are doing medical applications? I don't know if this was a useful answer, but still, have a nice day Bert _______________________________________________ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org _______________________________________________ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
