Versions Compared

Old Version 17

changes.mady.by.user Jerry Goodnough (Unlicensed)

Saved on

compared with

New Version 18

changes.mady.by.user Jerry Goodnough (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Update History

DateWhoChange
9/22/2016HL7 OOLook at support for CopyTo behavior.
9/8/2016Jerry GoodnoughFixed the Date in Query Filter
9/8/2016Jerry GoodnoughAdded Order Context to Order
8/18/2016Jerry Goodnough & Lorraine ConstableAdded Priority to Order.
8/18/2016Jerry GoodnoughAdded Query Filter support class
8/18/2016Jerry GoodnoughAdded Order Summary and Order Summary Info for Order Query Results
8/18/2016Jerry GoodnoughChange Rationale Class from Abstract to wrapper.
8/18/2016Jerry GoodnoughAdded 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/2016Jerry GoodnoughItemized Requirement extended to include requirement and type.
8/4/2016Jerry GoodnoughThree types of Rational called out now - Current topic of Discussion.
8/4/2016Jerry GoodnoughFulfillment Association extended to include FulfilmentPeriod to better reflect the historical view of Fulfillments
8/3/2016Jerry GoodnoughRationale Member made
8/3/2016Jerry GoodnoughReference Types made explicit
8/3/2016Jerry GoodnoughAdded FulfillmentAssocation and Fulfillers to OrderItem
8/3/2016Jerry GoodnoughReworked Diagrams to split out Support Data
7/7/2016Jerry GoodnoughFirst pass of attribute Multiplicity and type.
7/7/2016Jerry GoodnoughAdded first cut of core datatype classes (Modeled on Simple FHIR)
7/7/2016Jerry GoodnoughAdded Reference Type concept.
7/7/2016Jerry GoodnoughShifted Identifier<Type> to simple Identifier.
6/14/2016Jerry GoodnoughAdded 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/2016Jerry GoodnoughStandardize a code and enum references to a coding
6/9/2016Jerry GoodnoughAbstract the Subject be a Subject Reference with supports Multiple Identifiers and the ability to have a Subject Type specific details.
6/7/2016Jerry GoodnoughUpdated Order Response, Subject Identity to refer to any subject type - Not just Patient.
6/7/2016Jerry GoodnoughAdded Order Item Identifier
6/7/2016Jerry Goodnough

Change Order Identity to Order Identities

6/7/2016Jerry GoodnoughCreated 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/2016Jerry GoodnoughIn Requirement Status change the attribute "RequirementIdentifier" to "Requirement Identifer"

...