Difference between revisions of "Service Decomposition in RIMBAA Applications"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
[[category:RIMBAA Issue]]  
+
[[category:Closed AID Issue]]  
 
==Introduction==
 
==Introduction==
 
*If (as an implementer) one is requested to implement a number of course-grained (HL7v3 based) services [or the equivalent in terms of v3-messaging: a number of v3-interactions], how does one decompose these services into (backend/internal) fine-grained services?
 
*If (as an implementer) one is requested to implement a number of course-grained (HL7v3 based) services [or the equivalent in terms of v3-messaging: a number of v3-interactions], how does one decompose these services into (backend/internal) fine-grained services?

Latest revision as of 08:12, 25 March 2015

Introduction

  • If (as an implementer) one is requested to implement a number of course-grained (HL7v3 based) services [or the equivalent in terms of v3-messaging: a number of v3-interactions], how does one decompose these services into (backend/internal) fine-grained services?
  • See [1] and [2] on the general principles of service composability.

Discussion

  • From a static model perspective this raises issues similar to this one: Safe querying of a RIM-based data model - how does one select "selfcontained/contextualized subsets" of the static model as used by the course-grained service.