This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Fulfillment Manager Conceptual Specification"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "Link back to solution specification ==Overview== ===Service Description and Purpose=== ===Scope=== Comment Describe t...")
 
Line 20: Line 20:
 
The Fulfillment Manager Conceptual Diagram is shown below. Individual functional profiles have not yet been identified as we still need to work through the more complex use cases and identify the need for different profiles to support different contexts.
 
The Fulfillment Manager Conceptual Diagram is shown below. Individual functional profiles have not yet been identified as we still need to work through the more complex use cases and identify the need for different profiles to support different contexts.
  
[[image:OrderManagementConceptual.png ]]
+
[[image:FulfillmentManagementConceptual.png ]]
  
 
===Organization===
 
===Organization===

Revision as of 03:42, 26 November 2012

Link back to solution specification

Overview

Service Description and Purpose

Scope

  Comment
    Describe the overall potential scope of the service.  Are any items being specifically excluded from the scope?  Why?


Reason why the service is necessary

  Comment
    Rationale for creating this specification. Consumer viewpoint and the value offered by the work product

Links to Use Cases/ Storyboards

  • (optional, depending on detail in interop business scenario section

Structure of the Service

The Fulfillment Manager Conceptual Diagram is shown below. Individual functional profiles have not yet been identified as we still need to work through the more complex use cases and identify the need for different profiles to support different contexts.

FulfillmentManagementConceptual.png

Organization

 Comment
   Elaborate any logical groupings that emerge from the usage scenarios

Assumptions and Dependencies

 Comment
   Upon what services does this specification depend (underpinning infrastructure, other HL7 services,  etc. Are there any key assumptions that are being made?

Implementation Considerations

  Comment
    Relevant and representative examples of deployment scenarios. Consider representation formalism and the intended audience, not necessarily rigorously expressing the content in UML. This specification in the real world (e.g., relationships to existing infrastructure, other deployed services, dependencies, etc.). Consider the ways that information bindings will be realized through the operations. If necessary, outline a strategy for this binding.

Detailed Functional Model for Each Operation

Request Fulfillment

  • Description: Allows an order manager to request fulfillment of an order
  • Pre-Conditions:
  1. The client has sufficient information to create the request
  2. User or requestor has permissions to create a request within the context
  • Conceptual Information Objects
    • Inputs: Order
    • Outputs: Promise
  • Post-Conditions:
  • Exception Conditions: None identified
  • Aspects left for Technical Bindings (optional)
  • Reference to Functional Profiles (optional)
  • Notes

Communicate Result

  • Description: Allows the fulfill to communicate a result to the requestor.
  • Pre-Conditions:
  • Conceptual Information Objects
    • Inputs: Result
    • Outputs: Code
  • Post-Conditions:
  • Exception Conditions:
  • Aspects left for Technical Bindings (optional)
  • Reference to Functional Profiles (optional)
  • Notes

Cancel Order

  • Description: Used when a requstor (placer) would like for a previously requested, and not yet completed, order to not be performed.
  • Pre-Conditions:
  1. An order exists and the identifier is known
  2. The order is not completed
  3. The user or requestor has permission to update an order
  • Conceptual Information Objects
    • Inputs: Order, Order Identifier
    • Outputs: Order
  • Post-Conditions:
  1. The order referenced by order identifier has been cancelled and will not be acted upon.
  2. The cancel order identifier is returned
  • Exception Conditions:
  1. Order is not known to the fulfiller
  2. Order has already been completed

Retrieve Result

  • Description: Allows a requestor to retrieve a result from the fulfiller with using the result identifier
  • Pre-Conditions:
  1. The result identifier has been previously communicated to the fulfiller.
  • Conceptual Information Objects
    • Inputs: Result Identifier
    • Outputs: Result
  • Post-Conditions
  • Exception Conditions
  • Aspects left for Technical Bindings (optional)
  • Reference to Functional Profiles (optional)
  • Notes


Profiles

Introduction

Functional Profiles

Information Profiles

  Comment
    - describe any information profiles applicable to this service, and the related state transitions

Recommendations for Conformance and Compliance