Healthcare Administration & Management · Independent exam preparation

CTTP Certification Exam Study Guide

Practise choosing telehealth modalities, organizing monitoring, protecting patient information, and evaluating safe, accessible services for GHA Institute’s CTTP.

By CertMedbry · Updated 4 November 2026

60 concepts explainedWorked examples & common pitfallsOfficial blueprint references

Practise deciding which telehealth approach fits a patient’s needs, how monitoring data should lead to action, and when privacy, examination limits, or emergencies require a different response. These 60 concepts connect service design with daily operations, information protection, and program evaluation. The official GHA Institute course outline and Key Outcomes define the complete published scope; this guide is a selective study resource.

Try 20 free practice questions

What is the exam format?

Check the question types, timing and outline before planning your revision.

Which credential and examination does this guide address?

It addresses GHA Institute’s Certified Telemedicine/Telehealth Professional (CTTP) credential and named CTTP Certification Exam. The issuer describes CTTP as introductory professional education, with no course prerequisites. It does not establish RN or NP licensure or expand a clinician’s practice authority.

Certified Telemedicine/Telehealth Professional (CTTP)

How does CTTP differ from A-CTTP?

A-CTTP is a separate advanced program. The historical linked curriculum describes additional quality content and a laboratory for experienced professionals and administrators. This guide follows introductory CTTP; these sources do not establish A-CTTP examination specifications or equivalence.

CTTP 467 Curriculum · Certified Telemedicine/Telehealth Professional (CTTP)

What are the question count and scored or pretest item counts?

The cited official materials do not state the certification examination’s total question count or distinguish scored from pretest questions. This resource contains 20 independent learning questions; that count does not describe the actual examination.

Certified Telemedicine/Telehealth Professional (CTTP) · CTTP 467 Curriculum

What examination duration, delivery method, and adaptivity are verified?

The issuer’s currently accessible, undated FAQ states that the certification examination is delivered through its learning management system after completion of the three-day course. This independently published FAQ provides more specific delivery information than the course page, which describes online, self-paced education and an included examination. Learning management system delivery does not establish the examination’s time limit, proctoring arrangements, physical testing-location requirements, or adaptive versus fixed delivery; those details remain unestablished. Course contact hours and completion estimates are not examination time limits.

GHA Institute · Certified Telemedicine/Telehealth Professional (CTTP)

Which examination item styles and passing requirements are verified?

The issuer’s currently accessible, undated FAQ states that learners must achieve 100% on all quizzes and at least 80% on the certification examination. The historical CTTP 467 curriculum also states these thresholds, but its event disclosures expired October 14, 2026. The separate FAQ supports reporting the thresholds as issuer-published requirements without establishing a newly dated examination specification or renewing the historical event disclosures. Examination item styles remain unverified. These four-option drills do not simulate the issuer’s examination format or predict passing.

GHA Institute · CTTP 467 Curriculum

Which outline and effective dates apply?

The undated official course page and Key Outcomes define the published scope. They provide no syllabus effective date or examination domain percentages. The linked CTTP 467 document has a 2023 filename and expired event disclosures; it supplies historical detail, without establishing a renewed effective date. The guide distributes attention across all four study groups without claiming official weights.

Certified Telemedicine/Telehealth Professional (CTTP) · CTTP 467 Curriculum

This independently authored guide prepares learners for GHA Institute’s introductory Certified Telemedicine/Telehealth Professional (CTTP) pathway. Its four study domains organize the published topics editorially. They are not issuer-designated weighted examination domains. United States regulatory examples are identified by jurisdiction.

Outline used: Undated official CTTP course scope and Key Outcomes, available on 2026-10-19. The workbook label maps to GHA Institute's Certified Telemedicine/Telehealth Professional (CTTP) credential and its CTTP Certification Exam. The linked CTTP 467 curriculum has a 2023 filename and event disclosures expiring 2026-10-14; that detailed document is historical. No replacement effective date or examination domain percentages were stated.

60 key concepts: understand, apply and avoid the traps

Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.

Foundations, technology, and service designnot stated

1.What distinguishes telemedicine from broader telehealth?

Telemedicine describes clinical services delivered through telecommunications, including assessment and treatment. Telehealth also encompasses activities that support health and healthcare delivery, such as education and information exchange. Classify the actual activity rather than the device used: the same video platform can support a clinical consultation or staff education. This distinction helps define the service’s purpose, participants, documentation needs, and relationship to the wider care program.

Apply it

A clinic uses video for a patient assessment and a separate staff training session. Describe the assessment as telemedicine within telehealth, while classifying the training as a broader telehealth activity supporting service delivery.

Common pitfall: Calling every digital interaction telemedicine obscures whether clinical care occurred. A technology’s presence does not establish the purpose or professional responsibilities of its use.

CTTP 467 Curriculum · Getting started with telehealth

2.When does synchronous care add value?

Synchronous care involves interaction in real time, allowing immediate questions, clarification, and observation when video is available. Its distinguishing feature is simultaneous participation, rather than a particular communication tool. Choose it when the clinical task benefits from dialogue or observing the patient’s responses. Audio and video provide different information, so a live telephone encounter may support discussion while leaving a visually dependent assessment incomplete.

Apply it

A patient needs to discuss treatment concerns and demonstrate an instructed movement. Schedule live video so the clinician can ask follow-up questions while observing the movement and deciding whether further examination is necessary.

Common pitfall: Assuming all live encounters provide equivalent evidence overlooks the information lost without video. Real-time communication alone does not make every clinical task remotely assessable.

Getting started with telehealth · Conduct a telehealth physical exam

3.How does asynchronous care change service design?

Asynchronous care separates information submission from professional review. Examples include sending images, messages, or measurements for evaluation later. This can reduce the need for simultaneous availability, but it creates a review queue that needs ownership and clear patient expectations. Choose it when the information can safely wait for the planned review process and is sufficient for the intended decision; a submitted message is not evidence that someone has assessed it.

Apply it

A service accepts routine images for later review. Its intake instructions explain when review occurs and how to seek help for urgent concerns, while staff assign each submission to a responsible reviewer.

Common pitfall: Treating an asynchronous inbox as continuously watched creates unsafe expectations. Submission time, review time, and clinical response time are separate stages of the service.

Getting started with telehealth · Planning your telehealth workflow

4.What separates mobile health from remote patient monitoring?

Mobile health uses mobile devices or wearables to support health through functions such as reminders, education, or activity tracking. Remote patient monitoring adds transmission of patient measurements or clinical information to a provider. These categories can overlap, but a phone application alone does not establish a monitoring service. The discriminating question is whether relevant patient data enter an organized professional review and follow-up process.

