Motion to do the following:   Update SupplyDelivery.status from 0..1 to 1..1 Add SupplyDelivery.stage 1..1 and flag it as summary Add SupplyDelivery.stage valueSet, drafted here: https://build.fhir.org/branches/jct-supply/valueset-supplydelivery-stage.html  to have an Extensible binding instead of Required binding Change SupplyDelivery.type to have an Extensible binding instead of Required binding Add core profiles for dispatch and reception – drafted here: https://build.fhir.org/branches/jct-supply/supplydelivery-profiles.html For SupplyDelivery I propose the following: Scope and Usage Append the following text below the existing paragraphs: Sample use cases include: - Movement of bulk supplies between locations - Receipt of bulk supplies  - Rejection of a delivery due to item condition - Noting the loss of a delivery due to transportation failure The SupplyDelivery enables the documentation of the one or more relevant stages, such as dispatch of and reception of a shipment.  One may opt to document multiple stages given a particular use case, e.g., shipments of biologically derived products in a tightly controlled process, or only use a singular stage to summarize the shipment.  Examples would include the dispatch and reception stages that in certain use cases need to be documented separately using two or more instances. 7.  Update short Description & Constraint text for SupplyDelivery from "Delivery of bulk Supplies" to " Record of movement of supplies from one location to another ". 8. Add a pink ribbon to highlight the change and seek specific feedback on the implementability of one resource with multiple stages, each represented with specific profiles in the base standard to determine specific attributes/value sets applicable to each stage.  Note that this approach replaces a request to create two separate resources to address dispatch vs. reception where the discussion concluded that one resource with multiple, extensible stages provided a better approach to support the variety of needs to document the different steps. Note Jira ( FHIR-42947 ) that further clarified the Boundaries and Relationships need to reflect the difference between SupplyDelivery and Transport.