This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Marcia Hawkins-Day
Authoring Organization(s)
CEPI
Email address
hawkinsdaym@michigan.gov
Use Case Title
Add properties for Effective Date and Expiration Date
Use Case Description
- Effective Date: The date on which the information contained in the record becomes valid or applicable, regardless of when the record was created or modified.
- Expiration Date: The date on which the information contained in the record is no longer valid or applicable.
Use Case Background
The State of Michigan has identified a need for general-purpose data elements that indicate when information within a record becomes effective and when it ceases to be valid. Although some CEDS classes include context specific effective or expiration dates, these apply to limited situations and do not address the broader need for a cross domain effective date/expiration date.
Record Effective Date and Record Expiration Date elements provide a consistent, cross domain way to define a record’s period of validity.
The Record Effective Date element indicates when a record becomes valid or applicable. It is intended for situations where no other context specific effective date exists, providing a single, consistent way to capture effective dates across all domains, while still allowing domain specific effective dates to coexist when multiple effective dates are required within a single class.
The Record Expiration Date complements the effective date by capturing when a record is no longer valid or applicable. This helps clearly define the period during which the data is valid.
Placing both elements in the CEDS Base Resource class ensures broad applicability across all domains. This approach provides a consistent structure for managing the lifecycle of records, while still allowing flexibility for classes that require additional, context specific dates.
Location of Element in the Domain Entity Schema
CEDSBaseResource
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Marcia Hawkins-Day
Authoring Organization(s)
CEPI
Email address
hawkinsdaym@michigan.gov
Use Case Title
Add properties for Effective Date and Expiration Date
Use Case Description
Use Case Background
The State of Michigan has identified a need for general-purpose data elements that indicate when information within a record becomes effective and when it ceases to be valid. Although some CEDS classes include context specific effective or expiration dates, these apply to limited situations and do not address the broader need for a cross domain effective date/expiration date.
Record Effective Date and Record Expiration Date elements provide a consistent, cross domain way to define a record’s period of validity.
The Record Effective Date element indicates when a record becomes valid or applicable. It is intended for situations where no other context specific effective date exists, providing a single, consistent way to capture effective dates across all domains, while still allowing domain specific effective dates to coexist when multiple effective dates are required within a single class.
The Record Expiration Date complements the effective date by capturing when a record is no longer valid or applicable. This helps clearly define the period during which the data is valid.
Placing both elements in the CEDS Base Resource class ensures broad applicability across all domains. This approach provides a consistent structure for managing the lifecycle of records, while still allowing flexibility for classes that require additional, context specific dates.
Location of Element in the Domain Entity Schema
CEDSBaseResource