MHDS Specification 9.1 requires that MHDS-compliant booking systems offer therapists a way to import and export their data.
MHDS Specification 9.2 requires the following criteria for exports:
- 9.2.1. object data must be exported via a JSON file;
- 9.2.2. the JSON file must consist of a list of JavaScript objects;
- 9.2.3. a JSON file must only contain one type of MHDS object;
- 9.2.4. JSON files must only be transferred over a secure and encrypted connection;
- 9.2.5. export tools must not export User or Office data.
MHDS Specification 9.3 requires the following criteria for MHDS-compliant imports:
- 9.3.1. data must be imported via a JSON file;
- 9.3.2. the import tool must reject JSON files which do not comply with S9.2;
- 9.3.3. the booking system must check for duplicate IDs and provide new ones, where applicable;
- 9.3.4. the import tool must re-assign MHDS objects with the proper* User IDs and Office IDs, where applicable;
* The same therapist or office will likely have a different ID from one platform to another, given that IDs are pseudo-randomly generated. When exporting MHDS objects, they will be referencing therapists and offices with the IDs of the booking system that is exporting the data. The onus is on the import tool to prompt the user and assign the appropriate IDs, where applicable.