This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "SAIF Alpha OO"

From HL7Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 8: Line 8:
 
ArB Facilitator: John Koisch; jkoisch@guidewirearchitecture.com
 
ArB Facilitator: John Koisch; jkoisch@guidewirearchitecture.com
  
Project Fac: Patrick Loyd, Lorraine Constable, lorraine@constable.ca
+
Project Fac: Patrick Loyd, Lorraine Constable; lorraine@constable.ca
  
 
== Conference Calls and Minutes ==
 
== Conference Calls and Minutes ==
Line 21: Line 21:
  
 
==Documentation==
 
==Documentation==
* [[Lab Order Conceptual Specification]]
 
 
* [[Conceptual BF Document]]
 
* [[Conceptual BF Document]]
 
* [http://www.ncientarch.info/hl7_bf/ SAIF BF UML Diagram]
 
* [http://www.ncientarch.info/hl7_bf/ SAIF BF UML Diagram]
Line 34: Line 33:
 
* [http://gforge.hl7.org/gf/project/orders/scmsvn/?action=browse&path=%2Ftrunk%2FPOOR%2Fbf%2F Project Repository on GForge]
 
* [http://gforge.hl7.org/gf/project/orders/scmsvn/?action=browse&path=%2Ftrunk%2FPOOR%2Fbf%2F Project Repository on GForge]
 
* OO Domain Analysis Document (Draft)  
 
* OO Domain Analysis Document (Draft)  
* OO Behavioral Model Specification (Draft)
+
* [[OO Behavioral Model Conceptual Specification]] (Draft)
  
 
[[Category:SAIF_AP_Projects]]
 
[[Category:SAIF_AP_Projects]]

Latest revision as of 17:47, 12 September 2011

Back to Orders & Observations WG main page

Leadership

Co-Chair: Patrick Loyd; 415-209-0544, patrick.e.loyd@gmail.com

ArB Facilitator: Grahame Grieve; grahame@kestral.com.au

ArB Facilitator: John Koisch; jkoisch@guidewirearchitecture.com

Project Fac: Patrick Loyd, Lorraine Constable; lorraine@constable.ca

Conference Calls and Minutes

Dates: Currently, this project doesn't meet separately, but with the OO WG

Project Charter

Orders and Observations has engaged a SAIF Alpha Project to determine to what degree the HL7 SAIF Behavioral Framework can and should be used to develop a Behavioral Model for Orders and Observations. The intent is that this new Behavioral Model can more adequately and comprehensively capture the behavioral semantics of integration, specifically, business process state machines, overarching business processes, and a consistent means of separating out accountability.

Documentation

Deliverables

Links