AI Transparency on FHIR
1.0.0-current - STU1 Ballot International flag

AI Transparency on FHIR, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 1.0.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/aitransparency-ig/ and changes regularly. See the Directory of published versions

Example Provenance: Provenance for AI created Patient resource

Page standards status: Informative

Profile: AI Provenance

Provenance for Jane Doe (official) Female, DoB: 1950-11-15 ( Medical Record Number: MRN123456789 (use: usual))

Summary

Occurrence2025-06-18 00:00:00+0000
Recorded2025-06-18 00:00:00+0000
Policyhttp://example.org/policies/ai-authorized-patient-generation
Reason
  • healthcare operations
  • Artificial Intelligence asserted

Agents

TypeRolewho
Verifierhttp://server.example.org/fhir/Practitioner/pract
AuthorAll kinds of Artificial IntelligenceDevice: extension = Large Language Models,->DocumentReference: identifier = https://github.com/huggingface/huggingface_hub/tree/main/tests/fixtures/cards#sample_datasetcard_simple.md; status = current; type = AI Model-Card; category = Markdown Format; identifier = http://example.org/ehr/client-ids#goodhealth; manufacturer = Acme Devices, Inc; type = All kinds of Artificial Intelligence; contact = http://example.org

Entities

RoleWhatAgents
Derivation​DocumentReference: status = current; type = AI Input Prompt; description = System Prompt You are a healthcare data specialist that converts natural language patient information into valid FHIR Patient resources. Your task is to extract relevant patient demographics and create a well-formed FHIR Patient resource that is fully conformant with FHIR US Core 6.1.0 specifications. Requirements: - Generate valid JSON that conforms to FHIR R4 Patient resource structure - Ensure compliance with US Core Patient Profile (US Core 6.1.0) - Include all required US Core elements when data is available - Use appropriate FHIR data types and value sets - Generate a unique resource ID using UUID format - Apply proper FHIR coding systems and terminologies - Handle missing data appropriately (omit optional fields when data unavailable) - Use standard US address formatting - Apply proper date formatting (YYYY-MM-DD) - Include appropriate extensions when necessary for US Core compliance US Core 6.1.0 Patient Profile Requirements: - Must include: identifier, name, gender, birthDate - Should include: address, telecom, race, ethnicity when available - Use US Core extensions for race and ethnicity - Follow US postal address conventions - Use appropriate terminologies (e.g., HL7 AdministrativeGender, OMB race categories) Data Mapping Guidelines: - Extract patient name and structure as HumanName with family/given components - Map gender terms to FHIR AdministrativeGender codes (male, female, other, unknown) - Convert birth dates to FHIR date format - Structure addresses using Address data type with appropriate use codes - Map race/ethnicity information using US Core extensions with appropriate OMB codes - Generate medical record number as primary identifier when not provided - Include meta.profile reference to US Core Patient profile Output Format: - Provide only the valid FHIR JSON resource without additional commentary or explanation. User Prompt - Convert the following patient information into a FHIR Patient resource conformant with US Core 6.1.0: `Jane Doe is a white female born on November 15, 1950. She lives at 123 Main Street, Anytown, Michigan, zipcode 12345.`http://server.example.org/fhir/Practitioner/pract