Community Screening Eligibility and Follow-Up Constraint Verification Dataset
- Records
- 5000
- Size
- 0.4GB
- Format
- JSON
- Provider
MOBIUSI INC- Updated
- v1.02026-11-04
This dataset organizes community medicine screening program rules, recipient information, and post-screening disposition records in JSON, alongside derived validation results for eligibility, screening pathways, and follow-up or referral deadlines. Its examples cover key checks from inclusion criteria through overall constraint assessment, supporting evaluation of a model's ability to reason across multiple rules and detect inconsistencies. It is suitable for community screening quality control, medical rule validation, and domain-specific model evaluation.
Overview
Dataset Insights
Preview
Sample Examples
Schema
Technical Specifications
| Field | Type | Description |
|---|---|---|
| file_name | string | File name |
| follow_up_record | object | Source record of screening completion, results, disposition, and follow-up or referral dates. |
| service_recipient | object | Source information about the person receiving community screening services. |
| pathway_validation | object | Derived comparison of the recorded disposition with the screening pathway specified by the program. |
| deadline_validation | object | Derived checks of follow-up or referral timing against the applicable program constraints. |
| eligibility_assessment | object | Derived assessment of whether the recipient meets the program's inclusion and exclusion criteria. |
| screening_program_rules | object | Source rules for the screening program, including eligibility criteria, pathway steps, and follow-up deadlines. |
| overall_constraint_result | object | Derived overall result combining eligibility, pathway, and timing validations. |
Trust
Compliance Statement
Authorization Type
Proprietary - Commercial AI Training License (No Redistribution)
Commercial Use
Requires exclusive subscription or authorization contract (monthly or per-invocation charging)
Privacy and Anonymization
No PII, no real company names, simulated scenarios follow industry standards
Compliance System
Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs
FAQ
Frequently Asked Questions
- What does the dataset contain?
- The JSON records include screening program rules, recipient information, follow-up and disposition records, and derived fields for eligibility assessment, pathway validation, deadline validation, and the overall constraint result.
- Which model tasks does it support?
- It supports training and evaluation for screening eligibility assessment, comparison of recorded dispositions with program pathways, follow-up or referral deadline checks, and integrated constraint verification.
- What is the format, and how should data quality be checked?
- Examples use structured JSON fields that support parsing, rule comparison, and automated evaluation. Before use, review the field definitions, data completeness, and any privacy requirements relevant to your application.
- How can I access the dataset, and what are the licensing terms?
- Refer to the product page for available download or access options, and review its stated license scope, commercial-use conditions, and data-handling requirements before use. The dataset supports model training and evaluation and is not a substitute for professional medical judgment.
Can't find the data you need?
Post a request and let data providers reach out to you.
Get this Dataset
High-quality data, ready for your next AI breakthrough.
Cite this Work
@dataset{Mobiusi2026,
title={Community Screening Eligibility and Follow-Up Constraint Verification Dataset},
author={MOBIUSI INC},
year={2026},
url={https://www.mobiusi.com/datasets/5132226c92897825c56270e2b563d871?dataset_scene_cate_type=3},
urldate={2026-10-13},
keywords={community screening dataset,screening eligibility validation,follow-up deadline checks,medical constraint reasoning,screening pathway validation,community medicine evaluation,medical JSON data,healthcare workflow validation},
version={1.0}
}Using this in research? Please cite us.