Apply it

One application reminds a patient to take medication; another transmits home readings to the care team. Identify the reminder function as mobile health and the transmitted readings as part of remote monitoring.

Common pitfall: A wearable’s ability to collect numbers does not prove that clinicians receive or review them. Clarify the actual data pathway before describing a monitoring service.

Getting started with telehealth · Developing a remote patient monitoring strategy

5.How should a monitoring device match the clinical question?

Select a device by the physiological information needed for the care decision. A scale measures weight, a blood pressure monitor measures pressure, a glucose device tracks glucose, and a pulse oximeter estimates oxygen saturation. These measurements answer different questions and cannot substitute for one another. Useful selection also requires a suitable patient interface, reliable data transmission, and a plan explaining how the team will use the result.

Apply it

A clinician’s monitoring plan requires home blood pressure readings. The coordinator selects a suitable blood pressure device and transmission method, rather than substituting an activity tracker merely because the patient already owns it.

Common pitfall: Choosing the most convenient gadget can produce irrelevant data. Device ownership and connectivity matter only after the measurement matches the intended clinical purpose.

Using remote patient monitoring · Developing a remote patient monitoring strategy · Pulse Oximeter Basics | FDA

6.Why must connectivity be assessed at the patient’s location?

A successful clinic connection does not demonstrate that a patient can sustain the required encounter from home. Assess the patient’s available device, connection, bandwidth, and intended location together. Video may fail despite basic internet access, and public connectivity introduces privacy considerations. A workable alternative must still provide enough information for the clinical task; changing the connection method should trigger reconsideration of what can be assessed.

Apply it

A patient’s home connection repeatedly freezes during a visual assessment. Staff arrange a supported location with adequate connectivity or an in-person visit, because an audio connection would not supply the observation required.

Common pitfall: Recording only that a patient has internet access misses functional limitations. Connectivity should be tested against the actual platform, location, and appointment requirements.

Getting patients set up with telehealth technology · Conduct a telehealth physical exam

7.How does a practice appointment improve technical readiness?

A practice appointment tests the complete patient journey before clinical time is needed. It checks the invitation, login, browser compatibility, camera permission, microphone, sound, and the patient’s ability to use essential controls. Troubleshooting should target the observed failure, such as a blocked microphone or weak connection. Written instructions and a named help contact support later independence rather than assuming the patient will remember every setup step.

Apply it

During a rehearsal, a patient opens the visit successfully but cannot transmit sound. A coordinator checks microphone permission and repeats a short conversation, then supplies simple instructions and the service’s technical support contact.

Common pitfall: Sending a download link is not evidence of readiness. The decisive test is whether the patient can complete the required steps using their own equipment.

Getting patients set up with telehealth technology

8.Which vendor features matter for service fit?

Vendor selection should begin with the intended service, patient population, and staff workflow. Relevant features include usability, patient access, training, accessibility, record integration, and information safeguards. Evaluate whether the platform supports the actual tasks and accommodations the service requires. A feature-rich product may still be unsuitable if patients cannot enter appointments or staff must maintain disconnected records that make follow-up unreliable.

Apply it

Two platforms support video, but only one allows the clinic’s required participant support and fits its record workflow. The selection team tests those tasks with patients and staff before choosing the better-fitting platform.

Common pitfall: Selecting solely on demonstration quality or feature count overlooks operational fit. Evaluate the tasks users must complete, including entry, documentation, assistance, and follow-up.

Planning your telehealth workflow · Getting started with telehealth

9.How does equipment readiness differ from connectivity?

Connectivity moves information between locations, while equipment readiness determines whether the necessary information can be captured and presented. A functioning connection is insufficient if a camera fails, a microphone is blocked, or a monitoring device cannot transmit. Readiness checks should cover power, compatible software, essential peripherals, and operation. Equipment maintenance supports continuity, but the exact checks must reflect the devices used and the service’s planned tasks.

Apply it

The clinic’s internet works, but its examination camera has no power. Staff identify the equipment failure during a pre-session check and restore the camera before scheduling encounters that depend on its images.

Common pitfall: A successful network test does not certify every device as operational. Check capture, transmission, and display functions rather than treating connectivity as the entire system.

Getting patients set up with telehealth technology · CTTP 467 Curriculum

10.How should telehealth team responsibilities be divided?

Telehealth changes tasks across scheduling, intake, technical support, clinical assessment, documentation, and follow-up. Assign each task to a role with appropriate competence and authority, and specify how information moves between roles. Technical assistance can help a patient connect, but it does not replace clinical judgment. Clear ownership prevents a completed appointment from ending with unresolved responsibilities for patient instructions, records, referrals, or review of later information.

Apply it

A service assigns connection support to its coordinator, assessment to the clinician, and referral tracking to a designated staff member. Each handoff identifies what was completed and what the next person must do.

Common pitfall: Giving everyone general responsibility can leave no one accountable. Define ownership for individual tasks and handoffs, especially activities that continue after the video session.

Planning your telehealth workflow

11.Why does remote monitoring require more than technical support?

Remote monitoring generates continuing clinical work after devices are installed. A program needs responsibility for enrollment, education, data review, patient follow-up, and technical assistance, including a decision about coverage outside normal hours. These functions differ: repairing transmission does not interpret a concerning measurement. Staffing should match the promised service and expected data volume, with explicit escalation pathways for reviewers who cannot independently make treatment decisions.

Apply it

A vendor can repair device connections, but the clinic has not assigned clinical reviewers. Before enrollment, the clinic names reviewers, defines coverage hours, and establishes who receives findings requiring clinical decisions.

Common pitfall: A technical help desk cannot supply unassigned clinical surveillance. Patients need accurate expectations about who reviews information, when review occurs, and how concerns escalate.

Developing a remote patient monitoring strategy

12.What distinguishes fee-for-service from value-based payment?

Fee-for-service payment primarily rewards separately delivered services, whereas value-based arrangements link financial results to quality, costs, or outcomes for specified care. Telehealth is a delivery method that can operate within either arrangement. Examine what the contract rewards: additional encounters, achievement of quality measures, or accountability for spending. Lower utilization alone does not establish value if the required standards of care are not maintained.

Apply it

A team proposes adding routine calls solely to increase billable encounters. Under its quality-linked arrangement, managers instead assess whether those calls improve defined outcomes and justify their costs within the actual contract.

Common pitfall: Calling a service virtual does not make its payment value-based. Identify the incentive mechanism and quality conditions rather than inferring them from the communication modality.

