On this page:
  • Reference
  • 60.0 P2P Implementation Checklist
  • 60.1 Multi-Repo Data Blend
    • 60.1    Multi-Repo Data Blend   
    Table of Contents

    P2P Implementation Checklist

    60.0.1P2P Implementation Checklist

     

    60.0.1.1Overview

    This checklist outlines the key activities and discussions required to implement the Smile CDR Payer-to-Payer solution.

    60.0.2Responding Payer Checklist

     

    For implementations where Smile CDR software responds to Payer-to-Payer requests:

    60.0.2.0.1Data Management

    • Assess current data availability and format
    • Determine storage architecture for P2P data
    • Plan data migration if necessary

    60.0.2.0.2Registration and Security

    • Define registration workflow
    • Establish authentication mechanisms
    • Set up OIDC client definitions
    • Create Organization resources for business identity

    60.0.2.0.3Patient Matching

    • Define demographic matching criteria
    • Implement custom matching scripts
    • Test matching accuracy
    • Handle edge cases and multiple matches

    60.0.2.0.4Architecture and Operations

    • Design repository structure
    • Plan data flow between repositories
    • Configure FHIR Gateway if using multiple repos
    • Set up export orchestration

    60.0.2.0.5Consent Management

    • Configure consent filtering capabilities
    • Define sensitive data categories
    • Implement consent evaluation logic
    • Set up consent storage

    60.0.2.0.6Data Scope

    • Define data sharing boundaries
    • Implement access controls
    • Configure resource filtering
    • Validate export scope

    60.0.2.0.7External Data Handling

    • Plan MDM (Master Data Management) strategy
    • Configure EID (Enterprise Identifier) generation
    • Set up data linking mechanisms
    • Handle provenance tracking

    60.0.3Requesting Payer Checklist

     

    For implementations where Smile CDR requests Payer-to-Payer exchanges:

    60.0.3.0.1Data Management

    • Plan storage for imported data
    • Design DocumentReference storage strategy
    • Configure FHIR resource creation
    • Set up data lifecycle management

    60.0.3.0.2Member Engagement

    • Design consent capture workflows
    • Implement member portal integration
    • Set up automated request triggers
    • Plan manual request processes

    60.0.3.0.3Registration and Security

    • Create OIDC server definitions
    • Configure authentication methods
    • Manage key pairs and certificates
    • Establish Organization resources

    60.0.3.0.4Monitoring

    • Set up Task resource tracking
    • Implement status monitoring
    • Configure error alerting
    • Plan performance metrics

    60.0.3.0.5Data Retention

    • Define retention policies
    • Plan archival processes
    • Configure purge schedules
    • Implement compliance tracking

    60.0.4Prerequisites Checklist

     

    60.0.4.1System Requirements

    60.0.4.1.1Networking Configuration

    • Smile CDR Network requirements met
    • Firewall paths whitelisted for P2P traffic
    • SSL/TLS certificates configured for secure communication

    60.0.4.1.2License Key Installation

    • Premium license key obtained from Sales/Account Manager
    • License installed

    60.0.4.2Module Configuration Checklist

    60.0.4.2.1System to System Data Exchange Module

    • Module added and enabled
    • Patient identifier systems configured:
      • Reference System used by Target Patient
      • Responder Identifier System
    • Consent filtering settings configured
    • FHIR Storage module dependency added

    60.0.4.2.2FHIR Endpoint Module

    • FHIR Endpoint configured or existing one verified
    • OpenID Connect Security enabled
    • SMART_OUT_SECURITY module added as dependency

    60.0.4.2.3Persistence Module

    • FHIR endpoint URL set
    • Auto-Create Placeholder Reference Targets enabled
    • bulk_export enabled
    • Index missing search parameters enabled

    60.0.4.2.4SMART Security Modules

    • SMART Outbound Security module configured
    • Federated OAuth2/OIDC enabled if using external IdP
    • Authentication scripts created
    • Token cache configured
  • Reference
  • 60.0 P2P Implementation Checklist
  • 60.1 Multi-Repo Data Blend
    • 60.1    Multi-Repo Data Blend