Built to work alongside the systems you already use.

Where we sit in the flow

1. 1. Person or family looking for help
2. 2. Patrick's Path: plain-language navigation
3. 3. Existing systems: 988, Rapid Response, NH Care Connections, hospitals
4. 4. Follow-up and community resources

The warm handoff: sequential steps, not competing tools

Patrick's Path is independent and not affiliated with or endorsed by NH DHHS, 988, NH Care Connections or Unite Us. Names are used only to describe how our navigation fits with them.

Potential integration & partner access options

Patrick's Path™ is designed to work alongside existing healthcare, behavioral-health, government, and community systems. During a pilot, participating organizations can explore secure authentication, resource sharing, referrals, care-navigation workflows, and data-exchange options appropriate to their existing technology environment.

1. Healthcare-specific access platforms

2. General enterprise identity providers

3. Healthcare, payer, network & EHR portals

EHR & data integration

Patrick's Path™ is not currently presented as a plug-and-play EHR application. Connecting Patrick's Path™ with systems such as Epic, Oracle Health/Cerner, behavioral-health EHRs, health information exchanges, or other proprietary systems would require appropriate technical configuration and partner approval.

Depending on the participating organization's capabilities, potential integration methods could include APIs, FHIR, SAML, OpenID Connect, secure data feeds, or other supported interoperability standards. Potential use cases could include:

• Crisis referrals
• Resource availability
• Care-navigation information
• Crisis-intake handoffs
• Appropriate community-resource information
• Other authorized data exchanges

Any exchange of protected health information would require appropriate authorization, security controls, contractual agreements, and compliance processes.

4. Streamlined partner access

Organizations may be able to provide Patrick's Path™ through an existing provider, county, health-system, or partner portal where technically and contractually supported. The goal is to reduce unnecessary screen switching and make crisis-navigation resources easier for authorized staff to access. Integration would be configured individually with each participating organization.

5. Community resource sharing

Patrick's Path™ can help identify local resources that may be difficult to find through larger healthcare networks. Examples may include:

• Food pantries
• Community organizations
• Peer-support programs
• Recovery resources
• Transportation resources
• Housing resources
• Faith-based community resources
• Local crisis-support services

Where appropriate, participating coordinators could share verified community resources with individuals seeking assistance.

6. Two-minute implementation training

Instead of lengthy mandatory training sessions, Patrick Dowling's training services can provide short, role-specific micro-learning lessons designed to help staff understand the Patrick's Path™ workflow. A sandbox demonstration can allow participating staff to explore the platform before a potential launch.

Integration expectations

Required API documentation & national exchange standards

For a proposed integration, the vendor must support open, well-documented Application Programming Interfaces (APIs) and comply with the applicable national data exchange standards—for example, HL7 and FHIR for healthcare data, or NIEM for public safety data—to support interoperability with legacy Computer-Aided Dispatch (CAD) and Electronic Health Record (EHR) systems.

This is a partner integration requirement, not a claim that Patrick's Path™ currently provides these APIs, has verified HL7/FHIR or NIEM conformance, or connects to CAD, EHR, 911, or 988 systems. Each proposed connection requires documented API versions, supported exchange profiles, access controls, partner approval, and compatibility testing. Seamless integration cannot be guaranteed across legacy systems. The current network does not collect patient or health information and cannot receive emergency calls or dispatch help.

Security & privacy

Patrick's Path™ is designed with privacy, security, and minimum-necessary access in mind. Any integration involving protected health information would be subject to appropriate security assessment, contractual requirements, access controls, and applicable healthcare privacy requirements.

Patrick's Path™ does not claim HIPAA compliance, certification, or a Business Associate Agreement with any organization unless specifically established through the appropriate legal and security process.

Intellectual property ownership

Patrick's Path™ and all work product created for the platform — including software code, designs, text, graphics, documentation, and derivative works — are owned by Patrick Dowling Speaker LLC, a New Hampshire limited liability company that owns and operates Patrick's Path™ and Patrickspath.com.

These statements summarize the approach; the operative terms are those in the signed agreement between the parties. Agencies should have their own legal counsel review any agreement before signing.

Known challenges we plan for

Software only helps if people use it. These are the two biggest hurdles to working well at city scale, and how a pilot addresses them.

Current status

These capabilities require technical evaluation, security review, agreements, and participation from the relevant organizations.

Explore a pilot

Patrick's Path™ is seeking healthcare organizations, behavioral-health organizations, crisis-response providers, technology companies, payers, government agencies, and community organizations interested in exploring pilot opportunities.