Value-based Care State Medicaid Directors Letter

13.How does an episode payment shape care coordination?

An episode payment bundles a defined set of services associated with a healthcare event during a specified period. Its boundaries determine which services and costs belong to the episode. Telehealth follow-up may support coordination within that period, but a bundle does not imply that every service is separately payable. Evaluate the episode definition, benchmark, and quality measures together before deciding how additional contacts affect performance.

Apply it

A hypothetical recovery bundle includes specified follow-up services for a defined period. The team places virtual check-ins within that episode’s care plan and evaluates their contribution to quality and total episode costs.

Common pitfall: Treating every virtual contact as additional revenue ignores bundled payment boundaries. A clinically useful contact may be included within an existing episode payment.

Value-based Care State Medicaid Directors Letter

14.When do savings create a payment opportunity?

Shared savings arrangements may reward spending below a defined benchmark when quality requirements are also met. Some arrangements permit only additional earnings, while others include possible repayment or loss when performance falls short. Identify the covered population or services, the benchmark, quality conditions, and whether downside risk exists. Actual payment depends on the contract’s calculation; a spending reduction does not automatically become an equal payment to the provider.

Apply it

A hypothetical contract requires both spending below its benchmark and achievement of a quality threshold. Although the program reduces spending, it misses that threshold, so the team cannot assume it earned shared savings.

Common pitfall: Subtracting spending from a benchmark identifies a difference, not necessarily the provider’s payment. Eligibility conditions and the agreed sharing formula remain decisive.

Value-based Care State Medicaid Directors Letter

15.Why does current patient location matter for interstate practice?

In United States interstate telehealth, a patient’s current location can change the licensing pathway needed for an encounter. Verify location before the appointment rather than relying on the permanent address in the record. A clinician must have an applicable authorization for the circumstances, which may involve a full license or a qualifying alternative. Existing relationships and patient travel do not themselves establish unrestricted permission to practice across state lines.

Apply it

A patient normally seen at home joins from another state while traveling. Before routine care proceeds, staff identify that location and confirm whether the clinician has a valid pathway for that encounter.

Common pitfall: Using the address on file can conceal a jurisdiction change. Patient consent and an established relationship do not independently create interstate practice authority.

Licensing across state lines

16.Which pathways can support lawful interstate telehealth?

United States pathways can include a full state license, qualifying temporary practice provisions, reciprocity, participation in a relevant compact, or telehealth registration where offered. Each has conditions concerning the profession, participating jurisdictions, eligibility, and permitted activity. A compact streamlines practice or licensing under its own structure; it is not universal national permission. Telehealth registration may authorize remote services while restricting an office or in-person practice in that state.

Apply it

A clinician considers telehealth registration in a patient’s state. The service checks professional eligibility, the registration’s conditions, and its permitted activities before assuming it also allows opening a local in-person practice.

Common pitfall: A pathway’s name does not establish its reach. Compact membership, temporary exceptions, and registration must fit the profession, state, activity, and particular encounter.

Licensing across state lines

Care operations, documentation, and patient safetynot stated

17.How should intake establish a useful clinical starting point?

Telehealth intake should establish patient identity, the reason for the encounter, relevant symptoms and history, and available measurements when appropriate. These details help the clinician determine whether the planned encounter can address the concern. Collect information before or at the visit through a usable process, with staff assistance when needed. A completed electronic form is useful only if its contents reach the clinician and support the current assessment.

Apply it

A patient cannot complete the electronic history form. A staff member collects the same relevant information by conversation and makes it available to the clinician, rather than allowing the appointment to start without intake.

Common pitfall: Electronic completion is a method, not the clinical objective. Requiring a difficult portal process without assistance can obstruct collection of information needed for care.

Planning your telehealth workflow

18.Why must telehealth forms connect to workflow decisions?

Forms support decisions when their purpose, timing, reviewer, and destination are defined. History forms inform assessment, consent documentation records the consent process, and administrative information supports scheduling or payment tasks. Collecting everything without assigning review can produce complete-looking records but missed concerns. Design the process so clinically relevant responses reach an appropriate professional and required documentation is available at the point where the service needs it.

Apply it

An intake form includes a response requiring clinician review, but only scheduling staff see submissions. The clinic changes routing so the responsible clinician receives relevant responses before deciding whether the booked visit is appropriate.

Common pitfall: A stored form is not proof that anyone acted on it. Completion, review, and response are separate steps requiring explicit ownership.

Planning your telehealth workflow · Obtaining informed consent

19.How does record integration support continuity?

Telehealth information should fit the patient’s ongoing record and care workflow. Integration helps clinicians find the encounter, relevant measurements, and follow-up decisions without depending on an isolated platform. Operationally, assess whether the correct patient’s information arrives in the intended location and is available to the responsible team. A technically successful connection between systems does not prove that the transferred information is clinically usable or that follow-up ownership is clear.

Apply it

A monitoring interface sends readings to an archive that treating clinicians rarely open. The team tests a workflow that makes those readings available in the patient record and assigns responsibility for reviewing resulting concerns.

Common pitfall: Equating data transfer with effective integration overlooks visibility and action. Information must reach the right record and the people responsible for using it.

Planning your telehealth workflow · Developing a remote patient monitoring strategy

20.What makes telehealth consent meaningful?

Meaningful consent involves explaining what the telehealth encounter entails, addressing the patient’s rights and questions, and documenting consent through a method that meets applicable requirements. United States state requirements vary, so a signature is not a universal substitute for an informed discussion. Confirm that required documentation is received or recorded during the check-in process. The useful distinction is between a completed form and evidence of informed agreement.

Apply it

A patient signs a form but asks whether the visit will be recorded and who can attend. The clinician answers those questions and confirms understanding before proceeding, then documents the consent discussion appropriately.

Common pitfall: Treating a signature as the entire consent process misses unresolved questions. Documentation should reflect informed agreement using a method appropriate to the applicable rules.

Obtaining informed consent

21.When must an observer be discussed with the patient?

If someone is observing a telehealth encounter, tell the patient and obtain consent at the start. A person outside the camera frame can still hear sensitive information, so visibility alone does not establish who is present. Identify participants and explain their roles before disclosure occurs. Consent to receive telehealth care does not automatically resolve whether an additional observer may participate in that particular encounter.

Apply it

A clinician plans to include a trainee who is seated outside the camera’s view. Before discussing the patient’s concern, the clinician introduces the trainee, explains the role, and asks for the patient’s agreement.

Common pitfall: An unseen observer still receives patient information. General agreement to a virtual appointment does not eliminate the need to disclose and discuss observer participation.

