This wiki has undergone a migration to Confluence found Here

Software Implementation of CDA

From HL7Wiki
Revision as of 13:58, 13 October 2009 by Rene spronk (talk | contribs) (New page: category:RIMBAA Issue ==Summary== Question: if my software application solely has to support the CDA R2 model, what should my application architecture look like? What approach with reg...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Summary

Question: if my software application solely has to support the CDA R2 model, what should my application architecture look like? What approach with regards to code generation and persistence is appropriate?

Details

The more generalized question would be: if I have to support/persist only 1 single R-MIM/CIM, what should the architecture of my RIMBAA application be?

CP-CO-CS (using technology matrix terms) is probably the way to support this,

  • with MIF based code genration for CO (e.g. using Dave Carlson's CDA tool) or schema based code generation if one can't use the MIF tool.
  • And use a standard ORM tool for CP-CO.

Discussion

Peter Hendler: I you are certain that you will never need to persist another R-MIM then Dave Carlsons way would be fine. Your application could not be upgraded to handle another type unless it were RIM not clone classes. I suppose you could add that later. I'd be uncomfortable locking down an application to a specific R-MIM.