Examples in JSON

Open an example in Simplifier's JSON view to inspect, copy or download it. Use definitions from the same release; see Packages and the working draft.

Type: Single resource contains one record; collection groups records for inspection; transaction contains atomic write instructions; history illustrates resource versions. Only transaction examples contain transaction requests, and their use still depends on the receiving service's supported operations.

Start with these examples

Example Type Demonstrates Open on Simplifier
Dental clinic contact Single resource finished / AMB, with a clinic Location View JSON ↗
From recall to treatment collection Two visits showing the clinical workflow and references. Tooth–surface expressions remain under review; see the anatomy proposal. View JSON ↗

DENT transaction examples

These focused examples use the DigiDOT Transaction Bundle draft. They reference an existing MPI Patient and care actors; they do not create them. Each example is an independent scenario, not a sequence to submit unchanged. The receiving DENT release must support the resource workflows shown.

Example Purpose Open on Simplifier
Create an Encounter POST one Encounter View JSON ↗
Create linked clinical records POST Encounter, Condition and Procedure using internal UUID references View JSON ↗
Update an Encounter PUT the complete existing resource with ifMatch View JSON ↗
Avoid duplicate creation POST with ifNoneExist on a stable identifier for each entry View JSON ↗
DELETE structure only DELETE with ifMatch, without payload or fullUrl. Deletion reason remains unresolved; not a complete integration template. View JSON ↗

Submit the transaction to the DENT FHIR base endpoint, not /Bundle. ifMatch uses the stored resource version; ifNoneExist reuses one matching record without updating it. Follow the profile-version policy for meta.profile. After an uncertain response, reconcile the result before resubmitting changes; conditional creation does not make mixed create/update/delete transactions safely repeatable in every state.

Older complete datasets are labelled Test-data transaction, not a DENT submission. Their Patient entries and import instructions serve a different purpose and must not be copied into a DENT submission.

Planning and appointments

Example Type Demonstrates Open on Simplifier
Declined recall offer Single resource A revoked recall plan and the patient's explicit decision; distinct from a missed appointment View JSON ↗
Planning with care responsibility collection Request, booking and contact linked to EpisodeOfCare View JSON ↗
Planning without an episode collection The same clinical links without EpisodeOfCare View JSON ↗
Fulfilled dental booking Single resource Appointment with patient, location, request and care-episode links View JSON ↗
Booking requiring endodontics Single resource Dental service category plus an optional specialty; no treating practitioner is assigned View JSON ↗
Missed specialist appointment Single resource Appointment noshow; acceptance and attendance are distinct View JSON ↗
Cancelled appointment Single resource The patient cancelled; the previously booked start and end are retained. The cancellation does not itself end a clinical request or care episode. View JSON ↗
Proposed appointment Single resource A requested booking window and duration, without confirmed start/end or participant acceptance. View JSON ↗
Waiting-list appointment Single resource A booking on the waiting list without an allocated time; participant acceptance remains needs-action in this example. View JSON ↗
Patient reference in a Bundle collection A proposed Appointment refers to the Patient through urn:uuid: without actor.type. The reference matches the Patient entry fullUrl. View JSON ↗
Referral request (ServiceRequest) Single resource One referral: requested service, patient, referrer, intended provider and clinical references View JSON ↗

Encounter examples

Example Type Demonstrates Open on Simplifier
Dental home visit Single resource finished / HH, without a Location resource for the home View JSON ↗
Video follow-up Single resource in-progress / VR, without Location or an end time View JSON ↗
Earlier health-group contact Single resource A1 applied on 12 December 2012 View JSON ↗
Later health-group contact Single resource A2 applied on 16 January 2013; the earlier contact retains A1 View JSON ↗

Dental Contact Note examples

Example Type Demonstrates Open on Simplifier
One contact note with two Conditions Single resource One Encounter, readable journal text, and links to caries and a tongue ulcer View JSON ↗
Refused deletion request Single resource Request, affected record version, justification and patient notification; separate final note without Encounter. View JSON ↗
Refused correction request Single resource The corresponding correction scenario, with the original entry retained. View JSON ↗
Record-request reference context collection Collection containing the two illustrative request notes, original clinical note and its contact, Patient and author. View JSON ↗
Minimum contact note Single resource A journal note without structured section entries View JSON ↗
Attested contact note Single resource A final note with an actual professional attestation, including time and practitioner. View JSON ↗
Amendment of the same note history Two versions with the same resource ID and business identifier: final followed by amended. This is an illustrative history response, not a transaction to submit. View JSON ↗
Separate addendum Single resource A new note with its own identifier and appends pointing to the original note identifier. View JSON ↗
Allergy and reported medication context collection A collection containing a contact note and resolved DigiDOT AllergyIntolerance and MedicationStatement entries. View JSON ↗

Examples in development and evaluation

These illustrate profiles in development and experimental content. The examples use synthetic data; implementation details remain subject to review.

Example Type Demonstrates Open on Simplifier
Financial lines and claim collection Restoration, image-count and time charge lines for the profiles in development with total fees; public-benefit and insurance claim scenarios linked to Procedure and ChargeItem. Synthetic values, not eligibility or settlement. View JSON ↗
Patient coverage single resource Experimental Coverage profile: minimal public-benefit or insurance coverage for Claim; synthetic patient and payer references. Public benefit JSON ↗ · Insurance JSON ↗

Historical examples

The older example-digidot-external-critical-context and example-digidot-complete-line-danser-transaction resources are tagged as historical. They contain supportingInfo targets outside ServiceRequest 0.6.8 and must not be used as current validation or import examples. Use the selected examples above for the current representation.

The Bundles below also contain historical local Observation coding. They remain available for understanding earlier scenarios, but are not current validation or import examples. The original measurements are preserved pending agreed mappings; changing a local code to an arbitrary SNOMED code would change the clinical meaning. Use the current two-visit scenario and the focused Observation examples instead.

The earlier planning pilot also retains its explicitly versioned 0.1.0-test health-group classification. Do not interpret its D2 as the current D2. In the older Line Danser, recall and treatment-flow examples, unsupported unversioned D2 assignments have been removed; no replacement entitlement is inferred. Current health-group examples above demonstrate confirmed assignments.