AuroraMed v0.5.0 is a synthetic-data pilot. See exactly what's built →

Clinical care requirements

Clinical documentation and the chart

Problem-oriented chart, notes, templates, signatures, amendments.

How to read status labels: In the pilot (v0.5.0, synthetic data) Simulated in the pilot (no real external system) Designed, not yet built Open decision Not offered / no claim made Planned partner integration

C0610Does AuroraMed present a patient header/banner with identifiers, age, sex, allergies, code status, isolation and restricted flags on every chart screen?

The clinical documentation and the chart part of the specification (REQ-0401) says the system must present a patient header/banner with identifiers, age, sex, allergies, code status, isolation and restricted flags on every chart screen. The pilot covers part of this. The rest is designed, not built. Acceptance check: banner is visible on all clinical screens and print outputs.

In the pilot (v0.5.0, synthetic data)Permalink

C0611Does AuroraMed provide a chart summary/snapshot with problems, meds, allergies, vitals, recent results and care team?

How would it be tested? The specification says summary loads within the interactive budget (file 07). That is the check for REQ-0402: the system must provide a chart summary/snapshot with problems, meds, allergies, vitals, recent results and care team. The pilot covers part of this. The rest is designed, not built.

In the pilot (v0.5.0, synthetic data)Permalink

C0612Does AuroraMed manage the problem list (active/resolved/inactive) with SNOMED CT or ICD-10-CM/CIE-10 coding and verification status?

Only as a simulation: real code runs against an in-hub stand-in, not against a real outside system. For reference, REQ-0403 (a top-priority requirement, all three tiers) says the system must manage the problem list (active/resolved/inactive) with SNOMED CT or ICD-10-CM/CIE-10 coding and verification status. Check: resolving a problem requires abatement date; coded value validates against the pinned release.

Simulated in the pilot (no real external system)Permalink

C0613Does AuroraMed record medical, surgical, family and social history with coded and free-text entries?

The system must record medical, surgical, family and social history with coded and free-text entries. That is REQ-0404, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.5.0 does it. Test in the specification: family history relationship uses RoleCode; social history supports SDOH codes.

Designed, not yet builtPermalink

C0614Does AuroraMed manage allergy/intolerance lists with reaction, severity, criticality and explicit no-known-allergies assertion?

Only as a simulation: real code runs against an in-hub stand-in, not against a real outside system. REQ-0405 says the system must manage allergy/intolerance lists with reaction, severity, criticality and explicit no-known-allergies assertion. Its acceptance check: empty list is not treated as NKA; cross-sensitivity check fires on new orders.

Simulated in the pilot (no real external system)Permalink

C0615Does AuroraMed record vital signs and flowsheets with LOINC-mapped rows and UCUM units?

REQ-0406 is a top-priority requirement for all three tiers: the system must record vital signs and flowsheets with LOINC-mapped rows and UCUM units. The pilot covers part of this. The rest is designed, not built. To verify it, the specification says unit conversion preserves both original and normalized values.

In the pilot (v0.5.0, synthetic data)Permalink

C0616Does AuroraMed support clinical notes of all types in file 01 with structured sections and free text?

The clinical documentation and the chart part of the specification (REQ-0407) says the system must support clinical notes of all types in file 01 with structured sections and free text. The pilot covers part of this. The rest is designed, not built. In the pilot: Basic MVP equivalent: patient banner/summary, vitals/note/I&O entries, stay/day/hour timeline, care assignment, results view; free-text, not coded or templated. Acceptance check: each note type has a registry definition; unknown note type rejected.

In the pilot (v0.5.0, synthetic data)Permalink

C0617Does AuroraMed provide templates, smart phrases and macros with variable substitution that cannot execute code?

How would it be tested? The specification says attempt to embed script is refused. That is the check for REQ-0408: the system must provide templates, smart phrases and macros with variable substitution that cannot execute code. The pilot covers part of this. The rest is designed, not built. What v0.5.0 does today: Note templates with smart fields (patient, mrn, age, vitals, problems, allergies, meds); no executable macros by design.

In the pilot (v0.5.0, synthetic data)Permalink

C0618Does AuroraMed support voice dictation with review before filing; audio is not retained beyond policy?

No. The specification describes it, but the pilot does not include it. For reference, REQ-0409 (a medium-priority requirement, all three tiers) says the system must support voice dictation with review before filing; audio is not retained beyond policy. Check: dictated text is filed only after user acceptance.

Designed, not yet builtPermalink

C0619Does AuroraMed optionally support ambient AI documentation as draft notes under section AI?

The system must optionally support ambient AI documentation as draft notes under section AI. That is REQ-0410, a lower-priority requirement for the medium and large tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: draft is labeled AI and cannot be filed without signature.

Designed, not yet builtPermalink

C0620Does AuroraMed support copy-forward with visible change highlighting and provenance?

