This wiki has undergone a migration to Confluence found Here
Difference between revisions of "QDM Based HQMF R1.1"
Jump to navigation
Jump to search
(flavorId) |
|||
| Line 4: | Line 4: | ||
---- | ---- | ||
| − | To reduce the amount of syntax needed for handling non-null attributes in QDM (i.e., through flavorId), please consider only requiring the parent node for the specific attribute to contain the flavorId - not item. This would need to be done for all attributes whose respective node in the XML would contain an item node to handle value sets (e.g., value for some results, value for the 'result' supporting template, length of stay). | + | To reduce the amount of syntax needed for handling non-null attributes in QDM (i.e., through flavorId), please consider only requiring the parent node for the specific attribute to contain the flavorId - not item. This would need to be done for all attributes whose respective node in the XML would contain an item node to handle value sets (e.g., value for some results, value for the 'result' supporting template, length of stay). This will also mean that an attribute's value/xsi:type=”CD” constraint in supporting templates will need to be relaxed. |
Latest revision as of 18:24, 9 December 2014
Please post your comments to the QDM-based HQMF IG R1.1 below:
To reduce the amount of syntax needed for handling non-null attributes in QDM (i.e., through flavorId), please consider only requiring the parent node for the specific attribute to contain the flavorId - not item. This would need to be done for all attributes whose respective node in the XML would contain an item node to handle value sets (e.g., value for some results, value for the 'result' supporting template, length of stay). This will also mean that an attribute's value/xsi:type=”CD” constraint in supporting templates will need to be relaxed.
