After importing a Scotty patient, how would you test to ensure mappings are correct?

• A. Test the curriculum that uses the patient
• B. Validate the patient in the system
• C. Check logs for errors
• D. Run a full backup

Answer: (A)

When you want to verify that mappings are correct after importing a Scotty patient, you test the actual component that will use that data—the curriculum that consumes the patient. Running a test through the curriculum lets you see end-to-end how each imported field appears in the places the curriculum expects them, and whether the data leads to the expected behavior or outputs.

Think of it this way: you import the patient, then you run a realistic scenario where that patient’s data drives the curriculum’s steps. Check that the patient identifier is recognized, demographics populate the correct fields, and clinical data (like diagnoses or treatments) appear in the parts of the curriculum that rely on them. If anything is mapped to the wrong field or misinterpreted, the curriculum’s flow or results will reveal the mismatch, and you can adjust the mappings accordingly.

Other actions, such as validating the patient’s existence in the system, scanning logs for errors, or running a full backup, don’t directly confirm that the import mappings align with how the curriculum uses the data. They’re useful for general health checks, but they don’t validate the correctness of the mappings in this end-to-end usage context.