Designed, not built: there is no code for this in the pilot. REQ-0411 says the system must support copy-forward with visible change highlighting and provenance. Its acceptance check: copied text shows original source and date.

Designed, not yet builtPermalink

C0621Does AuroraMed support note signing, cosigning, attestation and teaching-physician statements?

REQ-0412 is a top-priority requirement for all three tiers: the system must support note signing, cosigning, attestation and teaching-physician statements. The pilot covers part of this. The rest is designed, not built. What v0.5.0 does today: Sign, cosign and attestation for trainee/APP notes. To verify it, the specification says trainee note remains pending until attending attestation when policy requires.

In the pilot (v0.5.0, synthetic data)Permalink

C0622Does AuroraMed support addenda, amendments and entered-in-error marking without deleting original content?

The clinical documentation and the chart part of the specification (REQ-0413) says the system must support addenda, amendments and entered-in-error marking without deleting original content. The pilot covers part of this. The rest is designed, not built. Pilot detail: Addenda that never replace the original. Acceptance check: original text remains retrievable by HIM with audit.

In the pilot (v0.5.0, synthetic data)Permalink

C0623Does AuroraMed support late entries with both event time and entry time displayed?

How would it be tested? The specification says late entry banner shown. That is the check for REQ-0414: the system must support late entries with both event time and entry time displayed. The pilot covers part of this. The rest is designed, not built. Where the code stands: Late entry with event time and entry time.

In the pilot (v0.5.0, synthetic data)Permalink

C0624Does AuroraMed capture structured data through discrete forms and questionnaires (FHIR Questionnaire/SDC)?

Designed, not built: there is no code for this in the pilot. For reference, REQ-0415 (a top-priority requirement, all three tiers) says the system must capture structured data through discrete forms and questionnaires (FHIR Questionnaire/SDC). Check: form response validates against form version.

Designed, not yet builtPermalink

C0625Does AuroraMed provide document management: scanning, indexing, OCR, categories, encounter links and fax intake?

The system must provide document management: scanning, indexing, OCR, categories, encounter links and fax intake. That is REQ-0416, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.5.0 does it. Test in the specification: scanned document is virus/CDR scanned and indexed before filing.

Designed, not yet builtPermalink

C0626Does AuroraMed capture clinical photographs and wound images with annotation, measurement scale and consent?

No. The specification describes it, but the pilot does not include it. REQ-0417 says the system must capture clinical photographs and wound images with annotation, measurement scale and consent. Its acceptance check: image stored with EXIF removed and consent flag.

Designed, not yet builtPermalink

C0627Does AuroraMed provide body diagrams with vector annotations?

REQ-0418 is a medium-priority requirement for the medium and large tiers: the system must provide body diagrams with vector annotations. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says marks remain vector data.

Designed, not yet builtPermalink

C0628Does AuroraMed provide validated clinical calculators with versioned formulas?

The clinical documentation and the chart part of the specification (REQ-0419) says the system must provide validated clinical calculators with versioned formulas. The pilot covers part of this. The rest is designed, not built. In the pilot: BMI, BSA (Mosteller), eGFR, NEWS2 calculators with versioned formulas. Acceptance check: formula version is recorded with result.

In the pilot (v0.5.0, synthetic data)Permalink

C0629Does AuroraMed provide a clinical inbox with pooled and delegated queues for results, messages, refill requests and referrals; every item has an owner?

How would it be tested? The specification says unowned items escalate after the configured interval. That is the check for REQ-0420: the system must provide a clinical inbox with pooled and delegated queues for results, messages, refill requests and referrals; every item has an owner. The pilot covers part of this. The rest is designed, not built. What v0.5.0 does today: Inbox with delegation and shared pools; tasks.

In the pilot (v0.5.0, synthetic data)Permalink

C0630Does AuroraMed generate result-notification letters and templates?

No. The specification describes it, but the pilot does not include it. For reference, REQ-0421 (a high-priority requirement, all three tiers) says the system must generate result-notification letters and templates. Check: letter uses patient language and release rules.

Designed, not yet builtPermalink

C0631Does AuroraMed support letters, forms and correspondence templates and FMLA/disability forms?

The system must support letters, forms and correspondence templates and FMLA/disability forms. That is REQ-0422, a high-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: template variables fill from chart.

Designed, not yet builtPermalink

C0632Does AuroraMed generate and consume C-CDA documents and represent notes as FHIR DocumentReference/Composition?

Designed, not built: there is no code for this in the pilot. REQ-0423 says the system must generate and consume C-CDA documents and represent notes as FHIR DocumentReference/Composition. Its acceptance check: c-CDA passes scorecard validation.

Designed, not yet builtPermalink

C0633Does AuroraMed support Open Notes / Cures Act sharing with exceptions and documented reasons?

