Comment:

In reality, the boundary between devices and medication is fluid, dictated by local jurisdictions, so it should not be too strict in the standard. Medication, device, etc. resources are currently not consistent not only in content (which is ok) but in general structure e.g. handling of identifiers and codes (which is manageable but not easy for implementation) and on handling of workflows (i.e. a product can be defined, then ordered, distributed, delivered, used/administered - this should be done in a consistent way). This consistency is also important for new resources (e.g. biologicallyDerivedProduct) or questions like "nutrition products" that may fall in a boundary. Suggest looking at existing resources and observe commonalities before implementation results in the incompatibility that can be seen in HL7 v2.

Summary:

Discuss a pattern or parent resource for Products, to avoid implementation questions, and ensure that the use of resources does not create obstacles to traceability and safety.