This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA ReferenceApplication"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | [[category:RIMBAA | + | [[category:Closed RIMBAA Issue]] |
Closed - RIMBAA changed its mission and scope; and won't take on the job (itself) of creating a reference application. | Closed - RIMBAA changed its mission and scope; and won't take on the job (itself) of creating a reference application. | ||
Latest revision as of 17:25, 4 October 2010
Closed - RIMBAA changed its mission and scope; and won't take on the job (itself) of creating a reference application.
Summary
What is a RIMBAA Reference Application? Is this a running application or an IDE or both? UMCN has a RA, NHS has (part of) an IDE (the SMD) and PHI has an IDE that generates RA's.
Analysis
- Rene Spronk: by definition a RIMBAA application has to persist instances of RIM-based models (instances of data used in healthcare worklows). An IDE has knowledge of RIM based structures, but doesn't persist instances of those models. The IDE is a helpful/necessary tool for the generation of RA's, but in itself (to me) it is not a 'running RIMBAA application'.
- Michael van der Zel: I concur with Rene, but.. In the Model Driven paradigm the IDE is probably part of the running RIMBAA application. The question might be if a RIMBAA application is a MDA? I think it is.
Discussion
- Ecore
- OHT
