Servers for con27 connectathon

NameDescriptionNotesFHIR VersionAddress
touchstone undefined
MITRE - PAS RI Server https://github.com/HL7-DaVinci/prior-auth/wiki/Connectathon-README 4.0.1 https://davinci-prior-auth.logicahealth.org/fhir/
Test: MedMorph Server MedMorph Server Test: MedMorph Server undefined
VCI Health Cards R4 $health-cards-issue operation for SMART Health Cards https://connectathon.vci.org/
MITRE Open Health Manager 4.0.1 https://ohm.healthmanager.pub.aws.mitre.org/fhir/
PCT payer (MITRE RI) https://davinci-pct-payer.logicahealth.org/
Vulcan SoA Sandbox Server Pre-loaded with Patient/Subject data for SoA Testing 4.0.1 https://api.logicahealth.org/soaconnectathon30/open/
HAPI R4 RestServer 4.0.1 http://hapi.fhir.org/baseR4/
Terminz HL7® FHIR® terminology, directory & conformance services for use in New Zealand - plus IPS testing capabilities. Can POST IPS Bundles to this Server and request them using the Patient $summary operation e.g. https://terminz.azurewebsites.net/fhir/Patient/$summary?profile=http://hl7.org/fhir/uv/ips/StructureDefinition/Bundle-uv-ips&identifier=https://standards.digital.health.nz/ns/nhi-id|NNJ9186&_format=json 4.0.1 https://terminz.azurewebsites.net/fhir/
WildFHIR R4 Server AEGISWildFHIR401 AEGIS WildFHIR Test Server supporting the HL7 FHIR R4 (v4.0.1-Official) specification. 4.0.1 https://wildfhir4.aegis.net/fhir4-0-1/
CareEvolution Protected end point, requires authentication. Anyone can self-register to get a login. SMART and SMART backend auth are both supported, or you can get a token directly at https://fhir.careevolution.com/Master.Adapter1.WebClient/GetToken. See https://fhir.careevolution.com/Master.Adapter1.WebClient/fhir/ for more details, 4.0.1 https://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-r4/
COVID IG Test 4.0.1 https://api.logicahealth.org/covidigtest/open/
Argo Subscription R5 4.5.0 https://server.subscriptions.argo.run/r5/
Argo Subscription R4 4.0.1 https://server.subscriptions.argo.run/r4/
Azuba R4 4.0.1 http://fhir-dev.azuba.com/
Da Vinci Care Gaps RI 4.0.1 http://gic-sandbox.alphora.com/cqf-ruler-r4/fhir/
Matchbox - Validation support for specific Implementation Guides - FHIR Mapping Language Support - SDC Test server for questionnaire $extract and $populate see also https://github.com/ahdis/matchbox 4.0.1 https://test.ahdis.ch/matchbox/fhir/
EMR Direct UDAP Enabled Server 4.0.1 https://stage.healthtogo.me:8181/fhir/r4/stage/
MITRE CPCDS RI STU1.1.0 + Patient Access STU 1.1.0 Version of the MITRE CPCDS RI https://github.com/carin-alliance/cpcds-server-ri/wiki/Connectathon-README Also includes PDexPatient1 with a single coverage for Patient Access API 4.0.0 http://cpcds-ri.org/cpcds-server/fhir/
MITRE CPCDS RI STU2 STU 2 Version of the MITRE CPCDS RI https://github.com/carin-alliance/cpcds-server-ri/wiki/Connectathon-README 4.0.0 http://cpcds-ri.c3ib.org/cpcds-server/fhir/
MITRE - DTR RI Server 4.0.0 https://davinci-dtr.logicahealth.org/fhir/r4/
MITRE - CRD RI Server 4.0.1 https://davinci-crd.logicahealth.org/fhir/r4/
PACIO AD HAPI FHIR JPA Server 5.0.0 FHIR R4 4.0.1 FHIR US Core 3.1.1 PACIO ADI IG v0.0.1 STU1 20210514 This server is open unsecured and unsupported as-is for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-AD-SMART/fhir/
medMorph HAPI-FHIR-JPASERVER 4.2.0 FHIR R4 4.0.1 US Core 20210628 Making EHR Data More available for Research and Public Health (MedMorph) 0.2.0 - STU 1 draft 20211208 Quality Measure STU2 for FHIR R4 20200723 MessageHeader FHIR R4 4.0.1 20191101 Server Root non-authenticated: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer/fhir/
medMorph + ECR HAPI-FHIR-JPASERVER 4.2.0; FHIR R4 4.0.1; US Core 20210628; Making EHR Data More available for Research and Public Health (MedMorph) 0.2.0 - STU 1 draft 20211208; Quality Measure STU2 for FHIR R4 20200723; MessageHeader FHIR R4 4.0.1 20191101; electronic Case Reporting (eCR) (FHIR IG) 20200129 non-authenticated Server Base: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-ecr/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-ecr/fhir/
medMorph + KitchenSink HAPI-FHIR-JPASERVER 4.2.0; FHIR R4 4.0.1; HL7 FHIR US Core Implementation Guide STU3 Release 3.1.1; MessageHeader FHIR R4 4.0.1 20191101; Bulk Data Access FHIR 4.0.1 20210416; C-CDA on FHIR 1.1.0 - (FHIR R4) STU Release 1.1 20201021; SMART Application Launch Framework Implementation Guide Release 1.0.0; HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm 1.1.0 - STU 2 Ballot 20201216; Making EHR Data More available for Research and Public Health (MedMorph) 0.2.0 - STU 1 Draft 20211208 UI at: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-kitchensink/ HAPI-FHIR Base at: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-kitchensink/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-kitchensink/fhir/
Mettles PA Solution 4.0.1 https://fhir-dev.mettles.com/interop/fhir/
MITRE - MedMorph Demo EHR Demo EHR, just in case it is needed for the MedMorph track. Developed by MITRE. HAPI-based. Supports R5 Subscription Backport, SMART Backend Authorization, $process-message operation. 4.0.0 http://ec2-3-211-58-180.compute-1.amazonaws.com:8080/fhir/
MITRE - MedMorph Demo KAR Demo Knowledge Artifact Repository, just in case it is needed for the MedMorph track. Developed by MITRE. HAPI-based. Supports R5 Subscription Backport, SMART Backend Authorization, $process-message operation. 4.0.0 http://ec2-3-211-58-180.compute-1.amazonaws.com:8081/fhir/
MITRE - MedMorph Demo PHA Demo PHA, just in case it is needed for the MedMorph track. Developed by MITRE. HAPI-based. Supports R5 Subscription Backport, SMART Backend Authorization, $process-message operation. 4.0.0 http://ec2-3-211-58-180.compute-1.amazonaws.com:8082/fhir/
CorroHealth R4 Secure 4.0.1 https://fhirsandbox2.tsysinteropsvcs.net:8100/r4/sites/123/
CorroHealth Open R4 For test patient with data, use Patient ID=1. 4.0.1 https://fhirsandbox1.tsysinteropsvcs.net:8100/r4/sites/123/
ADVault R4 4.0.1 https://qa-rr-fhir2.maxmddirect.com/
Optum UHC Hybrid of Production CARIN 1.1.0 spec with some 2.0 enhancements (Dental and Vision profiles primarily). Public Directories (Open): https://public.fhir.stage.flex-nonprod.optum.com/R4 Registration for authenticated access: https://portal.stage.flex-nonprod.optum.com/homepage Patient Access (Authenticated): https://sandbox.fhir.stage.flex-nonprod.optum.com/R4 Public Directories (Authenticated): https://fhir.stage.flex-nonprod.optum.com/R4 Auth URL: https://sandbox.authz.stage.flex-nonprod.optum.com/oauth/authorize Access Token URL: https://sandbox.authz.stage.flex-nonprod.optum.com/oauth/token Developer documentation: https://www.uhc.com/legal/interoperability-apis 4.0.1 https://sandbox.fhir.stage.flex-nonprod.optum.com/R4/
MITRE PACIO ADI RI Server MITRE Server Reference Implementation of the PACIO Advance Directive Interoperability IG Requires whitelisted client IP addresses to connect. Contact Corey Spears on Zulip to add an IP address. https://iqies-api.mitre.org/fhir/
SDOH EHR R4 Used by the Task Initiation RI at https://sdoh-exchange-ri-ehr.herokuapp.com. More info at https://github.com/FHIR/Gravity-SDOH-Exchange-RI/blob/main/README.md 4.0.1 https://api.logicahealth.org/GravitySandboxNew/open/
SDOH CP R4 Used by the Coordination Platform RI at https://sdoh-exchange-ri-cp.herokuapp.com. Also used by the Questionnaire Builder (https://formbuilder-lhcforms.herokuapp.com/) and the Questionnaire app (https://lforms-fhir-app.herokuapp.com/). More info at https://github.com/FHIR/Gravity-SDOH-Exchange-RI/blob/main/README.md 4.0.1 https://api.logicahealth.org/GravitySDOHCBRO/open/
CNSI Patient Access API (C4BB) The Patient Access API leverages CMS recommended CARIN IG for Blue Button® (C4BB) Implementation Guide (IG) STU1 in conjunction with SMART Application Launch Framework (Standalone Sequence). More information about CNSI Sandbox Environment can be found at: http://sandbox.mhbapp.com/patient-access.html Please contact Ajay Tipnis (ajay.tipnis@cns.inc.com) or Thananjayan, Nithaiyan (thananjayan.nithaiyan@cns.inc.com) to register your application. CNSI Sandbox Environment will be available during and after the Connectathon. 4.0.1 https://sb.fhir.mhbapp.com/pa/api/v1/
CNSI Provider Directory API (DaVinci PDex Plan Net) The Provider Directory API leverages CMS recommended DaVinci PDEX Plan Net Implementation Guide (IG) STU1. More information about CNSI Sandbox Environment can be found at: http://sandbox.mhbapp.com/patient-access.html. CNSI Sandbox environment will be available during and after the Connectathon. Please contact Ajay Tipnis or Thananjayan, Nithaiyan for support. 4.0.1 https://sb.fhir.mhbapp.com/pd/api/v1/
PAS FHIR X12 Converter Converts FHIR PAS Claim Bundles into X12 and back Please contact Benjamin Langley (blangley@mitre.org) for authorization and endpoint details. https://davinci-fhir-x12.logicahealth.org/
MiHIN Open Server Open access 4.0.1 https://gw.interop.community/MiHIN/open/
MITRE - Integrated Trial Matching Synthetic patient data server for the Integrated Trial Matching for Cancer Patients and Providers track. Relevant patient ids: 33111, 33064 4.0.1 https://api.logicahealth.org/IntegratedTrialMatch/open/
FEvIR A developing platform to upload and retrieve FHIR Resources using Current Build, especially for Citation, Evidence, EvidenceVariable and EvidenceReport Resources. undefined
Hausam Consulting HAPI Server Basic HAPI server with support for IPS and basic terminology services. Using Elasticsearch backend for indexes. 4.0.1 https://fhir.hausamconsulting.com/r4/
Cerner R4 - Insecure Access Cerner R4 implementation with a subset of resources targeted towards various connectathon tracks. This endpoint supports insecure access, with new authorization header being required. Notes regarding SMART Health Cards: https://github.com/joeratt/connectathon_notes/blob/may_2021-HL7-health_cards/health_cards/Cerner%20SMART%20Health%20Cards%20-%20Integration%20Notes.md 4.0.0 https://fhir-open.stagingcerner.com/beta/ec2458f2-1e24-41c8-b71b-0e701af7583d/
Cerner R4 - Patient Access Cerner R4 implementation with a subset of resources targeted towards various connectathon tracks. This endpoint supports patient access. Refer to http://fhir.cerner.com/authorization/#registration for authentication details. Notes regarding SMART Health Cards: https://github.com/joeratt/connectathon_notes/blob/may_2021-HL7-health_cards/health_cards/Cerner%20SMART%20Health%20Cards%20-%20Integration%20Notes.md 4.0.0 https://fhir-myrecord.stagingcerner.com/beta/ec2458f2-1e24-41c8-b71b-0e701af7583d/
Firely Server 4.0.1 https://server.fire.ly/r4/
MedMorph KAR ONC Argonaut FHIR MetadataONC Argonaut FHIR Server 4.0.0 http://ecr.drajer.com/medmorph-kar/fhir/
Firely Server (labs) Bleading edge version of Firely Server, including support for FHIR R5 (4.5.0) 4.5.0 https://labs.server.fire.ly/r5/
CDC - Representing Cancer Registry CDC Fhir Sever based on HAPI FHIR 5.3.0 REST Server (FHIR Server; FHIR 4.0.1/R4) The $process-message endpoint is up and running and can be found at the following endpoint: http://20.84.81.240:8081/r4/fhir/$process-message The operator relies on the following validation endpoint, which can be found at: http://20.84.81.240:8081/eicr-fhir-validator/r4/resource/validate Authentication not required, Unsecured, for testing purpose only 4.0.0 http://20.84.81.240:8081/r4/fhir/
Allscripts Sunrise R4 4.0.1 https://scmfhirconnect.open.allscripts.com/fhir-testingDevMode/
onfhir.io 4.0.1 https://hl7eu.onfhir.io/r4/
Da Vinci DEQM-GIC Reference implementation server for DEQM and gaps in care 4.0.1 https://gic-sandbox.alphora.com/cqf-ruler-r4/fhir/
MITRE CARIN BB RI MITRE CARIN Blue Button/CPCDS Reference Implementation https://github.com/carin-alliance/cpcds-server-ri/wiki/Connectathon-README 4.0.0 http://cpcds-ri.c3ib.org/cpcds-server/fhir/
MITRE PDEX Formulary RI MITRE PDEX Formulary Reference Implementation Supports Shopping and Patient Access API (Authenticated). Authentication Info: https://github.com/carin-alliance/cpcds-server-ri/wiki/Connectathon-README 4.0.0 https://davinci-drug-formulary-ri.logicahealth.org/fhir/
Smile CDR C4BB RI Reference Implementation server for Carin IG for Blue Button (version 1.1.0) Open server for testing purposes. SMART Auth supported but not required. Please contact if you would like an account. Test patients available: Patient ID =1, Patient ID =2, Patient ID =3, Patient ID =4 4.0.1 https://bcbsa-bb.smilecdr.com/
test.fhir.org See Graham Grieve for more info 4.0.1 http://test.fhir.org/r4/
UW R4 University of Washington Public Health Authority FHIR server No authentication required for both root and FHIR base URL 4.0.1 https://medmorph-pha-fhir.cirg.washington.edu/fhir/
Infor - Da Vinci PAS Accepts a $submit operation to convert FHIR to X12. Uses Oauth2 authentication. https://https://ec2-52-67-136-163.sa-east-1.compute.amazonaws.com:18080/AuthServer/token?grant_type=client_credentials&scope=openid&client_id=FhirServer&client_secret=secret 4.0.1 https://ec2-52-67-136-163.sa-east-1.compute.amazonaws.com:28080/fhir_bridge/R4/
Infor - Da Vinci Notifications A accepts a notification bundle using $process-message, stores the resources, and validates. Uses Oauth2 authentication. https://ec2-52-67-136-163.sa-east-1.compute.amazonaws.com:28081/FhirServer/R4/
1upHealth Demo Health Plan FHIR server for CMS Patient Access (CARIN BB) Please see instructions here for obtaining client ID, and notes on connecting - https://1up.health/docs/start/cms-patient-access-rule-for-developers/connectathon 4.0.1 https://api.1updemohealthplan.com/r4/
MITRE C4BB Server RI Reference FHIR server for the Consumer-Directed Payer Data Exchange Implementation Guide STU2. This server is protected and requires users to authenticate before obtaining access to protected resources. Connecting: ==================================================================================================== 1) Register your client (if not yet registered) at http://cpcds-ri.c3ib.org/cpcds-server/fhir/oauth/register/client You just need to submit your client's redirect URI and you will be assigned a client id and client secret. Note: If already registered, you can retrieve your client's id and secret at http://cpcds-ri.c3ib.org/cpcds-server/debug/Clients ==================================================================================================== 2) Authorization: The client must retrieve an access token via the SMART on FHIR Standalone Launch Sequence. Check the capability statement(http://cpcds-ri.c3ib.org/cpcds-server/fhir/metadata) or well-known smart configuration (http://cpcds-ri.c3ib.org/cpcds-server/fhir/.well-known/smart-configuration) for the authorization endpoint. When sending a GET request to the authorization endpoint you will be prompted to log in. You can use the following test user credential: {username: Patient1, password: password}. ==================================================================================================== Find more detail on the authorization workflow here: https://github.com/carin-alliance/cpcds-server-ri/wiki/Authorization-&-Launch-Sequence ==================================================================================================== Once an access token is received it must be sent in the Authorization header using the correct token_type returned by the auth server for all subsequent request. ==================================================================================================== Note: We also provide an admin token to bypass the authorization process for clients that do not support this workflow. Set the request `Authorization` header with `Bearer admin` to access all resources without authorization. 4.0.0 http://cpcds-ri.c3ib.org/cpcds-server/fhir/
MITRE DEQM Test Server https://github.com/projecttacoma/deqm-test-server 4.0.1 https://ohm.healthmanager.pub.aws.mitre.org/deqm-test-server/
Novillus Risk Adjustment Server This is the Novillus Risk Adjustment Server Password is required to access this server. 4.0.1 https://cql-poc.smilecdr.com:8081/fhir
Ontoserver 4.0.1 https://r4.ontoserver.csiro.au/fhir/
PatientCorrections This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) This is not a Secure Server. Please do not store other than TEST Data. This server is built from a number of modules of the HAPI FHIR project, which is a 100% open-source (Apache 2.0 Licensed) Java based implementation of the FHIR specification. It Includes: HAPI-FHIR-JPASERVER 4.2.0; FHIR R4 4.0.1; HL7 FHIR® US Core Implementation Guide STU3 Release 3.1.1; Electronic Long-Term Services and Supports (eLTSS) Release 1 - US Realm 20190912; Patient Corrections Implementation Guide 0.4.0 - ci-build 20210913; SMART-ON-FHIR CI 20201111 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-PatientCorrections/fhir/
UPMC Register to connect with us here: https://www.upmchealthplan.com/interop/ 4.0.1 https://api.upmchp.com/FHIR/R4/
Welld Welld is a tool for CBOs, gyms, and other non-traditional healthcare providers to manage programs. An example would be referring someone to the Diabetes Prevention Program at a YMCA. We're new to FHIR so we only have a few endpoints live: POST /Observation (Physical Activity), POST /ServiceRequest (referral to a CBO), and POST /QuestionnaireResponse (submitting a PREPARE SDOH screening). This is hooked up to a local test database which will eventually get erased. Still, please don't post any PII https://dev-josh.api.qa.mywelld.com/fhir_api/v1/
Risk Adjustment Sandbox This is a HAPI FHIR server with support for operation defined in the Da Vinci Risk Adjustment Implementation Guide. 4.0.1 https://cloud.alphora.com/sandbox/r4/ra/fhir/
Raven Raven is a proof of concept platform that provides a reference implementation and testing tools for the interoperability between case management system (CMS) and electronic death registration system (EDRS) Demo Version https://apps.hdap.gatech.edu/raven-dashboard/ for server info and access, contact Myung Choi or Michael Riley https://mortalityreporting.github.io/raven-platform/
RamSoft DicomWeb RamSoft DICOM Web Server Disabled authentication for now. https://toronto-anthony-dicom-api-webapp.azurewebsites.net/
RamSoft Ramsoft FHIR Server. Disabled authentication for now. 4.0.0 https://toronto-anthony-fhir-api-r4-webapp.azurewebsites.net/fhir/
PACIO MCC Server Root non-authenticated: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-pacio-mcc/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) ; This server provides a complete implementation of the FHIR Specification using a 100% open source software stack. This is not a Secure Server. Please do not store other than TEST Data. This server is built from a number of modules of the HAPI FHIR project, which is a 100% open-source (Apache 2.0 Licensed) Java based implementation of the FHIR specification. It Includes: HAPI-FHIR-JPASERVER 5.0.0 ; FHIR R4 4.0.1 ; FHIR US Core Implementation Guide STU4 Release 4 Published 20210628 ; MCC Profiles for MCC Careplan, Chronic Kidney Disease from IG - 20220405 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-pacio-mcc/fhir/
PACIO ELTSS Server Root non-authenticated: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-pacio-eltss/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) ; This server provides a complete implementation of the FHIR Specification using a 100% open source software stack. This is not a Secure Server. Please do not store other than TEST Data. This server is built from a number of modules of the HAPI FHIR project, which is a 100% open-source (Apache 2.0 Licensed) Java based implementation of the FHIR specification. It Includes: HAPI-FHIR-JPASERVER 5.0.0; FHIR R4 4.0.1 ; FHIR US Core Implementation Guide STU4 Release 4 Published 20210628; Electronic Long-Term Services and Supports (eLTSS) Release 1 - US Realm 20190912 fixed the //fhir in the server url 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-pacio-eltss/fhir/
PACIO ADI "MiHIN" Secured FHIR Server URL: https://gw.interop.community/MiHIN/data (Contact Corey for Access) Open FHIR Server URL: https://gw.interop.community/MiHIN/open 4.0.1 https://gw.interop.community/MiHIN/open/
Onyx "SAFHIR" SAFHIR is a Secure Architecture FHIR PaaS solution offered by Onyx Technology, LLC. Lead by our FHIR-Wiz Mark Scrimshire, Onyx has built a modular and flexible end-to-end solution for Payors and Providers to transfer, load, and serve their data in a SMART-on-FHIR-compliant Patient Access API launch. When launching against SAFHIR please follow the SMART-on-FHIR v1 Standalone Launch. http://www.hl7.org/fhir/smart-app-launch/#standalone-launch-sequence ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: B2B Flow Steps: Step 1 - Make an App with our "T31" certificate, attained from the [[currently nonexistant]] CA-trust-framewrk (get it from Mike michael.cox@onyxhealth.io) https://osidmdht31mikedcrpfunc.azurewebsites.net/api/p2p_dcrp?code=h0IFvrTeZpIciH9dPACk47aiiaP46Hpl2MEROr2S6fcrRI/X4tXIQA== Body { "software_statement": [a JWT containing claims in the body. see below for claims in your software-statement json fields to format ] } recommended software_statement claims { "client_name": "B2B-SAFHIR-Test-App-DCRPByUser", "client_uri": "https://onyxhealth.io", "redirect_uris": "http://localhost:3000/myredirectpage", "scopes": "", "logo_uri": "https://www.example.org/logo", "policy_uri": "https://www.example.org/policy", "payer_Id": "" } ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Step 2 - Use your DCRP App creds to get your "Member-Match Token" https://api-dmdh-t31.safhir.io/v1/b2b/member-match/token Body { client_id:xxxx client_secret:xxx grant_type: client_credentials payer_id: same payer_id declared in your dcrp step } ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Step 3 - Send a MemberPatient and OldCoverage to SAFHIR $member-match https://api-dmdh-t31.safhir.io/b2b/member-match/osidmdht31internalmatchfunc Body: send an email michael.cox@onyxhealth.io for example member-match input JSON, OR, use the following info in MemberPatient if you have a good member-match-input body firstname = Rueben lastname = Rolfson dob = 1963-02-08 gender = male ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Step 4 - Member-Access https://api-dmdh-t31.safhir.io/v1/b2b/member-access/token body { grant_type:client_credentials client_id: client_secret:: payer_id:: member_id: } ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Then, request resources with that bearer token at the base url: https://api-dmdh-t31.safhir.io/v1/api/pdex/ CS: https://api-dmdh-t31.safhir.io/v1/api/pdex/metadata ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: _Available Scopes___________________________ : launch/patient openid fhirUser offline_access patient/AllergyIntolerance.read patient/CarePlan.read patient/CareTeam.read patient/Condition.read patient/Coverage.read patient/Device.read patient/DiagnosticReport.read patient/DocumentReference.read patient/Encounter.read patient/ExplanationOfBenefit.read patient/Goal.read patient/Immunization.read patient/List.read patient/Location.read patient/Medication.read patient/MedicationKnowledge.read patient/MedicationRequest.read patient/Observation.read patient/Organization.read patient/Patient.read patient/Practitioner.read patient/PractitionerRole.read patient/Procedure.read patient/Provenance.read ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Please email michael.cox@onyxhealth.io for any urgent questions 4.0.1 https://api-dmdh-t31.safhir.io/v1/api/pdex/
Okta UDAP Reference A FHIR server that uses UDAP for authentication. The authorization service supports B2B, B2C, and Tiered-OAuth as a dataholder. https://securefhir.zimt.work/udap-public
TIMS (Terminology Infrastructure Management System) A HAPI server. In development for custom extensions and content. https://github.com/HOT-Ecosystem/hapi-fhir-jpaserver-starter/ 4.0.1 http://20.119.216.32:8080/fhir/
Patient Centric Solutions eLTSS HIE-Data Hub The Patient Centric Solutions server supports the eLTSS exchange for the Missouri LEAP project for the Sept connectathon. This server has participated in multiple connectathons and supports multiple IGs. It will be used for the IPS in January 2022. Reach out for connectivity. For the 2022 Jan connectathon, we are importing IPS data into this server. 4.0.1 https://data-mgr.azurewebsites.net/openMO/
Meld (Interop.Community) Publicly available FHIR server supporting FHIR DSTU2, STU3, and R4 data. Provides ~100 synthetic patients which can be used for testing. If you go to https://meld.interop.community/ you can create an account and spin up your own sandbox. This will allow you to generate new endpoints and invite other users. 4.0.1 https://gw.interop.community/connectathonr4/open/
MedPlum A server with a 'bot' which can automate a cancer pathology report submission to a registry endpoint. Requires OAuth2 workflow to connect https://app.medplum.com/
MedMorph + CancerRegistry Medmorph FHIR Server to receive using the Medmorph CancerRegistry IG It Includes: HAPI-FHIR-JPASERVER 4.2.0; FHIR R4 4.0.1; US Core 20210628; Making EHR Data More available for Research and Public Health (MedMorph) 0.2.0 - STU 1 draft 20211208; MedMorph Cancer Registry 20211209; mCODE minimal Common Oncology Data Elements STU1 20200318; Quality Measure STU2 for FHIR R4 20200723; MessageHeader FHIR R4 4.0.1 20191101; Server Root non-authenticated: https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-cancerregistry/fhir/ This server is open unsecured for connectathon testing purposes. DO NOT POST PROTECTED HEALTH INFORMATION (PHI) 4.0.1 https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-drajer-cancerregistry/fhir/
mCODE STU2 R4 Contains * FHIR R4, US Core, mCODE STU2 StructureDefinitions. * Logicahealth default FHIR examples + mCODE examples for CancerPatient, PrimaryCancerCondition, CancerStageGroup, TumorMarkerTest, CancerRelatedMedicationAdministration. 4.0.1 https://api.logicahealth.org/mcodestu2/open/
Lantana National Directory 4.0.1 https://national-directory.fast.hl7.org/fhir/
Lantana Connectathon 4.0.1 https://connectathon.lantanagroup.com/fhir/
IPS/ePI testserver 2 IPS data for ePI interaction 4.3.0 http://fhir.hl7.pt/fhir/metadata
IPS $summary server Server that only supports the $summary operation. It serves patients from the national danish test infrastructure - eg - curl -X POST 'https://gravitate-ips.gravitate.tcs.trifork.dev/fhir/Patient/$summary' -H 'Content-Type: application/json' -d '{"parameter":[{"name":"identifier","valueIdentifier":{"system":"urn:oid:1.2.208.176.1.2","value":"0101010101"}}],"resourceType":"Parameters"}' 4.0.1 https://gravitate-ips.gravitate.tcs.trifork.dev/fhir/
ICF CQF Ruler 4.0.1 https://cqf-ruler.ecqm.icfcloud.com/fhir
IBM FHIR Server - R4B Draft FHIR R4B implementation on the open source IBM FHIR Server project https://github.com/ibm/fhir/tree/r4b. Currently configured with Basic Auth: username: fhiruser password: connectathon29 Open to exposing over OAuth or even no auth as needed. 4.3.0-CIBUILD https://r4b.cluster1-blue-250babbbe4c3000e15508cd07c1d282b-0000.us-east.containers.appdomain.cloud/fhir-server/api/v4/
Humana FHIR Server Humana's FHIR Server exposes a sandbox environment for testing consumer-mediated data exchange. You can register a test client here: https://developers.humana.com/apis/registerapp. You can find info on OAuth and test member login details here: https://developers.humana.com/apis/oauth. For testing the CARIN Digital Insurance Card IG, please test with HUser00002, but please note this user will also have Coverage data that does not align to these profiles so you will need to filter using Coverage?_profile=http://hl7.org/fhir/us/insurance-card/StructureDefinition/C4DIC-Coverage 4.0.1 https://fhir.humana.com/sandbox/api/
Philips FAST hybrid exchange FAST exchange registry http://212.187.34.124:9490/api/fhir/
HAPI R5 5.0.0-snapshot1 http://hapi.fhir.org/baseR5/
TIMS (Terminology Infrastructure Management System) 2 4.0.1 http://20.119.216.32:8000/r4/
GE Server Test Server for Radiation Dose Summary IG 4.0.0 http://93.26.92.227:55000/fhir/