Page History

...

For systems generating ODM files or messages:

1. Generated ODM for exchange as files and messages must satisfy all the relevant correctness rules in this standard, both syntactic and semantic.
2. Information included in the generated ODM files and messages must be accurate according to the rules of this standard as defined in this specification.
3. Systems generating ODM files or messages must support at At least one of the published media types, XML or JSON, must be supported.
4. Systems APIs generating ODM content via an API files and messages must return resources that satisfy all the relevant correctness rules for the elements represented in the resourcein this standard, both syntactic and semantic.Systems
5. APIs generating ODM content via an API must document the API files and messages must have their endpoints and the returned resources returneddocumented.
6. Generated ODM files need not include information that is not normally handled or stored by the generating system.
7. All system ODM generation limitations or constraints must be documented.
8. If conformity of the generated ODM files and messages is dependent on certain system modes or settings, this must also be documented.

9. Where Generated ODM files or messages must satisfy any ODM conformance rules that exist for a given the relevant use case, the generated ODM documents or messages must satisfy the relevant conformance rules.

For systems receiving ODM files or messages:

1. A receiving system must be able to read any ODM file or message that satisfies all the relevant correctness rules in this standard, both syntactic and semantic.
2. A system receiving an ODM file may validate the any ODM file against the ODM schema for the ODM version indicated in the ODM root element.
3. A receiving system must interpret information read from an ODM file or ODM API accurately according to the rules of this standard as defined in this specification.
4. A receiving system must support at least one of the published media types, XML or JSON.
5. Systems receiving ODM content via an API must be able to read any resources that satisfy all the correctness rules for the elements represented in the resource, both syntactic and semantic.
6. A receiving system may selectively ignore information read from an ODM file if that information is not normally handled or stored by the receiving system.
7. A receiving system may constrain the range of data values, keys, names, and so on, that it is capable of handling or storing.
8. Systems that receive ODM clinical data files but do A receiving system that does not normally support one or more of the datatypes specified in section 2.14, should accept clinical data of the unsupported types as text.
9. All A receiving system must document all ODM processing limitations or constraints must be documented.
10. Any A receiving system must document all system settings or modes of operations operation needed to receive and process ODM must be documented.files or messages.
11. A Where ODM conformance rules exist for a given use case, the receiving system should be able to confirm ODM conformance by running those rules against the received file or messageany conformance rules that exist for the relevant use case.