2016-05-05 Meeting Minutes

Owned by Emory Fry
May 05, 2016
1 min read

We will follow RLUS example with generic or abstract content model requirements - allow us to be isolated FHIR "noise" and keeps the door open for using models such as OpenEHR.

Will discuss in with O&O and SOA.

 

Graham

-Ordering Service SFM not informing conversation about FHIR Order Workflow operation/resource

-SFM includes discussion of REST and restful approaches

-SFM includes discussion of detailed, and concrete implementation considerations.  Not your typical more abstract, kitchen sink Domain Model 

-Ammonia level use case

-Fulfillment negoation use case

-Prospective, unendorsed/unsigned order management (medical student/resident) endorsement use cases

----Service architecture expects to see a broad discussion/handling of more complete order lifecycle discussion

Solution Suggestion

--invite FHIR re to join OMG work?

--how does OMG effort participate constructively with FHIR Order Workflow group without being being disruptive