Direct Secure Messaging lets healthcare organizations send encrypted health information to a known recipient through a dedicated Direct address. It is one way a pharmacy and another care team can exchange records. The software provides the inbox, Direct carries the message, and the attachment determines whether the recipient gets a readable document or structured clinical data.
Those are separate capabilities. A pharmacy may send a PDF through Direct while submitting a structured eCare Plan through a network-specific connection. Neither route establishes that a particular prescriber receives or reviews the information. Choose the route and format the receiving team actually uses for the task.
A Direct address is different from an ordinary email address
A Direct address looks like an email address, but it belongs to a service that authenticates participants and uses digital certificates to protect the exchange. A Health Information Service Provider, or HISP, manages the security and trust functions behind that service. DirectTrust's overview explains how the encrypted exchange works.
Your pharmacy might access Direct through an existing clinical system, an HIE service or a separate HISP product. Ask your software or exchange provider whether Direct is enabled for your organization, where staff send and receive messages, and whether setup or ongoing fees apply. An ordinary email account or a feature called secure chat doesn't by itself establish Direct capability.
Pharmacies can obtain Direct addresses, but their software may not offer a usable Direct interface. NCPDP's pharmacy notification guidance identifies that limitation. If a separate inbox is required, decide who monitors it and how a received document reaches the pharmacy's clinical record before relying on it for patient follow-up.
Direct carries the record; the attachment determines what arrives
Direct is a method of sending information. A continuity of care document, or CCD, is one kind of clinical summary it can carry. Other attachments may include a readable report or a PDF, depending on what the sending and receiving systems support. Our CCD guide explains how to interpret the summary itself.
Sending a document to a known clinic is directed exchange. Querying an HIE for available outside records is a different capability. A Direct address doesn't give the pharmacy search access to the recipient's chart, and a Direct message doesn't automatically become structured data in the pharmacy's own record.
The receiving system might display an attachment, place it in a work queue, or support importing some of its data after review. DirectTrust's technical guide explains why flexible attachment formats still require agreement about how the recipient handles them. If the recipient needs an importable CCD, a scanned PDF may be readable but won't meet that requirement.
Before a regular exchange starts, ask the receiving team which document format it accepts and where the document appears. A demonstration with fictional data can show whether staff can open the attachment and associate it with the correct patient. Ask separately whether supported fields can be imported or the team will read a document.
Where fax and eCare Plans fit
A receiving office may use an established fax process for a document and phone calls for time-sensitive clarification. Direct is an alternative when both organizations have a working service and a monitored destination. A fax number, a Direct address and a clinical-platform message inbox are different endpoints; verify the one the office wants for your request.
A PDF gives the recipient a readable document. Structured data labels individual elements so compatible software can process them, subject to its mapping and review behavior. Sending the same PDF through Direct changes the transport; it does not turn the medication text into structured medication entries.
The Pharmacist eCare Plan specifications describe structured care-plan representations, including FHIR, a healthcare data standard. A product may also provide a PDF view or export. The document standard and the product's active sending connections are separate facts.
For example, Outcomes' current eCare Plan FAQ lists FHIR-based JSON, CCD and PDF formats, but says its automated sending goes only to CPESN for pharmacies in eligible programs. That describes Outcomes' implementation, not every eCare Plan product or every potential recipient. It shows why an export-format list does not tell you where a plan is actually sent.
DocStation supports eCare Plan submission to CPESN with tracking and reconciliation. That supported connection does not establish a Direct inbox or a route to an arbitrary prescriber. Our pharmacist eCare Plan overview explains the care-planning purpose; for an actual exchange, confirm the named recipient, accepted format and available connection.
If the aim is to ask a prescriber a medication question, a plan submitted to a network is not evidence that the prescriber received that question. Use the office's agreed contact route and include the relevant readable information. If a program requires structured fields, confirm that the sending product supports that specific submission.
Choose the address for the actual team and purpose
Start with the Direct address the receiving organization gives you for this work. An organization may have different addresses for an individual clinician, a location, referrals or records intake. A matching clinician name alone doesn't resolve which inbox the team uses for your request.
If you don't have the address, use your service's provider directory or ask the receiving office. DirectTrust's address-selection guidance recommends the recipient's supplied address and explains how directory descriptions can distinguish different uses. When several addresses match, confirm the location and purpose with the office rather than guessing from the address spelling.
Include enough patient identification for the recipient's approved matching process, the reason for sending the document and the response you need. Keep the request in the message itself so staff don't have to infer it from a long attachment. Agree on the team's follow-up route if the exchange needs a response within a particular time.
A delivered summary can still need a reply
Consider a fictional pharmacy consultation. The pharmacist has a patient's account of a recent medication change and an older clinic summary that differs. The clinic confirms which Direct inbox its clinical team uses for medication questions. Through the pharmacy's approved Direct service, the pharmacist sends the relevant summary with a short request: “Please clarify the intended current regimen; the patient reports a change after the attached summary was created.”
The sending system then reports successful delivery. That establishes delivery to the receiving Direct system, not that a clinician has answered the question.
The pharmacy keeps the medication question open until the appropriate clinician clarifies the plan. If prompt clarification is needed, staff use the agreed phone or other urgent-contact route rather than wait on the delivery label. Once the reply arrives, the pharmacist reviews it in the clinical context and records the resolved plan through the pharmacy's normal process.
When delivery fails or the attachment cannot be used
Read the failure message and contact the sending service's support team with the message reference. An incorrect or unavailable mailbox, a trust problem between services and a missing delivery notification require different fixes. DirectTrust's delivery guidance describes those distinctions. A timeout can leave delivery uncertain; it isn't a reason to assume either successful review or definite nonreceipt.
If the receiving office can see the message but cannot open or use the attachment, confirm its supported format and arrange a usable copy through an approved route. If the office can open the document but hasn't responded, the next step is clinical follow-up with that office, rather than troubleshooting message transport.
