CCDD Technical specification edits proposed

Hello Marc
thanks for the question. I do not see this happening, however it is possible the status might change as you say
Regards
beverly

Regarding special_groupings_status, is it possible for the status to transition Active -> Inactive -> Active -> Inactive, and if so what happens to the special_groupings_status_effective_time?

Thanks,
Marc

Hi
Although we did not expect to make changes to the CCDD Technical Specifications we have received some excellent feedback from FDB and would like to highlight some changes we plan to make in the November Release. they include:
Coded_attribute file
Field for Attribute – defined as a String 8 but populated with text characters exceeding that (e.g. policy_type). Plan to increase the String character length as follows:
attribute String 8 The name of the specific coded attribute from the CCDD file type.
To
attribute String 50 The name of the specific coded attribute from the CCDD file type.

Full release file descriptions
All Full release file descriptions in the Technical Specification and where mentioned within the release notes will be edited as follows:
Current description:
The 'Full' release contains every concept that has ever been released. This release provides a full historical record and can be used to obtain views of the state of any concept at any point in time since its first release. The 'Full' release includes inactive and active concepts.
to
Future description
The 'Full' release contains one entry for every concept that has ever been released and new content added for that release. New content added for a specific release may at times include “Inactive” content.

Clarify Special Groupings Status date
Currently the Technical Specification as the following descriptions for special_groupings_status and special_groupings_status_effective_time
special_groupings_status: The lifecycle status of the relationship between the concept described in ccdd_code and the policy described in policy_type. Allowable values for this status are "Active" and "Inactive".
special_groupings_status_effective_time: The date of the relationship status described above. Format = YYYYMMDD.

The following will be the future description for
special_groupings_status_effective_time: For “Active” status entries, this is the date that the information became present in this file. For “Inactive” status entries, this is the date that the policy information in this file is no longer applicable. Format = YYYYMMDD.

If anyone has any concerns or questions with the above, please let me know
Beverly