Why English? | Reporting mERA Mobile Health Interventions Through Infrastructure, Interoperability, Access, Security, Scale and Fidelity

ORIENTATION

What this guide owns

Current fact check

mERA is a 2016 WHO-linked reporting guideline for mobile-health interventions. It has 16 core items focused on intervention content, context and technical features, plus 29 methodological reporting items in a web appendix.

Canonical boundary

This article owns reporting of mobile-health interventions with mERA. It does not prescribe technology architecture, certify data security or regulatory compliance, replace CONSORT or STROBE, or prove feasibility, effectiveness or scalability.

Worked example

Every chapter returns to a fictional mobile programme that sends study-wellbeing prompts and routes selected responses to a support team. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.

Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.

CHAPTER 1 OF 13

1. Describe the Infrastructure Needed

Back to contents

Why this move matters

Report electricity, connectivity, coverage, devices, charging, hosting and other system dependencies.

Place the phone inside the wider system

Report electricity, connectivity, coverage, devices, charging, hosting and other system dependencies. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to The programme requires basic smartphones, intermittent data and a server that queues messages during outages. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

National coverage statistics may hide local dead zones. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Describe the Infrastructure Needed”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 2 OF 13

2. Specify the Technology Platform

Back to contents

Why this move matters

Name channels, software, version, open or proprietary components, hosting and major technical functions.

Place the phone inside the wider system

Name channels, software, version, open or proprietary components, hosting and major technical functions. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to The programme uses an Android application with SMS fallback and a dated server release. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

A platform brand does not reveal the implemented configuration. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Specify the Technology Platform”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 3 OF 13

3. Explain Interoperability and Information-System Context

Back to contents

Why this move matters

Describe data exchange, identifiers, standards, manual transfer and how the intervention fits existing records and workflow.

Place the phone inside the wider system

Describe data exchange, identifiers, standards, manual transfer and how the intervention fits existing records and workflow. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Selected alerts enter a support dashboard but do not write directly to the school record. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Manual copying can create delay, omission and duplicate work. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Explain Interoperability and Information-System Context”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 4 OF 13

4. Map Intervention Delivery

Back to contents

Why this move matters

Show who initiates each contact, timing, direction, automation, escalation and response expectations.

Place the phone inside the wider system

Show who initiates each contact, timing, direction, automation, escalation and response expectations. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Scheduled prompts are automated; risk responses create a reviewed task during staffed hours. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Automated delivery does not mean automated interpretation or care. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Map Intervention Delivery”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 5 OF 13

5. Make the Content Inspectable

Back to contents

Why this move matters

Describe message libraries, language, media, behaviour-change elements, authorship, update process and access to materials.

Place the phone inside the wider system

Describe message libraries, language, media, behaviour-change elements, authorship, update process and access to materials. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to The report provides sample prompts and the rules that select them. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

A sample can mislead if it omits difficult or high-risk content. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Make the Content Inspectable”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 6 OF 13

6. Report Usability and Content Testing

Back to contents

Why this move matters

State prototypes, participant groups, tasks, languages, devices, changes and unresolved usability problems.

Place the phone inside the wider system

State prototypes, participant groups, tasks, languages, devices, changes and unresolved usability problems. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Students test message clarity and navigation on low-cost devices before rollout. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Positive testing with a small group cannot guarantee population usability. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Report Usability and Content Testing”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 7 OF 13

7. Describe User Feedback During Implementation

Back to contents

Why this move matters

Explain help routes, complaints, feedback collection, response times and how feedback changed the system.

Place the phone inside the wider system

Explain help routes, complaints, feedback collection, response times and how feedback changed the system. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Users can report confusing prompts, with changes versioned and dated. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Feedback channels may be used mainly by confident participants. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Describe User Feedback During Implementation”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 8 OF 13

8. Report Individual Access and Exclusion

Back to contents

Why this move matters

Describe device ownership, shared phones, literacy, disability access, language, gender or household control and support provided.

Place the phone inside the wider system

Describe device ownership, shared phones, literacy, disability access, language, gender or household control and support provided. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to The study records whether the phone is personal or shared and offers an alternative access route. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Possession of a phone does not guarantee private or autonomous use. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Report Individual Access and Exclusion”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 9 OF 13

9. Account for Costs

Back to contents

Why this move matters

Report development, devices, data, staff, training, maintenance and user costs from stated perspectives.

Place the phone inside the wider system

Report development, devices, data, staff, training, maintenance and user costs from stated perspectives. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to The report separates research-only development from routine service costs. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