Obtaining informed consent

22.How should privacy expectations be discussed in telebehavioral care?

Telebehavioral consent should support an understandable discussion of privacy, participation, and relevant limits on confidentiality. Ask whether the patient can speak privately and explain practical measures such as headphones and a quiet location. Also explain circumstances in which information may need to be shared under applicable requirements. A patient may connect successfully yet lack a setting where sensitive discussion is possible, making privacy preparation a care issue as well as a technical one.

Apply it

A patient joins a behavioral appointment with household members nearby and appears hesitant to speak. The clinician discusses who can hear, explores a private arrangement, and confirms how the session can proceed appropriately.

Common pitfall: Headphones reduce what others hear from the clinician but do not stop them hearing the patient. Avoid promising absolute confidentiality or assuming connection means privacy.

Obtaining informed consent for telebehavioral health

23.How should patients learn to use monitoring equipment?

Monitoring education should explain how the device works, what the patient must do, which information is collected, and how the team receives and uses it. Demonstration followed by patient practice can reveal difficulties that written instructions alone miss. Include a help contact and instructions the patient can revisit. The endpoint is successful use within the care plan, rather than merely handing over equipment or completing an education checkbox.

Apply it

After a device demonstration, a patient practises taking and sending a reading while a staff member observes. The staff member corrects a missed transmission step and provides concise instructions for later use.

Common pitfall: Agreement that instructions were clear does not demonstrate successful operation. Ask the patient to show the required actions and identify how to obtain help.

Preparing patients for remote patient monitoring

24.Why should the first monitoring transmission be confirmed?

The first transmission tests whether a measurement reaches the care team, rather than simply appearing on the patient’s device. Staff confirmation provides evidence that setup and routing worked and reassures the patient about the process. Distinguish measurement capture, transmission, receipt, and clinical review: success at one stage does not establish the others. A service should explain what receipt means and when the information is ordinarily reviewed.

Apply it

A patient reports that a device displays a completed measurement. Staff check the receiving system, discover no data arrived, and troubleshoot transmission before telling the patient that monitoring has been established successfully.

Common pitfall: A number on the device screen confirms local capture only. It does not prove transmission, correct routing, staff receipt, or clinical review.

Preparing patients for remote patient monitoring

25.How should pulse oximetry inform monitoring of chronic obstructive pulmonary disease?

Chronic obstructive pulmonary disease, or COPD, is a chronic lung condition that can cause blood oxygen levels to fall. A fingertip pulse oximeter uses light to estimate oxygen saturation, displayed as SpO2, and pulse rate. Interpret trends alongside symptoms and the patient’s care plan: some people with lung disease have lower saturation values than most healthy individuals. Poor circulation, skin pigmentation, skin temperature, and nail polish can affect accuracy. The device estimates oxygenation; it does not independently diagnose hypoxia or determine treatment.

Apply it

For teaching only, a hypothetical COPD care plan requires clinician contact after a repeat SpO2 below 92%. An otherwise comfortable patient records 91% with a cold hand. The reviewer guides a repeat using a warm, relaxed hand and a steady reading, then follows the contact rule if it remains below 92%. Serious or worsening symptoms require clinical contact without waiting for routine uploads.

Common pitfall: The hypothetical 92% parameter is not a universal COPD threshold. Do not label an unexpected result as device error without assessment, assume accuracy is identical across skin pigmentations, or treat a transmitted alert as completed follow-up.

Pulse Oximeter Basics | FDA · Developing a remote patient monitoring strategy · CTTP 467 Curriculum

26.Why must symptoms guide interpretation of oxygen readings in asthma?

Asthma is a respiratory condition that can cause oxygen levels to drop. Pulse oximetry provides an estimate of blood oxygen saturation, but the reading must be considered with breathing difficulty, worsening cough, chest tightness, and other symptoms. A reassuring displayed value does not settle whether worsening symptoms need assessment, because pulse oximeters can be inaccurate and measure only selected information. Poor circulation and skin pigmentation are among the accuracy factors. Patients should contact a healthcare provider for concerning readings or serious or worsening symptoms.

Apply it

A patient with asthma reports worsening breathing difficulty while a home device displays 97%. The reviewer assesses the symptoms and follows the clinical escalation plan rather than sending reassurance based solely on the reading. If the clinician identifies an immediate emergency, the team activates the location-specific emergency plan rather than waiting for another measurement.

Common pitfall: A value within the range typical for most healthy people does not override serious symptoms. General wellness or sporting pulse oximeters have not been evaluated by the FDA for clinical decision-making or deciding whether to seek medical intervention.

Pulse Oximeter Basics | FDA · Creating an emergency plan · CTTP 467 Curriculum

27.What does missing monitoring data actually mean?

Missing expected data indicate a break in the planned information flow, with several possible explanations. The patient may not have measured, the device may have failed, or transmission may not have reached the receiving system. Missingness is therefore an operational signal to investigate under the program’s follow-up process. It does not establish either clinical stability or deliberate nonparticipation. The assigned reviewer should clarify symptoms and technical difficulties, follow the patient’s escalation plan when concerns arise, and document the resulting action.

Apply it

A patient’s expected readings stop arriving. Staff use the program’s contact process and learn that the device no longer connects, then arrange technical support while addressing any clinical concerns identified during the conversation.

Common pitfall: Automatically labeling missing readings as nonadherence can miss device failure or a patient needing assistance. Absence of transmitted data is not a normal clinical result.

Developing a remote patient monitoring strategy · Preparing patients for remote patient monitoring

28.How should patient-assisted findings be documented?

A telehealth record should distinguish what the clinician observed from what the patient reported or measured using home equipment. Record relevant limitations, including examination components that could not be performed. This preserves the basis for later interpretation and follow-up decisions. A home reading can be useful without being represented as a clinician-performed measurement, and an unavailable examination component should not silently become a normal finding in the record.

Apply it

During video care, a patient reads a home blood pressure result aloud. The clinician documents it as a patient-obtained measurement and separately records visual observations and examination components unavailable in the remote setting.

Common pitfall: Copying a standard normal examination template can misrepresent evidence. Clearly separate observed, reported, patient-measured, and unperformed elements rather than merging them.

Conduct a telehealth physical exam

29.Which observations can inform a virtual examination?

A virtual examination draws on what the clinician can see and hear, the patient’s description, and clearly explained patient-assisted actions. Appearance, speech, body language, visible skin changes, and movement may provide useful observations when the connection and view are adequate. The clinician should deliberately gather relevant information rather than equating video presence with examination completeness. Poor sound, framing, or image quality limits the conclusions that can reasonably follow.

