The portal includes role-aware sign-in, permission-controlled navigation, and seeded demonstration accounts for local testing.

Key capabilities:

• Cookie-based portal authentication.
• Permission-filtered sidebar navigation.
• Seeded roles such as Platform Administrator, Validation Analyst, Clinical Reviewer, Terminology Manager, and Interop Operator.
• Audit-first workflow design for clinical and administrative actions.

It summarizes:

• Generated document volume.
• Blocking validation issues.
• Active patient records.
• Pending exports.
• Inbound imports and validation failures.
• Reconciliation workload.
• Canonical readiness and blocked backfill items.
• Correction audit volume.
• Direct messaging and FHIR conversion activity.

Supported generation workflows include:

• Continuity of Care Document.
• Referral Note.
• Transition of Care.
• Care Plan.
• Discharge Summary.
• History and Physical.
• Unstructured Document.

Generated documents include metadata, patient linkage, version history, XML output, narrative output, validation operations, and export actions.

• MU3 styled XML view.
• Raw XML view with search.
• Printable clinical HTML.
• Self-contained export package previews.
• Document print summary with included section badges.

• Raw C-CDA XML.
• Rendering XSLT support.
• Self-contained MU3 HTML preview.
• index.html entry point for quick review.

Current validation layers include:

• XML well-formedness checks.
• CDA XSD schema validation.
• C-CDA Schematron conformance validation.
• Vocabulary, datatype, template, section, header, and narrative issues surfaced by XSD or Schematron.
• Optional remote ONC SITE-compatible validation when configured.
• Optional local SITE-style validator adapter when configured.

Validation entry points:

• Validation Center: run or re-run validation for stored generated documents.
• Validation Details: inspect findings by stage, severity, location, and conformance ID.
• Validate Pasted XML: validate arbitrary XML without importing or saving it.
• Import Upload: test inbound source-system intake validation.

Import validation includes:

• Source system/profile checks.
• Source type and transport type checks.
• File extension policy checks.
• XML well-formedness.
• ClinicalDocument root and namespace checks.
• Document type code validation.
• Patient identity checks.
• Trusted OID and assigning authority checks.
• Supported clinical section checks.

The workspace supports:

• Session summary and matched-patient context.
• Candidate section comparison.
• Incoming vs existing clinical data review.
• Accept, merge, and reject decisions.
• Bulk accept, merge, and reject operations.
• Session closing.
• Generating a CCD from a completed reconciliation session.

It also identifies imports that cannot be backfilled because they failed validation or were rejected, keeping unsafe data out of downstream canonical records.

It includes:

• Patient search by MRN, name, or identifier.
• PHI correction mode.
• Field-level before/after correction trail.
• Correction reason and audit history.
• Clinical section correction support.
• Warnings for changes that affect generated C-CDA documents and patient matching.

Profiles define:

• Source system name.
• Source type.
• Active/inactive status.
• Expected transport type.
• Trusted OID roots.
• Assigning authority names.
• Allowed document type codes.
• Allowed file extensions.
• Validation policy.
• Contact and ownership metadata.

Search fields include:

• Global text search.
• Event type.
• Entity name.
• Entity ID.
• IP address.
• Date range.
• Result limit.

• User administration.
• Role catalog.
• Permission catalog.
• Permission matrix by role.
• Dynamic sidebar filtering based on granted permissions.
• Platform roles for administration, validation, clinical review, terminology, and interoperability operations.

• System behavior.
• Validation assets.
• Terminology endpoints.
• Exchange defaults.
• Direct messaging.
• FHIR gateway settings.

• Direct inbox.
• Direct sent messages.
• Direct compose.
• Provider directory search.
• C-CDA-to-FHIR conversion jobs.
• FHIR conversion result review.

• .NET 8
• C# 12
• ASP.NET Core Razor Pages
• ASP.NET Core Web API
• Entity Framework Core 8
• SQL Server / SQL Server Express / SQL Server LocalDB-compatible configuration
• Bootstrap 5
• Font Awesome
• DataTables
• Chart.js
• xUnit
• Swashbuckle/OpenAPI
• Saxon HE for Schematron execution
• HL7 CDA XSD and C-CDA Schematron validation assets

• Health and dashboard summary.
• Document generation.
• Document retrieval.
• XML and narrative access.
• Validation pipeline operations.
• Terminology cache, resolution, unmapped review, manual maps, and value sets.
• C-CDA import.
• Reconciliation sessions and decisions.
• Direct messaging.
• FHIR conversion.
• Audit logs and background jobs.
• Users, roles, permissions, and role permission assignments.

Swagger is available at /swagger when src/Api is running.

• .NET 8 SDK
• SQL Server, SQL Server Express, or SQL Server LocalDB
• PowerShell
• Java runtime for Schematron validation through Saxon HE
• Optional: real HL7 validation assets under tools/validation