Can the project approve a controlled acceptance-test scope for the planned CT-to-archive workflow using the documentation currently available?
Illustrative sample review
Trace every finding from source to test.
A fictional CT-to-archive review showing the evidence boundary, exact citations, open actions, acceptance checks, and decision readout.
Downloadable work product
Inspect the working files.
The workbook contains the full evidence matrix, gap register, test scenarios, source register, and formula-driven readout. The PDFs provide a concise readout and the cited synthetic excerpts.
01 · Review brief
The decision and evidence boundary.
Harbor CT 4.2, Orion Archive 7.1, and Northstar Viewer 3.6.
Store a new synthetic CT study, make it available to the viewer, and query an existing prior under the correct patient context.
Three fictional source documents and a synthetic workflow brief. PHI, credentials, endpoints, logs, production access, and real product claims are excluded.
02 · Cited comparison
Capability claims kept separate from conclusions.
Every row points to exact fictional document, version, page, and section excerpts below.
SupportedDocumented on both sides
ConditionalDepends on a stated prerequisite
UnsupportedA required capability is absent
ConflictingSources disagree
UnknownThe reviewed evidence does not establish it
IDRequirement
Documented evidence
Counterpart evidence
Evidence statusCheckSourcesST-01CT image storage
Harbor CT 4.2 documents CT Image Storage as SCU.
Orion Archive 7.1 documents CT Image Storage as SCP.
SupportedIP-AT-01HCT-4.1.1OAR-5.2.2TS-02Required transfer syntax
Explicit VR Little Endian is documented for CT storage.
Explicit VR Little Endian is documented for CT storage.
SupportedIP-AT-01HCT-4.1.1OAR-5.2.2SEC-03Secure transport profile
TLS is site-configurable; the profile and certificate owner are not named.
TLS is optional; the profile and certificate assumptions are not stated.
ConditionalIP-AT-02HCT-8.2OAR-9.4QR-04Study-level prior query
Northstar Viewer 3.6 documents Study Root C-FIND as SCU.
Orion Archive 7.1 documents Study Root C-FIND as SCP for configured viewer AEs.
ConditionalIP-AT-03NSV-3.2OAR-10.3ID-05Patient-context correction
The reviewed Harbor CT and Northstar Viewer sections do not describe correction behavior.
The reviewed Orion Archive sections do not describe merge or reconciliation behavior.
UnknownIP-DISC-04HCT-1.3NSV-1.4OAR-2.103 · Gap and action register
Evidence state and follow-up state stay separate.
A finding can remain conditional or unknown even while the action to resolve it moves from open to resolved.
Confirm the approved TLS profile, certificate ownership, and environment prerequisites.
- Workflow consequence
- Secure transport cannot be configured or accepted.
- Recommended owner
- Vendor implementation leads
- Needed by
- Before interface configuration
- Action status
- Open
Define the required patient-context correction behavior and confirm each product's role.
- Workflow consequence
- The correction workflow has no agreed pass or fail condition.
- Recommended owner
- Imaging IT and vendors
- Needed by
- Before acceptance testing
- Action status
- Open
Confirm that the viewer AE is included in the archive query scope.
- Workflow consequence
- Prior studies may not be discoverable from the viewer.
- Recommended owner
- Archive administrator
- Needed by
- Before prior-query testing
- Action status
- Open
04 · Acceptance and discovery scenarios
Observable outcomes instead of “test connectivity.”
Acceptance checks have pass/fail outcomes. Discovery checks record behavior so an unresolved requirement can be defined; they are not acceptance tests.
Prerequisite
A synthetic CT study with agreed identifiers is available. Storage endpoints and transfer syntax are configured.
Action
Send the study over the approved test association, then open it from the archive worklist.
Expected outcome
The complete study is stored once. Patient and study identifiers match. Every instance uses the agreed transfer syntax.
Evidence to capture
Association log, archive receipt record, instance count, identifier comparison
Recommended owner
Imaging integration lead
Recorded state
Test: Not run
Actual: Not recorded
Action: Open
Prerequisite
The project has approved the TLS profile and configured test certificates.
Action
Send the storage workflow over the approved secure association, then repeat with an invalid trust condition.
Expected outcome
The approved path succeeds. The invalid trust condition fails without accepting image data.
Evidence to capture
TLS negotiation evidence, success log, rejected-connection log
Recommended owner
Security and interface leads
Recorded state
Test: Not run
Actual: Not recorded
Action: Blocked
Prerequisite
A synthetic prior exists under the agreed patient context. The viewer AE is in the archive query scope.
Action
Query from the viewer and open the returned prior study.
Expected outcome
The expected study is returned once and opens with the intended patient and study context.
Evidence to capture
Query request and response, returned identifiers, viewer screenshot
Recommended owner
Viewer and archive leads
Recorded state
Test: Not run
Actual: Not recorded
Action: Blocked
Prerequisite
The project has defined a synthetic correction case, but the required product behavior is not yet agreed.
Action
Run the proposed correction workflow and record behavior in the archive and viewer.
Expected outcome
No pass or fail result is assigned. Observed behavior is captured so the project can define an acceptance criterion with the responsible owners.
Evidence to capture
Before and after identifiers, audit records, archive behavior, viewer behavior
Recommended owner
Imaging IT and vendors
Recorded state
Test: Not run
Actual: Not recorded
Action: Open
05 · Executive readout
Controlled testing is supportable. Acceptance is not.
The documented CT storage path is supportable enough to begin controlled testing after the named prerequisites are resolved. Secure transport and prior-query scope remain conditional. Patient-context correction still lacks an agreed requirement and acceptance criterion.
Documented on both sides
Needs prerequisite proof
No sample findings
No sample findings
Evidence does not establish it
Next decision
Resolve the TLS profile and viewer query scope, then run the three acceptance checks. Use the discovery check to record correction behavior and define acceptance criteria before that workflow is approved.
Format, not a finding
This sample does not record executed tests, certify interoperability, support final acceptance, or describe any real product. Real reviews are tailored to the project's approved scope and evidence boundary.
06 · Synthetic source register
Exact excerpts behind the matrix.
All document names, versions, publication dates, pages, sections, and excerpts are fictional.
Page 4 · Section 1.3 Scope
This statement describes storage, worklist, and query support. Patient merge and correction workflows are outside the scope of this document.
Does not establish patient-context correction behavior.
Page 24 · Section 4.1.1 Image Storage
The Harbor CT Application Entity initiates C-STORE for CT Image Storage using Explicit VR Little Endian when negotiated with the destination SCP.
Supports CT storage and transfer-syntax findings.
Page 42 · Section 8.2 Transport Security
TLS can be enabled for configured destinations. The selected TLS profile and certificate-authority ownership are site configuration decisions.
Makes secure transport conditional on project confirmation.
Page 8 · Section 2.1 Document Coverage
This guide covers storage, query, retrieval, security, and deployment configuration. Patient merge and reconciliation behavior is not specified.
Does not establish patient-context correction behavior.
Page 31 · Section 5.2.2 Storage Services
The Orion Archive Storage AE accepts CT Image Storage through C-STORE and supports Explicit VR Little Endian.
Supports CT storage and transfer-syntax findings.
Page 52 · Section 9.4 Secure Associations
TLS is optional for DICOM associations. Certificate provisioning, trust configuration, and the approved profile are deployment-specific.
Makes secure transport conditional on project confirmation.
Page 57 · Section 10.3 Query Services
Study Root C-FIND is available to configured viewer Application Entities included in the assigned query scope.
Makes prior query conditional on the viewer AE configuration.
Page 6 · Section 1.4 Scope
The reference describes query, retrieval, display, and launch context. Patient-context correction workflows are not described.
Does not establish patient-context correction behavior.
Page 18 · Section 3.2 Prior Study Query
The Northstar Viewer Query AE initiates Study Root C-FIND to retrieve matching prior-study records from a configured archive.
Supports the viewer role in the prior-query finding.
Have a defined project decision?
Start with the workflow, systems, versions, and uncertainty.
The first note should be non-sensitive. If the review fits, scope and document-handling boundaries are agreed before evidence is exchanged.
Discuss a review