Apply it

A clinician needs to observe a patient’s movement but the camera shows only the face. The clinician explains a safe camera adjustment and records the resulting observations together with any remaining limits.

Common pitfall: Assuming the camera automatically captures the needed finding overlooks framing and image quality. Obtain a useful view without asking patients to perform unsafe maneuvers.

Conduct a telehealth physical exam

30.When does an examination limitation require another care setting?

A remote encounter is limited when the information needed for a decision cannot be obtained reliably through the available history, observation, and patient-assisted measurements. Recognize the specific missing information and determine whether further assessment must occur in person. The appropriate urgency depends on the clinical concern. Document the limitation and next step rather than declaring the examination complete because a scheduled video appointment has taken place.

Apply it

A clinician cannot obtain a required finding with the patient’s available equipment and video view. The clinician identifies that gap, arranges an appropriate in-person assessment, and explains why the remote encounter cannot settle the question.

Common pitfall: Continuing solely because video is available confuses access with adequacy. A reassuring conversation does not replace a necessary finding that the encounter cannot provide.

Conduct a telehealth physical exam · Planning your telehealth workflow

31.How should a telehealth encounter close the follow-up loop?

Closing a telehealth encounter includes documenting the encounter and ensuring the patient knows the plan and follow-up arrangements. Written or electronic instructions can reinforce important information discussed during the visit. Confirm how the patient will receive those instructions and allow final questions before ending. An encounter is operationally incomplete if the clinician has made a plan but the patient or responsible staff do not know what action is expected.

Apply it

At the end of a virtual examination, the clinician reviews the follow-up plan, confirms the patient can receive the electronic instructions, and allows final questions. Staff then complete the assigned scheduling task.

Common pitfall: A disconnected call does not demonstrate that the patient understood the plan. Instructions need an accessible destination and clear responsibility for any remaining actions.

Conduct a telehealth physical exam · Planning your telehealth workflow

32.Why should emergency planning use the exact current address?

Emergency response must reach the patient’s actual location, which may differ from the address in the record. Confirm the full current address at the beginning of each telehealth appointment and identify location-appropriate emergency resources. In a distant encounter, a call to emergency services from the clinician’s location should not be assumed to reach the patient’s local responders. Advance planning reduces uncertainty about where help must go.

Apply it

A patient attends from a relative’s home rather than the usual address. At the start, the clinician records that location and confirms the local emergency response information needed if the session becomes a crisis.

Common pitfall: A permanent address can be accurate yet unusable for today’s emergency. Location verification must reflect where the patient is during the encounter.

Creating an emergency plan

33.How should emergency disconnection be planned?

An emergency disconnection plan specifies who will call whom, which number or alternative channel will be used, and how local help will be activated when needed. Agree on these arrangements before a crisis interrupts communication. A dropped connection does not establish that the emergency resolved or that the patient chose to leave. The response should follow the known risk and agreed plan rather than ordinary technical troubleshooting alone.

Apply it

Before a telebehavioral appointment, the clinician confirms a callback number and explains the emergency reconnection process. If a crisis occurs and video drops, the clinician follows that process while arranging the indicated local response.

Common pitfall: Repeatedly refreshing video during a crisis can delay the planned response. Technical reconnection and emergency activation may need to proceed through coordinated, separate actions.

Creating an emergency plan

34.What role can a local support person play in an emergency?

A local support person may help check on a patient or assist the response during a crisis, particularly when the clinician is geographically distant. Identify that person and obtain appropriate authorization to share information if needed as part of advance planning. Define the role alongside local emergency resources. A support contact supplements the response; it does not establish that the person is available, clinically trained, or able to manage every emergency.

Apply it

A patient identifies a nearby relative for the emergency plan and authorizes needed contact. The clinician records how to reach that person and distinguishes their supportive role from the role of local emergency responders.

Common pitfall: Listing a contact without discussing authorization or responsibilities creates uncertainty. A nearby friend or relative cannot automatically replace the emergency services required by the situation.

Creating an emergency plan

Privacy, security, and ethical information handlingnot stated

35.When do HIPAA responsibilities apply to a telehealth arrangement?

In the United States, HIPAA responsibilities depend on the entities involved and their activities, rather than simply whether information concerns health. Covered entities and their business associates have applicable obligations for protected health information. A vendor performing services involving that information on a covered entity’s behalf may be a business associate. Determine the relationship and information flow before deciding which agreements and safeguards the telehealth arrangement requires.

Apply it

A covered clinic hires a service to maintain identifiable patient encounter information on its behalf. The clinic evaluates the service’s business associate role and applicable safeguards, instead of treating it as an ordinary consumer subscription.

Common pitfall: Neither a health-related product name nor a vendor’s marketing claim establishes the legal relationship. Examine who handles information, for whom, and for what function.

Guidance on HIPAA & Cloud Computing

36.Why does cloud storage of patient information require a business associate analysis?

A cloud provider that creates, receives, maintains, or transmits electronic protected health information on behalf of a HIPAA covered entity or business associate is itself a business associate. A compliant business associate agreement establishes permitted activities and required safeguards, but the customer must also evaluate its own use of the service. Cloud convenience does not transfer every responsibility or remove the need to understand the storage and processing arrangement.

Apply it

A clinic proposes storing encounter files with a separate cloud company. Before use, it identifies the information involved, establishes the required business associate agreement, and assesses how its staff will securely access and manage the files.

Common pitfall: Buying storage is still an information-handling relationship. A contract alone does not demonstrate that the customer’s configuration, access practices, and risk management are adequate.

Guidance on HIPAA & Cloud Computing

37.What changes when a cloud provider cannot decrypt stored information?

A cloud provider maintaining encrypted electronic protected health information on a regulated customer’s behalf remains a business associate even when it lacks the decryption key. Encryption reduces unauthorized viewing risk but does not independently ensure that data remain accurate or available. The relationship still requires applicable agreements and safeguards. Assess the provider’s actual function and the full information risk, rather than using inability to read the content as an exemption.

Apply it

A storage vendor says it needs no business associate agreement because only the clinic has the key. The clinic recognizes that maintaining the encrypted patient information still creates business associate responsibilities and addresses the agreement.

Common pitfall: No access to the key does not mean no HIPAA role. Encrypted information can still be lost, corrupted, or unavailable to authorized users.

Guidance on HIPAA & Cloud Computing

38.How do business associate and service level agreements differ?