A free application can still shift data and time costs to users. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Account for Costs”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 10 OF 13

10. Explain Adoption Inputs and Programme Entry

Back to contents

Why this move matters

Describe recruitment, registration, identity, eligibility, onboarding, training and reasons users or sites did not enter.

Place the phone inside the wider system

Describe recruitment, registration, identity, eligibility, onboarding, training and reasons users or sites did not enter. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to A participant receives a verified invitation and completes an assisted first login. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Registration counts can exaggerate active adoption. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Explain Adoption Inputs and Programme Entry”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 11 OF 13

11. State Limitations for Delivery at Scale

Back to contents

Why this move matters

Identify infrastructure, workforce, governance, financing, supply, language and support constraints that emerge beyond a pilot.

Place the phone inside the wider system

Identify infrastructure, workforce, governance, financing, supply, language and support constraints that emerge beyond a pilot. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to National expansion would require staffed escalation, multilingual content and reliable support coverage. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

A technically scalable server does not make the service system scalable. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “State Limitations for Delivery at Scale”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 12 OF 13

12. Describe Contextual Adaptability and Replicability

Back to contents

Why this move matters

Report which components are fixed, which can be adapted, the rules for change and the materials another setting would need.

Place the phone inside the wider system

Report which components are fixed, which can be adapted, the rules for change and the materials another setting would need. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Local teams may translate prompts but must preserve escalation categories and version control. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Adaptation can alter the mechanism if boundaries are vague. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Describe Contextual Adaptability and Replicability”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

CHAPTER 13 OF 13

13. Report Security, Regulation and Fidelity

Back to contents

Why this move matters

Describe data security, access control, retention, relevant national rules, monitoring, actual delivery, user receipt, deviations and failures.

Place the phone inside the wider system

Describe data security, access control, retention, relevant national rules, monitoring, actual delivery, user receipt, deviations and failures. Explain infrastructure, interoperability, staff workflow and user access rather than treating the handset as the entire intervention.

Trace one message or transaction

Apply the item to Logs show transmission and response while audits examine access and escalation fidelity. Follow content creation, transmission, receipt, user response, data return, escalation and storage, including what happens when connectivity fails.

Distinguish adoption from impact

Report entry into the programme, continued use, fidelity and user feedback separately from health or service outcomes. High message delivery does not by itself show understanding or benefit.

Keep scaling claims conditional

Encrypted transmission does not solve every privacy or governance risk. mERA improves reporting of mobile-health evidence; it does not select a research design, certify regulatory compliance or guarantee successful national scale-up.

Student, parent and career transfer

Make one evidence card for “Report Security, Regulation and Fidelity”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports mobile health, digital education, public health, information systems, implementation research and service design without promising a grade, admission, funding decision or job.

PRACTICE LAB

Build an mHealth decision trail

Student route

1. Choose one original report inside this guide’s scope.
2. Copy its objective and underline actor, action, context, evidence and intended decision.
3. Draw the specific reasoning chain used in this article.
4. Mark each step reported, inferred, contested or unknown.
5. Rewrite the conclusion so it preserves the narrowest important limitation.

Parent or teacher route

Ask the learner to explain mERA’s central reporting method twice: once to a classmate and once to a method specialist. Praise a precise correction and a well-stated unknown; both show disciplined attention to evidence.

Early-career route

Create a one-page mERA audit with source link, date checked, scope, method logic, decisive wording, contrary evidence, limit and next action. A colleague should be able to continue without guessing.

Continue with eduKate’s guides to reading course and career information and giving useful feedback in group projects.

USEFUL NEXT READING

Connect this narrow owner to its neighbour

Read the CONSORT-EHEALTH digital-health trial reporting guide for a related but different reader job. Return here when the question is specifically how to explain how a mobile-health intervention works inside real infrastructure and service delivery. This boundary keeps one canonical owner per intent.

For English practice across research, school and career communication, visit the English at work and in public life guide.

FREQUENTLY ASKED QUESTIONS

Questions students and parents often ask

What does mERA stand for?

mHealth evidence reporting and assessment.

How many core items are there?

Sixteen, plus a separate 29-item methodological appendix.

Does it replace CONSORT or STROBE?

No. Authors should also use the guideline appropriate to the study design.

Is message delivery the same as intervention receipt?

No. Delivery, opening, understanding and action are different stages.

Why include interoperability?

Mobile tools often depend on existing records, identifiers and staff workflow.

Does mERA certify security or scalability?

No. It improves reporting so these claims can be appraised.