Load TXT in your browser or import PDF, scans, photos and DICOM through your personal gateway. Check the complete source before model review (6000 UTF-8 bytes).TXT는 브라우저에서, PDF·스캔·사진·DICOM은 개인 게이트웨이에서 불러옵니다. 모델 검토(UTF-8 6000바이트) 전에 전체 원문을 확인하세요.
Start with a synthetic example, a FHIR .json bundle or radiology/pathology report text. The browser demo needs no model connection.합성 예제, FHIR .json 번들 또는 영상·병리 보고서 텍스트로 시작하세요. 브라우저 데모는 모델 연결이 필요 없습니다.
DICOM image pixels, medical images and waveforms need a separate validated imaging workflow. The public Imaging page shows local-installation demonstrations.DICOM 화소, 의료영상 및 파형에는 별도로 검증된 영상 작업 흐름이 필요합니다. 공개 영상 화면은 로컬 설치 기능을 시연합니다.
See measured results, supported tasks and pending reviews before choosing a workflow or comparing models. Universal clinical accuracy is not established.작업 흐름 선택이나 모델 비교 전에 측정 결과, 지원 작업 및 검토 현황을 확인하세요. 모든 임상 작업에 대한 정확도는 입증되지 않았습니다.
⋯ More
Research preview · synthetic data onlySynthetic example cases on this public page · Hospital use after local validation and specialist rule sign-off.
Finding → rule-based review → clinician review → follow-up record
🔴Standard Care (Neglected Obligation Path)
Hypothetical delayed pathway
🟢ClinLoop AI (Early Closed-Loop Intervention)
Hypothetical timely follow-up pathway
📖
Peer-Reviewed Clinical Rationale:ASCCP 2020 Guidelines show prompt colposcopic excision of HSIL prevents invasive cervical cancer progression in >95% of cases (PMID: 32243307).
Global Health Informatics Standards Grounding
Cross-institutional interoperability via OHDSI OMOP Common Data Model v5.4 and HL7 FHIR R4 JSON resources.
Example OMOP mappingFHIR-shaped sampleExample timing rule
●OHDSI OMOP-CDM Standard Mapping
Concept ID:4180497
Standard Concept NameHigh grade squamous intraepithelial lesion of cervix on cytology
Domain IDMeasurement
Vocabulary & Concept CodeSNOMED (416952002)
LOINC Observation Code10524-7
Standardized Observation Raw Record:
●HL7 FHIR R4 Interoperability Resource
Resource Type:DiagnosticReportExample JSON · active
Deterministic rules:Each obligation is checked against an explicit rule and deadline, so the same input always gives the same result and the reason is shown. This makes errors auditable; it does not guarantee that every finding is read correctly (see the accuracy evaluation).
🛡️
Data protection: what is built and what is not
ClinLoop sends no patient data to any external AI service. Each item below is markedIn use, Optional, DemoorNot built. Nothing here has been independently audited or certified.
Not certifiedNo patient data to external AI
⚡
Privacy review example
No live de-identification or external AI transmission is configured.
● EXAMPLE
PHI 항목: 0개 탐지됨
🛡️
→
Stripped:0
Pseudonymized:0
[De-identified output will appear here in real-time as you type above]
01
Optional · hospital server only
🔒
Local language model (optional)
Optional: a local language model (for example EXAONE 3.5 or Llama 3, via Ollama) can run on the hospital's own server, inside its firewall, on a CPU or a GPU. Patient text then never leaves the hospital. This public page has no model connected.
Idea for multi-hospital research: share model updates instead of records. Not built; ClinLoop's rules need no training data.
🏥 Seoul
🏥 Busan
🏥 Daegu
⚙️ Gradients Only
NVIDIA FLAREPySyftMulti-hospital
📊Design goal: patient data stays on-premise · not implemented
03
Not built
📊
Differential Privacy (ε-DP)
Idea for published statistics: add calibrated noise so no individual can be singled out. Not built; the slider below only illustrates the idea.
Mechanism: X̃ = X + Lap(Δf/ε) where ε=0.1, Δf=sensitivity
Exact value:42.1%(re-identifies individual)
ε-DP output:42.1% ± 2.3%(population-level only)
0.1
ε = 0.1Laplace NoiseApple / Google standard
🔢Illustration only · no privacy guarantee
04
Not built
💻
Confidential Computing (TEE)
Hardware-isolated processing in a cloud (Intel SGX / AMD SEV). Not built and not needed: ClinLoop runs on the hospital's own server.
Intel SGXAzure ConfidentialAMD SEV
🔐Roadmap only · not built
05
Not built
🧬
Synthetic data for research
The public site uses hand-written synthetic patients only. Generating realistic synthetic copies of real records is not built.
Encrypted EMR SyncCTGANMDClone standard
🧬Not built · no compliance certification
06
Demo · in this browser
🔥
Identifier screening (demo)
Try the box above: it finds identifier patterns (phone, resident number, e-mail, dates) and masks them, in your browser only. Pattern matching misses identifiers it has no pattern for; do not enter real patient information.
18 PHI CategoriesKorean PIPAphi_deidentifier.py
🔥Rule-based identifier removal · not measured on real records
07
Not built
🔮
Homomorphic Encryption (HE)
Computing on encrypted data. A research field, far too slow for this use today; not planned.
Microsoft SEALIBM HElibZama.ai
🔮Not planned
08
Not in use
🏦
Pseudonymised identifiers
A pattern-based de-identification module exists in the code (phi_deidentifier.py) but nothing uses it, because no patient data is sent outside the hospital. Its output would need review before being called de-identified.
SAMPLE-01→PT-99F74B58
780312-1234567→[National ID removed]
1978-03-12→1978
SHA-256 PseudonymOn-Premise VaultPCI-DSS model
🏦Module present · not used
📋
Example activity log
Example log of actions in this browser. On a server, ClinLoop keeps an append-only audit log of every detection and clinician action.
EXAMPLEExample log started (this browser only)
Summary
In use: no patient data to external AI; role-based access; audit trail
Optional: local language model · Demo: identifier screening
Not built: 6 of the ideas above
Regulatory status
Assessment pendingNo regulatory submission made
Report reading (synthetic, blind)
Clinical accuracy unestablishedSee Validation evidence for task-specific synthetic results
Clinical outcome benefit
Not studiedNo patient outcome data exist yet
Hospital integration
HL7 FHIR R4 (read)Tested against test servers only; no hospital connected
Research Action Preview
Clinical case
Simulated state change (nothing is sent)
This changes only the browser example. It sends no orders or patient messages.
Workflow review — design only
Selected synthetic example:
Questions for the existing workflow
Does the current system link results to the follow-up actions they require?
Does it distinguish acknowledgement, scheduling and completed care?
How are responsibility and escalation recorded?
EMR features vary. ClinLoop has not been compared with a hospital’s production workflow.
🏥EHR/SMART-on-FHIR IntegrationOn a hospital server
ehr_query_encounters
Query patient visit history from hospital EHR
ehr_push_fhir_task
Push 1-click FHIR orders back to EHR
🩻PACS / DICOM Imaging IntegrationOn a hospital server
pacs_fetch_dicom_metadata
Fetch DICOM metadata from hospital PACS (CT, MRI, X-ray)
Neuro-Symbolic Bridge:This panel shows curated citation metadata and example tool messages. It does not verify guideline interpretation or establish clinical accuracy.
📱
Patient message preview (example)
Plain-language reminder drafts for the synthetic cases. In the real workflow a message never names a diagnosis or result, and is sent only after a clinician approves it.
10:425G ▮▮▮ 🔋
AJ
ClinLoop (demo)Not sent
Example message preview2026.03.20
[예시병원] 자궁경부 건강검진 정밀 추적진료 안내
EMR Diagnostic Finding
Cervical cytology HSIL
Example message preview입니다. 실제 환자에게 발송되지 않으며 임상 조언이 아닙니다.
📍 Appointment status:예약된 일정 없음
시뮬레이션 전용입니다. 예약이나 EHR 업데이트는 발생하지 않았습니다.
public demo · no patient delivery
Patient messaging is not enabled
This public demonstration does not send messages, book appointments or connect to scheduling.
Sample metadata · not sent
CommunicationRequest/COMM-REQ-0062-ASCCP
Status:Pending Patient Action
Drafting engine:CHECKING…
💡 No booking or clinical workflow changes occur when this button is clicked.
Ethics & safety charter
Design and use principles. This research preview is not authorized for clinical use; regulatory classification and independent review are pending.
Principles the software follows today
First, do no harm.ClinLoop never diagnoses, orders or treats. It shows which follow-up a result requires and whether it happened; a clinician decides and acts.
Rules, not black boxes.Every alert comes from a written rule with its guideline reference and deadline. The same record always gives the same answer.
Specialist sign-off.A rule is marked “unsigned” until a specialist approves its current version; any change to the rule needs a new sign-off.
Says when it does not know.When a record is too sparse to judge, the loop is markedneeds human reviewinstead of guessed.
People stay in charge of patients.A message to a patient never names a diagnosis or result, and is sent only after a clinician approves it.
Everything is recorded.Each action (acknowledge, defer with a coded reason, close with evidence) goes into a tamper-evident audit trail.
Patient data stays in the hospital.No patient data is sent to an external AI service. Literature searches send rule-level search terms only.
Fair to every patient.The missed-follow-up rate is shown by language, age group and sex, so a group being missed becomes visible.
What has not been shown yet
No clinical validation on real hospital data, and no outcome evidence (no effect on patient outcomes, safety events, cost or workload has been measured).
No regulatory review (MFDS / FDA). Not for use in patient care.
Accuracy so far comes from synthetic and independently written test cases (docs/ACCURACY_EVALUATION.md).
Before any clinical use
Ethics committee (IRB) approval and a registered study protocol (docs/STUDY_PROTOCOL.md).
Specialist sign-off of every rule used, at the partner hospital.
Silent (shadow) running against chart review, before any clinician sees an alert.
Independent review of results, and the applicable regulatory pathway.
Compute: what runs where
Checked on the ClinLoop server, not assumed.
Hardware
–
GPU memory
–
Rules engine
CPU · no GPU needed
CT organ measurement
–
Does ClinLoop need a GPU? No.The rules engine runs on a CPU. Optional imaging and language models have their own hardware requirements. Processing time depends on the model and hardware; this page does not measure it.
🔑
Hospital AI & Biomedical API CredentialsZero-Leakage Security
Configure external biomedical LLM fallback, NCBI/PubMed research access, and Hospital EHR FHIR tokens.
⚠️ 연결 및 자격 증명 입력 비활성화
이 프로토타입은 외부 AI, PubMed 또는 병원 EHR에 연결되지 않습니다. API 자격 증명 입력이 비활성화되어 있습니다. 실제 API 키나 환자 정보를 입력하지 마십시오.