A business associate agreement addresses the HIPAA relationship, including permitted uses, disclosures, and required protections. A service level agreement describes operational expectations such as availability, recovery, data return, and division of responsibilities. These agreements should be consistent. An attractive uptime promise does not replace a required business associate agreement, while a business associate agreement alone may leave important operational expectations insufficiently defined for safe and reliable service.

Apply it

A vendor offers a compliant business associate agreement but says nothing about retrieving records after termination. The clinic clarifies data return and continuity expectations in the service terms before relying on the platform.

Common pitfall: Treating either agreement as a complete substitute for the other leaves gaps. Legal information protections and practical service performance need compatible, explicit terms.

Guidance on HIPAA & Cloud Computing

39.How broad should a security risk analysis be?

HIPAA security risk analysis covers all electronic protected health information an organization creates, receives, maintains, or transmits. Identify where information travels and resides, including relevant devices, cloud services, interfaces, and exported files. Limiting the analysis to the central record system can leave other information exposed. The inventory provides the basis for identifying threats, weaknesses, existing protections, and corrective actions across the actual telehealth environment.

Apply it

A clinic initially reviews only its main record system. Staff then identify monitoring exports on a workstation and files in a cloud service, adding those information locations and flows to the security risk analysis.

Common pitfall: A secure central record does not establish a secure information ecosystem. Exports, endpoints, and outside services can retain protected information beyond the main application.

Guidance on Risk Analysis

40.What separates a threat from a vulnerability?

A threat is a potential source or event that can cause harm, while a vulnerability is a weakness that the threat may exploit or trigger. An attacker is a threat source; an inadequately protected account is a vulnerability. Human mistakes, power failures, and natural events can also matter. Describing the combination makes risk analysis actionable because it identifies both what could happen and which weakness a safeguard should address.

Apply it

A risk discussion names unauthorized access as a concern. The team makes the scenario specific by identifying an attacker using a shared, poorly controlled account, then selects controls that address that account weakness.

Common pitfall: Listing alarming events without identifying exploitable weaknesses produces vague findings. A useful risk statement connects a plausible threat, a vulnerability, and a consequence.

Guidance on Risk Analysis

41.How should likelihood and impact guide security priorities?

Security risk reflects both the likelihood that a threat will exploit a weakness and the impact if it does. Assess existing safeguards before judging remaining exposure, then document the rationale and corrective actions. A frequent minor problem and an uncommon severe outage may require different responses. HIPAA guidance does not impose one universal scoring method; the selected method must support a thorough, defensible assessment of the organization’s circumstances.

Apply it

A team compares an inconvenience affecting appointment reminders with a credible failure that would block access to all clinical records. It evaluates likelihood and consequences explicitly rather than ranking solely by how often each event occurs.

Common pitfall: Frequency alone understates severe consequences, while dramatic consequences alone can obscure implausible scenarios. Assess both dimensions and the protections already operating.

Guidance on Risk Analysis

42.How do access controls protect confidentiality?

Confidentiality concerns whether information is available only to authorized people and processes. Access controls support it by connecting entry to an authenticated identity and limiting what that identity can reach. In telehealth, consider staff accounts, patient sessions, shared devices, and administrative tools. Encryption supports confidentiality but does not prevent someone with an improperly shared account from viewing information through an otherwise legitimate interface.

Apply it

Several staff members use one account to access telehealth records. The clinic replaces that practice with individually controlled access appropriate to assigned work, improving both confidentiality protection and its ability to investigate access concerns.

Common pitfall: Encrypted transmission does not fix excessive or shared account access. Protect the authenticated session and its permissions as well as the movement of data.

Guidance on HIPAA & Cloud Computing · Guidance on Risk Analysis

43.Why is data integrity a patient safety concern?

Integrity protects information against improper alteration or destruction. In telehealth, an altered, corrupted, or incorrectly associated measurement can mislead clinical decisions even when nobody outside the care team sees it. Evaluate how data are entered, transferred, and maintained, including accidental errors. Protecting confidentiality alone is insufficient: the team also needs confidence that the information presented for decision-making remains the correct information for the intended patient.

Apply it

An interface displays a measurement under the wrong patient record. Staff recognize an integrity and association problem, suspend reliance on the affected information, and investigate the transfer process before using it for clinical decisions.

Common pitfall: A private but incorrect record is still unsafe. Security assessment must consider accidental modification and data corruption alongside unauthorized disclosure of patient information.

Guidance on Risk Analysis · Guidance on HIPAA & Cloud Computing

44.How does availability differ from having a backup?

Availability means authorized users can obtain needed information when required. Backups support recovery, but their existence alone does not demonstrate that records can be restored or accessed during disruption. Cloud arrangements should address service reliability, recovery, and continued access. Evaluate whether the recovery process works for the service’s needs; encrypted, confidential records that remain inaccessible can still interrupt clinical work and follow-up.

Apply it

A vendor confirms that backups exist but cannot explain restoration. The clinic asks how records would become accessible after an outage and checks the recovery arrangements before treating backup creation as sufficient continuity protection.

Common pitfall: Counting backup copies does not establish usable recovery. Availability depends on access, restoration, and service arrangements that function when ordinary systems are disrupted.

Guidance on HIPAA & Cloud Computing

45.How should cloud security responsibilities be shared?

Cloud security responsibilities depend on the service design, risk management plans, and agreements. A customer may control user authentication while a provider protects infrastructure or performs other safeguards. Document the division and confirm that both sides actually perform their tasks. Outsourcing a function does not mean every obligation moves to the vendor, and overlapping assumptions can leave essential controls unimplemented even when each organization believes the other is responsible.

Apply it

A cloud vendor expects the clinic to manage user accounts, but clinic staff assume the vendor disables former employees. The parties clarify ownership and establish a process that actually removes access when employment ends.

Common pitfall: A general assurance that security is handled hides task gaps. Assign specific responsibilities and verify performance instead of relying on assumptions about outsourcing.

Guidance on HIPAA & Cloud Computing

46.How should a multi-user kiosk separate patient sessions?

A shared telehealth kiosk creates repeated transitions between users, so the service must assess whether one patient can encounter another’s information. Applying confidentiality and risk-analysis principles means examining authenticated sessions, displayed content, locally retained information, and physical privacy. The exact safeguards depend on the kiosk’s design. A successful connection is insufficient if the next user can resume a prior session or bystanders can observe sensitive content.

Apply it

During kiosk testing, the next patient can reopen the previous patient’s screen. The team treats session separation as an unresolved confidentiality risk and changes the kiosk workflow and controls before allowing routine use.

