Capturing temporal validity of data

[timgdavies]

In the Open Referral Legal Services working group call the issue came up of organisations that are only able to offer a particular service for a set period of time.

For example:

• An organisation receives a grant that allows them to provide a service to a particular population for a year;
• An organisation has a staff member going on parental leave, and therefore they cannot provide a service for a certain period;

Being able to capture this in HSDS could be very useful.

This issue is to log the need. More work will be needed to explore if/how this could/should be modelled.

[kinlane]

Great discussion. I feel like it overlaps with the overall data lifecycle discussion.

• Origin of data
• Logging each change (macro and micro) to a piece of data < historic change log
• Approval
• Transactional roll back
• TTL, or some sort of Time To Live imposed when it's created, or at some other point in time.

great thoughts Tim...look forward to more discussion.

[greggish]

This had come up before, and we encouraged folks to design their implementations to have time-stamped triggers of the status active / inactive field.

That said, it makes sense to include in future versions of the spec.