Motion to consider: VisionPrescription represents an authorization and specification for lenses. While one could create many DeviceDefinitions, these are custom specifications while DeviceDefinition manages model specifications and is not an authorization. Keep the name VisionPrescription as-is and address other custom specifications for later to sort out (e.g., pattern, some other more generic resource and use patterns where needed) Address where VisionPrescription should be referenced in, e.g., DeviceRequest, in a separate JIRA and address other custom devices. Clarify in VisionPrescription scope and boundary that it is not a SupplyRequest and describe the differences and use with other resources more clearly.