Common pitfall: A privacy screen cannot close an active account session. Physical visibility and electronic session separation address different risks and both need assessment.

Guidance on Risk Analysis · Guidance on HIPAA & Cloud Computing · Certified Telemedicine/Telehealth Professional (CTTP)

47.When should security risk analysis be revisited?

Risk analysis is ongoing because systems, information flows, threats, and organizational responsibilities change. New technology, a security incident, important staffing changes, or altered business operations can justify reassessment. Review whether existing safeguards remain adequate and document needed corrections. The cited HIPAA guidance does not prescribe one universal review interval; a calendar review should not delay addressing a meaningful change that introduces new risk.

Apply it

A clinic adds home monitoring with a new cloud connection between annual reviews. It assesses the new information flow and responsibilities before launch, then updates safeguards rather than waiting for the next scheduled review.

Common pitfall: A completed past assessment does not cover every later configuration. Review risks when material changes occur, and confirm that identified corrective actions are implemented.

Guidance on Risk Analysis

Implementation, assessment, and emerging technologynot stated

48.How should a program choose its initial patient population?

Begin with a defined care need and a population likely to benefit from the proposed service. For monitoring, consider the condition, program goals, patient interest, ability to use equipment, connectivity, and likelihood of sustained participation. Starting with a coherent service makes workflows and evaluation more interpretable. Technology availability alone is a weak enrollment criterion because it does not establish clinical usefulness or match the patient’s preferences.

Apply it

A clinic has funds for monitoring devices and considers enrolling every portal user. It instead identifies a clinically relevant group, defines intended benefits, and assesses practical participation needs before establishing enrollment criteria.

Common pitfall: Selecting only technologically confident patients may simplify launch while excluding people who could benefit with support. Assess need and barriers rather than convenience alone.

Developing a remote patient monitoring strategy

49.How can access barriers guide service adaptation?

Access depends on more than whether an appointment is offered online. Assess connectivity, compatible equipment, comfort with technology, disability-related accommodations, and the assistance needed to participate. Adapt the pathway to the identified barrier, while preserving clinical adequacy and privacy. A patient who cannot use a portal may still participate through staff-assisted preparation or another appropriate pathway; access problems should be investigated rather than interpreted automatically as disinterest.

Apply it

Patients with visual limitations abandon a complicated entry process. The service tests accessible instructions and staff assistance with affected patients, then checks whether they can reach and complete clinically appropriate appointments.

Common pitfall: Offering the same digital process to everyone does not ensure equal access. Match support to the specific barrier and assess whether the adaptation works.

Planning your telehealth workflow · Getting patients set up with telehealth technology

50.When can caregivers improve telehealth participation?

Caregivers can assist with equipment setup, reminders, device placement, charging, and transmission when the patient needs support. Explain how the device works and what information is shared so assistance fits the monitoring plan. Participation should remain appropriate to the patient’s preferences and privacy arrangements. Caregiver availability can make a pathway workable, but it should be established rather than assumed, and the clinical team retains its assigned professional responsibilities.

Apply it

A patient wants a family member to help send monitoring readings. Staff teach both people the transmission steps, clarify what information is involved, and confirm who to contact when technical or clinical questions arise.

Common pitfall: Assuming every patient has an available helper can make the service inaccessible. Caregiver assistance also does not replace consent discussions or professional review of clinical information.

Preparing patients for remote patient monitoring · Obtaining informed consent

51.How should resistance to a telehealth change be investigated?

Resistance can reveal workflow problems, unclear responsibilities, insufficient training, or concerns about workload and patient needs. Involve the staff who will perform the work, ask which tasks are difficult, and test changes against those specific obstacles. Training is useful when knowledge is missing, but it cannot by itself fix an unassigned review queue or duplicated documentation. Effective implementation connects the proposed benefit with a workable daily process.

Apply it

Nurses oppose a monitoring launch because they expect duplicate data entry and undefined after-hours work. The implementation team maps those tasks, clarifies coverage, and revises the workflow before selecting the remaining training needs.

Common pitfall: Labeling all resistance as poor attitude misses useful operational evidence. Determine whether the underlying problem is knowledge, workflow, resources, or unresolved responsibility.

Developing a remote patient monitoring strategy · Planning your telehealth workflow

52.Why test the complete workflow before expanding?

A limited workflow test can reveal whether enrollment, setup, transmission, review, patient contact, and documentation work together. Testing only the technology misses failures between people and stages. Define what successful operation looks like and gather patient and team feedback. A pilot is most useful when it leads to specific revisions and another check of the affected process, rather than serving merely as a demonstration that devices can connect.

Apply it

A small monitoring launch shows that readings arrive but patient callbacks are not documented. The team changes the handoff and documentation process, tests it again, and expands only after that gap is addressed.

Common pitfall: A technically successful demonstration does not prove operational readiness. Include the human handoffs and follow-up actions that turn transmitted information into a functioning service.

Developing a remote patient monitoring strategy · Planning your telehealth workflow

53.What separates a process measure from an outcome measure?

A process measure describes whether a planned activity occurred, such as patients transmitting data on time. An outcome measure describes a result the program aims to influence, such as readmissions. Both are useful but answer different questions. Strong transmission performance can show that the information pathway works without proving improved health. Choose measures linked to explicit goals and interpret them together rather than substituting activity counts for the intended benefit.

Apply it

A program reports that most enrolled patients send readings on schedule. Its evaluator identifies this as process performance and separately examines the selected clinical outcome before concluding that the program achieved its health goal.

Common pitfall: More appointments or uploads demonstrate activity, not necessarily better outcomes. A well-functioning process is evidence about implementation, with clinical benefit requiring its own assessment.

Developing a remote patient monitoring strategy

54.How does the denominator change a program performance rate?

A performance rate requires a clearly defined numerator, eligible denominator, and time period. The same number of successful transmissions can produce different rates depending on whether the denominator includes all enrolled patients, only active participants, or expected transmission opportunities. Define the measure before comparing results. A rise in a rate may reflect genuine improvement, changed eligibility, or exclusion of difficult cases, so interpretation requires more than the percentage alone.

Apply it

In a hypothetical weekly measure, 36 of 45 active patients transmit on time, giving 80%. The evaluator records the active-patient denominator and avoids presenting the result as the percentage of all patients offered enrollment.

Common pitfall: Changing denominators between reporting periods can create artificial improvement. Keep eligibility and timing consistent, and explain changes before comparing percentages across groups or periods.

Developing a remote patient monitoring strategy

55.Why evaluate staff workload alongside patient participation?

