I took a look at the xml file and it appears that the ItemOID is based on the where clause definition, which means that all origins for a given where clause are repeated within each item that uses that where clause.
I don’t think a user can avoid this without editing the outputted define.xml, but if the next update of P21 could base ItemOID on something more than the where clause, I think this would no longer be an issue.
If anyone has found a way around this, I’d be very keen to hear it.
Item-OIDs and WhereClause-OIDs should be independent of each other for reasons of reusability.
Simple example: SYSBP and DIABP normally have the same properties and thus share the same WhereClause.
Sophia, Matt, if you contact me I can show you how I found a way around this. It is hard to explain here, but I can show you.
I have unsuccessfully tried to find a workaround for 2 hours - but cannot find how to tweak the Excel file to avoid the problem.
I would be interested to know if there is a workaround.
When the same whereclause is used multiple rows in ValueLevel sheet, the text “Derived” is displayed multiple times in each of the metadata records in Origin/Source/Method/Comment column in define.xml. Please see the attached screenshots. Thanks, Sophia
