• Claim Detail Message Suite: Part 1 - Architecture
Hide navigation
  • Claim Detail Message Suite: Part 1 - Architecture
    • 1 Introduction
    • 2 Organisation of the Standard
    • 3 Normative References
    • 4 Terms and Abbreviations
      • 4.1 Terms and Definitions
      • 4.2 Abbreviations
    • 5 Choreography
    • 6 Relationship between DSR Messages and CDM Statements
      • 6.1 Number of messages
      • 6.2 Retractions and replacements
      • 6.3 Corrections
      • 6.4 Choreography without DSR Message
    • 7 Technical Details
      • 7.1 Baseline Format
      • 7.2 Character Coding
      • 7.3 Delimiters
      • 7.4 Primitive data types
      • 7.5 Empty Records
      • 7.6 Empty Cells
      • 7.7 Records to be ignored
      • 7.8 Mandatory Cells where no data is available
      • 7.9 Deprecated Cells
      • 7.10 Unknown Records
      • 7.11 Communicating decimals and integers
      • 7.12 Maximum Cell size
      • 7.13 Maximum file size
      • 7.14 Allowed-value sets
      • 7.15 User defined values
      • 7.16 Referencing Records
      • 7.17 Version
      • 7.18 Aiding human readability
    • 8 Transfer of CDM messages
      • 8.1 File name convention
      • 8.2 Sample File Names (informative)
      • 8.3 Sending and acknowledging CDM messages
      • 8.4 Sample SFTP server organisation
    • Annex A Release notes (informative)
Show navigation

7.12 Maximum Cell size

While some Cells have an inherent length, other Cells have no length limitation.

This has an implication for those using the CDM standard who have databases with field length limitations. Such users will be forced to shorten fields if the data received exceeds their databases’ capabilities.

Search

    Powered by Instant Websites for Confluence