A service can attract patients while generating more review, troubleshooting, and follow-up work than staff can reliably complete. Assessment should therefore examine how the workflow functions for both patients and the care team. Workload findings help determine whether staffing, responsibilities, or technology need adjustment. High participation is encouraging, but expansion is difficult to justify when the resulting information queue undermines the promised review and response process.

Apply it

Enrollment rises after a successful launch, but staff report a growing review backlog. Managers examine incoming work and available review capacity, then adjust staffing and workflow before increasing enrollment further.

Common pitfall: Celebrating adoption while ignoring unfinished work can conceal a failing service. Participation counts should be interpreted with evidence that the promised tasks are actually completed.

Developing a remote patient monitoring strategy · Planning your telehealth workflow

56.How should an AI device’s intended use guide adoption?

For a machine learning-enabled medical device, intended use identifies the medical purpose, target condition, users, population, and use environment. Compare those characteristics with the proposed local application before interpreting performance claims. Also determine the expected inputs, outputs, and influence on clinical decisions. An impressive overall result does not establish that a device fits a different patient group or that it is intended to replace professional judgment.

Apply it

A service considers using a device in a different care environment from the one described in its intended use. The team identifies the mismatch and seeks relevant suitability evidence before including it in care decisions.

Common pitfall: A broad claim that a product uses AI says little about clinical fit. Match the specific device purpose, population, inputs, and workflow to the proposed application.

Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles

57.Why do training populations and known limitations matter for AI?

A machine learning-enabled device’s performance evidence may not represent every population or input condition encountered locally. Information about training and testing data, underrepresented groups, known biases, and failure modes helps users judge applicability. Missing evidence should be recognized as a limitation, rather than converted into an assumption of equal performance. Evaluate the relevant subgroup and use conditions when deciding whether a reported result supports the intended clinical application.

Apply it

A device report summarizes strong overall performance but gives little information about a population common in the clinic. The adoption team identifies that evidence gap and examines subgroup applicability before relying on the summary.

Common pitfall: An overall accuracy figure can conceal uneven performance. Neither a large dataset nor a polished report proves adequate representation of the patients the service will treat.

Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles

58.What information helps a clinician use AI output appropriately?

Useful transparency explains what an AI-enabled device produces, how that output should affect decisions, and its relevant limitations. Users need information at the point where it supports action, rather than only in distant technical documents. When understandable information about the output’s basis is available, it can support critical assessment. The clinical question includes how people interact with the device, because safe performance depends on the human-AI team within the intended workflow.

Apply it

A device displays a risk estimate without explaining its role. The implementation team clarifies that role, makes relevant limitations visible in the workflow, and trains clinicians to integrate the output with the intended clinical assessment.

Common pitfall: A numerical output can appear authoritative without explaining its proper use. Do not infer diagnostic certainty or autonomous authority from the confidence of the display.

Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles

59.How should AI performance be monitored after implementation?

Machine learning-enabled medical devices require attention across their lifecycle, including local acceptance testing, ongoing performance monitoring, investigation of problems, and communication about updates. Performance information from initial development does not establish unchanged suitability after inputs, populations, or software change. Define how concerns reach responsible people and how new limitations are communicated. Monitoring supports detection of errors or declining performance before routine confidence becomes disconnected from actual local experience.

Apply it

After a device update, clinicians report an unfamiliar pattern of outputs. The service records and investigates the concern, reviews update information and local performance, and communicates relevant findings before assuming previous results still apply unchanged.

Common pitfall: Successful initial validation does not remove the need for later assessment. Updates and changing use conditions can make earlier assumptions insufficient for current decisions.

Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles

60.Which permissions matter for United States healthcare drone delivery?

Healthcare purpose does not itself authorize a United States drone delivery operation. For the commercial package-delivery operations described by the FAA, Part 135 operator certification, applicable airspace authorization, and other operational requirements matter. Beyond visual line of sight means flight outside the pilot’s direct visual view; it is an operating characteristic, not blanket permission. Match the proposed delivery operation to its actual authorizations rather than assuming ordinary pilot credentials cover every route.

Apply it

A clinic proposes commercial package delivery along a route beyond the pilot’s direct sight. It evaluates the operator’s applicable certification and operational authorizations for that route rather than relying solely on the healthcare purpose.

Common pitfall: Neither the term BVLOS nor a pilot credential independently authorizes a commercial delivery service. Requirements depend on the operation, its approvals, and applicable local conditions.

Package Delivery by Drone (Part 135)

What to focus on during revision

The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.

  • Distinguish synchronous care, asynchronous review, mobile health, and remote monitoring by timing, data flow, and clinical purpose.
  • Follow a monitoring result from measurement through transmission, receipt, review, escalation, and documented action; interpret COPD and asthma oxygen readings alongside symptoms and device limitations.
  • Separate patient-reported information, clinician observations, and examination components that could not be performed.
  • Use current patient location for United States licensure checks and location-specific emergency planning.
  • Distinguish meaningful consent, observer participation, and practical privacy during telebehavioral encounters.
  • Apply confidentiality, integrity, and availability to cloud services, shared kiosks, interfaces, and recovery arrangements.
  • Evaluate payment incentives, implementation barriers, meaningful measures, AI suitability, and drone operational authority.
  • Use the complete official course outline and Key Outcomes to identify additional study needs beyond this selective guide.

A practical preparation plan

1. Map the official scope

Read the GHA Institute course topics and Key Outcomes. Organize your notes under the four study groups, adding published topics beyond these 60 concepts. Keep examination logistics separate from subject knowledge.

2. Build a modality decision map

For each practice case, identify the information needed, whether interaction must be live, what equipment is required, and which limitation would require another care pathway.

3. Trace one complete monitoring workflow

Explain enrollment, device education, first transmission confirmation, review ownership, missing-data follow-up, escalation, and documentation. Assign a person or role to every handoff. For the COPD and asthma cases, explain what SpO2 estimates, what can distort it, and how symptoms change the response.

4. Rehearse safety and information decisions

Practise consent discussions, observer introductions, current-location checks, emergency disconnection plans, and accurate documentation. Then analyze one cloud service and one shared kiosk using confidentiality, integrity, and availability.

5. Evaluate a small service proposal

Choose a patient group, identify access barriers, define staffing, and select process and outcome measures with clear denominators. Check payment assumptions and the intended use of any emerging technology.

6. Use the drills diagnostically

Answer all 20 questions independently and explain why each alternative is less appropriate. Review missed mechanisms with the cited primary source, then use the flashcards to recall the decision cues without answer options.

Use your sample score as a starting point

The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.

Start the free sample

Official sources and updates

Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.