Uploaded image for project: 'Other Specification Feedback'
  1. Other Specification Feedback
  2. OTHER-2685

Clarify cardinality of individual data elements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: High High
    • HL7 Domain Analysis Model: Occupational Data for Health (OTHER)
    • 1.0.0
    • Public Health
    • (many)
    • Hide

      Clarification will be added that the cardinality of data elements within class models will not be defined in the DAM as they may vary by use case

      Show
      Clarification will be added that the cardinality of data elements within class models will not be defined in the DAM as they may vary by use case
    • Shirley Burton/Lori Fourquet: 28-0-0
    • Clarification
    • Non-substantive

    Description

      Cardinalities are assigned at the data class level but not at the level of the individual data elements. How should implementers of the data model understand the need for specific data elements? For example, if a system is designed to capture Employment status, is a status code absolutely required for a given period of employment? Is the start date absolutely required or is it permissible to have a code but not a start date. 

      If cardinalities aren't assigned at the data element level, please provide guidance on how systems should implement data elements in general (can they ever assume any given data element will or won't be valued)

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Craig Newman
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: