Skip to main content

How do I edit or version an existing Data Standard?

Updated this week

Over time, your reporting needs may change. When that happens, you can update an existing Data Standard by creating a new version. Versioning allows you to make changes while preserving the integrity of previously published standards.

Editing a Data Standard does not automatically change how other organizations or programs are using it. Each version is reviewed and published intentionally.

When versioning is especially useful

Versioning is helpful when:

  • Reporting requirements change

  • New fields are needed

  • Existing fields need clarification or refinement

  • Best practices evolve across programs or partners

Using versions helps keep reporting aligned while respecting the timing and capacity of those implementing the standard.

Before you start

  • You must be an Apricot Administrator.

  • Only published Data Standards can be versioned.

  • Changes are made by creating a new version, not by editing the published version directly.

Create a new version of a Data Standard

  1. In Apricot, go to Administrator.

  2. Open Workflow Station, then select Data Standards.

  3. Open the Data Standard you want to update.

  4. Select View versions.

5. Choose New version.

  • A draft version is created using the current published version as a starting point. (needs new screenshot)

6. Make the updates you need, such as:

  • Adding or removing fields

  • Updating included forms

  • Adjusting descriptions or guidance

7. Select Review to confirm your changes.

8. Select Create New Version to make this version active.

Once published, the new version becomes the current version of the Data Standard.

What happens to existing data and implementations

Creating a new version does not delete or overwrite historical data.

Important things to know:

  • Existing data remains intact and reportable.

  • Organizations or programs using an earlier version are not forced to update automatically.

  • Network Members or internal teams can review and implement the new version when they are ready.

This approach allows you to evolve standards over time without disrupting ongoing work.

What else do you need help with?

Did this answer your question?