REQ-0424 is a top-priority requirement for all three tiers: the system must support Open Notes / Cures Act sharing with exceptions and documented reasons. This is on the design side of the line. Nothing in v0.5.0 does it. To verify it, the specification says blocked note shows exception code to privacy staff.

Designed, not yet builtPermalink

C0634Does AuroraMed segment psychotherapy notes and 42 CFR Part 2 records into separate compartments?

The clinical documentation and the chart part of the specification (REQ-0425) says the system must segment psychotherapy notes and 42 CFR Part 2 records into separate compartments. No. The specification describes it, but the pilot does not include it. Acceptance check: standard chart views omit them; access needs purpose.

Designed, not yet builtPermalink

C0635Does AuroraMed document interpreter use?

How would it be tested? The specification says interpreter fields required when flag is set. That is the check for REQ-0426: the system must document interpreter use. Not yet. It is designed in the specification and not built in the pilot.

Designed, not yet builtPermalink

C0636Does AuroraMed support clinical coding of encounters (ICD-10-CM, CPT/HCPCS, CIE-10 and country equivalents) with encoder integration?

Designed, not built: there is no code for this in the pilot. For reference, REQ-0427 (a top-priority requirement, all three tiers) says the system must support clinical coding of encounters (ICD-10-CM, CPT/HCPCS, CIE-10 and country equivalents) with encoder integration. Check: coded claim validates before release.

Designed, not yet builtPermalink

C0637Does AuroraMed provide a longitudinal timeline view across encounters and external sources?

The system must provide a longitudinal timeline view across encounters and external sources. That is REQ-0428, a high-priority requirement for the medium and large tiers. The pilot covers part of this. The rest is designed, not built. Test in the specification: external items are visually distinct.

In the pilot (v0.5.0, synthetic data)Permalink

C0638Does AuroraMed support external/outside record reconciliation and incorporation?

No. The specification describes it, but the pilot does not include it. REQ-0429 says the system must support external/outside record reconciliation and incorporation. Its acceptance check: reconciliation never overwrites local data without user acceptance.

Designed, not yet builtPermalink

C0639Does AuroraMed provide assessments and scores (pain, falls, pressure injury, nutrition) with versioned instruments?

REQ-0430 is a top-priority requirement for all three tiers: the system must provide assessments and scores (pain, falls, pressure injury, nutrition) with versioned instruments. The pilot covers part of this. The rest is designed, not built. Where the code stands: Pain scales and NEWS2 only (no falls/pressure injury/nutrition). To verify it, the specification says score range checks pass.

In the pilot (v0.5.0, synthetic data)Permalink

C0640Does AuroraMed provide care team management and patient-provider relationships that drive access policy?

The clinical documentation and the chart part of the specification (REQ-0431) says the system must provide care team management and patient-provider relationships that drive access policy. The pilot covers part of this. The rest is designed, not built. Acceptance check: care-team change updates access within seconds.

In the pilot (v0.5.0, synthetic data)Permalink

C0641Does AuroraMed provide patient lists with minimum-necessary query enforcement?

How would it be tested? The specification says lists exceeding role limits are truncated and audited. That is the check for REQ-0432: the system must provide patient lists with minimum-necessary query enforcement. The pilot covers part of this. The rest is designed, not built.

In the pilot (v0.5.0, synthetic data)Permalink

C0642Does AuroraMed provide rounding, handoff and sign-out tools?

No. The specification describes it, but the pilot does not include it. For reference, REQ-0433 (a high-priority requirement, the medium and large tiers) says the system must provide rounding, handoff and sign-out tools. Check: handoff report prints and displays.

Designed, not yet builtPermalink

C0643Does AuroraMed provide pathways/protocols and order sets under clinical governance?

The system must provide pathways/protocols and order sets under clinical governance. That is REQ-0434, a high-priority requirement for the medium and large tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: order sets show version and owner.

Designed, not yet builtPermalink

C0644Does AuroraMed provide CDI query and response workflows?

Designed, not built: there is no code for this in the pilot. REQ-0435 says the system must provide CDI query and response workflows. Its acceptance check: query wording follows non-leading policy.

Designed, not yet builtPermalink

C0645Does AuroraMed support digital signature with ICP-Brasil certificates where the profile requires?

REQ-0436 is a high-priority requirement for all three tiers: the system must support digital signature with ICP-Brasil certificates where the profile requires. This is on the design side of the line. Nothing in v0.5.0 does it. To verify it, the specification says signed document verifies against the trust chain.

Designed, not yet builtPermalink

C0646Does AuroraMed provide patient education library integration with language and reading-level metadata?

The clinical documentation and the chart part of the specification (REQ-0437) says the system must provide patient education library integration with language and reading-level metadata. No. The specification describes it, but the pilot does not include it. Acceptance check: delivered education recorded with version.

Designed, not yet builtPermalink
See the synthetic-data demo first.Request a demo