Page History

The value of the ODM standard, like any information standard, is enhanced when systems can be developed with the assumption that ODM files have a high level of conformity. However, the ODM also provides value in that it provides both a standard and a technology for the interchange of clinical data where none has existed in the past. The conformity statements below represent an attempt at balancing the need for quality control with respect to the standard with the need for flexibility when encouraging adoption and innovation:  A computing system that processes information in ODM format can claim conformance to this standard only if it obeys the following rules.

For systems generating ODM files or messages:

1. Generated ODM files and messages must satisfy all the relevant correctness rules in this standard, both syntactic and semantic.A receiving system
2. Information in generated ODM files and messages must be able to read any ODM file that satisfies all the correctness rules in this standard, both syntactic and semantic.
3. ODM files must validate against the ODM schema for the ODM version indicated in the ODM root element.
Information included in generated ODM files must be accurate according to the rules of this standard as defined in this specification.
4. accurate according to the rules of this standard as defined in this specification.
5. At least one of the published media types, XML or JSON, must be supported.
6. APIs generating ODM files and messages must have their endpoints and returned resources documented.
7. All ODM generation limitations or constraints must be documented.
8. If conformity of generated ODM files and messages is dependent on certain system modes or settings, this must be documented.

9. Generated ODM files or messages must satisfy any ODM conformance rules that exist for the relevant use case.

For systems receiving ODM files or messages:

1. 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.Generated ODM files need not include information that is not normally handled or stored by the generating system.
2. A receiving system may selectively ignore information read from an ODM file if that information is not normally handled or stored by the receiving systemmust support at least one of the published media types, XML or JSON.
3. A receiving system may constrain the range of data values, keys, names, and so on, that it is capable of handling or storing.Systems that receive ODM clinical data files but do that does not normally support one or more of the datatypes specified in section Section 2.14, Data Formats, should accept clinical data of the unsupported types as text.
4. All system limitations (rules 6 through 9) must be documented.
5. A receiving system must document all ODM processing limitations or constraints.
6. A receiving system must document all system settings or modes of operation needed to receive and process ODM files or messagesIf conformity is dependent on certain modes or settings, this must also be documented.