2016 PIM Data Model

2016 PIM Data Model

Main Model

Platform Independent Model.wmf

 

Support Data

Support Data.wmf

Rationale

Rationale.wmf

Update History

Date

Who

Change

Date

Who

Change

10/26/2016

Jerry Goodnough

Cleanup, Added: Proposal, Result Argumentations, Operation Results

9/22/2016

HL7 OO

Look at support for CopyTo behavior.

9/8/2016

Jerry Goodnough

Fixed the Date in Query Filter

9/8/2016

Jerry Goodnough

Added Order Context to Order

8/18/2016

Jerry Goodnough & Lorraine Constable

Added Priority to Order.

8/18/2016

Jerry Goodnough

Added Query Filter support class

8/18/2016

Jerry Goodnough

Added Order Summary and Order Summary Info for Order Query Results

8/18/2016

Jerry Goodnough

Change Rationale Class from Abstract to wrapper.

8/18/2016

Jerry Goodnough

Added Rationale and separate diagram. Now with new rationale model and types. Change Order reason to CDS Rationale.Updated Subjective Rationale to include the author. Added Policy Rationale and Care Plan Goal Rationale. Create Common Rational type.

8/12/2016

Jerry Goodnough

Itemized Requirement extended to include requirement and type.

8/4/2016

Jerry Goodnough

Three types of Rational called out now - Current topic of Discussion.

8/4/2016

Jerry Goodnough

Fulfillment Association extended to include FulfilmentPeriod to better reflect the historical view of Fulfillments

8/3/2016

Jerry Goodnough

Rationale Member made

8/3/2016

Jerry Goodnough

Reference Types made explicit

8/3/2016

Jerry Goodnough

Added FulfillmentAssocation and Fulfillers to OrderItem

8/3/2016

Jerry Goodnough

Reworked Diagrams to split out Support Data

7/7/2016

Jerry Goodnough

First pass of attribute Multiplicity and type.

7/7/2016

Jerry Goodnough

Added first cut of core datatype classes (Modeled on Simple FHIR)

7/7/2016

Jerry Goodnough

Added Reference Type concept.

7/7/2016

Jerry Goodnough

Shifted Identifier<Type> to simple Identifier.

6/14/2016

Jerry Goodnough

Added Itemized Requirement class to allow requirements to be referenced in the workflow and fulfillment interfaces - Both of with should now use a List of Itemized Requirements rather then the requirement object. This it an additional case where the requirements catalog could be very useful.

6/9/2016

Jerry Goodnough

Standardize a code and enum references to a coding

6/9/2016

Jerry Goodnough

Abstract the Subject be a Subject Reference with supports Multiple Identifiers and the ability to have a Subject Type specific details.

6/7/2016

Jerry Goodnough

Updated Order Response, Subject Identity to refer to any subject type - Not just Patient.

6/7/2016

Jerry Goodnough

Added Order Item Identifier

6/7/2016

Jerry Goodnough

Change Order Identity to Order Identities

6/7/2016

Jerry Goodnough

Created Requirement Association class to allow direct binding to an Order Item, rather then an order. This corrects an oversight with the requirements associated by a fulfillment service implementation and provides correct granularity.

6/7/2016

Jerry Goodnough

In Requirement Status change the attribute "RequirementIdentifier" to "Requirement Identifer"

Old Model

Conceptual Order Information Objects without exceptions.wmf

Conceptual Order Information Objects without exceptions.svg