Which statement is NOT a design principle for MTM documentation?

Which statement is NOT a design principle for MTM documentation?

• A. Documentation should be reproducible, billable, and measurable
• B. Structured SOAP documentation supports consistent follow-up
• C. Documentation should be primarily narrative with no clear structure
• D. Documentation should support liability tracking and outcome measurement

Answer: (C)

In MTM documentation, a clear, standardized structure that supports reproducibility, billing, and outcome measurement is essential. The statement that is not a design principle says the documentation should be primarily narrative with no clear structure. That approach makes it hard to reproduce encounters, bill for services, or track outcomes and liability. Using a structured format, like SOAP, ensures consistent follow-up and allows meaningful data capture. It also supports liability tracking and measuring results over time. So the unstructured, purely narrative approach does not fit MTM documentation principles.

In MTM documentation, a clear, standardized structure that supports reproducibility, billing, and outcome measurement is essential. The statement that is not a design principle says the documentation should be primarily narrative with no clear structure. That approach makes it hard to reproduce encounters, bill for services, or track outcomes and liability. Using a structured format, like SOAP, ensures consistent follow-up and allows meaningful data capture. It also supports liability tracking and measuring results over time. So the unstructured, purely narrative approach does not fit MTM documentation principles.