Patient (103)

#NameSourceVerDescription
1ACC ICP Patienthl7.org.nz.fhir.ig.icp#currentR4The ACC ICP Patient resource based on NzPatient. Used to verify that an ICP Case has a valid claim.
2Argonaut Patient Profilefhir.argonaut.r2#1.0.0R2
3AU Base Patienthl7.fhir.au.base#currentR4This profile defines a patient structure that localises core concepts, including identifiers and terminology, for use in an Australian context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. [profiling](http://hl7.org/fhir/profiling.html), about how to support these concepts for specific implementation needs.
4AU Core Patienthl7.fhir.au.core#currentR4This profile sets minimum expectations for a Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It is based on the [AU Base Patient](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-patient.html) profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the Patient when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
5BePatienthl7.fhir.be.core#currentR4Belgian federal profile for a patient. Initially based on the functional description of the NIHDI. Special remarks for KMEHR users: following elements in KMEHR are not available in this FHIR resource. If needed, an extension can be defined in a future iteration of these specifications: the 'deathlocation' (location is not available but the death of the patient is expressed by either date or Boolean cfr. infra.), the 'insurancystatus' (covered in a seperate FHIR resource: Coverage), 'insurancymembership' (covered in a seperate FHIR resource: Coverage) and 'profession' (covered in a possible future FHIR resource: OccupationalData.)
6Breast cancer patienthl7.fhir.uv.ichom-breast-cancer#currentR4A patient who has been diagnosed with or is receiving medical treatment for breast cancer. This profile includes the ICHOM patient characteristics and demographic factors.
7C4BB Patienthl7.fhir.us.carin-bb#currentR4This profile builds upon the US Core Patient profile. It is used to convey information about the patient who received the services described on the claim.
8C4DIC Patienthl7.fhir.us.insurance-card#currentR4The goal of this profile is to describe a data-minimized version of Patient used to convey information about the Member who has health insurance coverage. Information that would normally not appear on a health insurance card is not required. The use of this profile is only approved for conveying information related to a health insurance card as part of this IG.
9Cancer Patient Profilehl7.fhir.us.mcode#currentR4A patient who has been diagnosed with or is receiving medical treatment for a malignant growth or tumor. The only difference between CancerPatient and [US Core Patient](http://hl7.org/fhir/us/core/StructureDefinition-us-core-patient.html) is that Patient.deceased is a [must-support](https://www.hl7.org/fhir/profiling.html#mustsupport) element in mCODE. Must-support is an instruction to implementers of FHIR clients and servers, rather than a constraint on data structure. Any Patient resource complying with US Core Patient Profile will also comply with CancerPatient.
10CDex Patient Demographics Profilehl7.fhir.us.davinci-cdex#currentR4This Profile is defined to be [contained](http://hl7.org/fhir/R4/references.html) within the CDex Task Attachment Request Profile or CDex Task Data Request Profile. It is referenced when additional patient demographic data is communicated for a clinical data request (for example, to verify patient identity for HIPAA compliance regulations). It constrains the following elements to be *mandatory* (min=1): - A default resource ID of "patient" - A member ID identifier slice - A patient's name and the following element to be [*must support*](attachments-conformance.html#cdex-must-support-definition) (min=0): - A patient account number identifier slice - A date of birth
11CDMH Patienthl7.fhir.us.cdmh#currentR4This is the Patient Resource profile for the IG.
12Central Cancer Registry Reporting Cancer Patienthl7.fhir.us.central-cancer-registry-reporting#currentR4Patient Resource profile for Central Cancer Registry Reporting based off the US Public Health Patient profile with further restrictions on identifiers.
13CH ALIS Patient Profilech.fhir.ig.ch-alis#currentR4Base definition for the Patient resource in the context of ALIS-Connect.
14CH Core Patientch.fhir.ig.ch-core#currentR4Core patient definition in the swiss context. Relevant are definitions by the eCH-0010 V7.0 data standard mailing address and eCH-0011 V8.1 data standard pesond data. The CH Core Patient is based upon the core FHIR Patient Resource and designed to meet the applicable patient demographic data elements in Switzerland. See also [BFS](https://www.bfs.admin.ch/bfs/de/home/register/personenregister/registerharmonisierung/nomenklaturen.html) for further information
15CH Core Patient EPRch.fhir.ig.ch-core#currentR4Core patient definition in the context of the electronic patient record (EPR). It is used to include the patient in an EPR document (referenced in Composition/DocumentReference).
16CH CRL Patientch.fhir.ig.ch-crl#0.9.0R4Definition of the Patient for reporting to the cancer registry
17CH ELM Patientch.fhir.ig.ch-elm#currentR4This CH ELM base profile constrains the Patient resource for the purpose of laboratory orders and test reports.
18CH EMS Patient Profilech.fhir.ig.ch-ems#1.9.0R4Definition of the patient
19CH EPR mHealth Patient Profile for PIXm Mobile Patient Identity Feedch.fhir.ig.ch-epr-mhealth#currentR4The patient demographics and identifier information which can be provided in the PIXm Feed according to the EPR. If the patient is already registered in a community, the MPI-PID SHALL be provided as an identifier. The EPR-SPID as an identifier MAY be added. The birthname can be added with the ISO 21090 qualifier extension.
20CH Lab Patientch.fhir.ig.ch-lab-report#currentR4This profile constrains the Patient resource for the purpose of laboratory test reports in Switzerland.
21CH Lab Patientch.fhir.ig.ch-laboratory-report#currentR4This profile constrains the Patient resource for the purpose of laboratory test reports in Switzerland.
22CL Pacientehl7.fhir.cl.corecl#currentR4Este Perfil ha sido desarrollado para cubrir las necesidades del Caso de Uso de Receta Electrónica. Sin embargo, se ha modelado con el fin de cubrir las necesidades nacionales de un Recurso Paciente para un Historial Clínico Nacional
23CL Pacientehl7.fhir.cl.clcore#1.8.4R4Este Perfil ha sido desarrollado para cubrir las necesidades del Caso de Uso de Receta Electrónica. Sin embargo, se ha modelado con el fin de cubrir las necesidades nacionales de un Recurso Paciente para un Historial Clínico Nacional
24CPG Patienthl7.fhir.uv.cpg#currentR4Profile of Patient for use with CPG Implementation Guide
25CRD Patienthl7.fhir.us.davinci-crd#currentR4This profile specifies additional constraints on the US Core Patient profile to support coverage requirements discovery.
26Danish Core Patient Profilehl7.fhir.dk.core#2.2.0R4HL7 Denmark core profile for a patient
27Davinci ATR Patienthl7.fhir.us.davinci-atr#currentR4This is the Patient Resource profile for the IG.
28Decedenthl7.fhir.us.vrsandbox#currentR4Decedent (USCorePatient)
29Decedenthl7.fhir.us.vrdr#currentR4Decedent (USCorePatient)
30EEBase Patienthl7.fhir.ee.base#currentR5Patient is a FHIR resource intended for documenting demographical and/or administrative information about the individual on the receiving end of healthcare services. In context of Estonian healthcare data exchange, the patient MUST be identifiable by Person Identity System.
31FHIRcast Patient for Close Eventshl7.fhir.uv.fhircast#currentR4BProvides guidance as to which Patient attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-close events.
32FHIRcast Patient for Open Eventshl7.fhir.uv.fhircast#currentR4BProvides guidance as to which Patient attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-open events.
33FI Base Patienthl7.fhir.fi.base#currentR4This is the Finnish base profile for the Patient resource.
34HRex Patient Demographicshl7.fhir.us.davinci-hrex#currentR4Defines constraints on the patient resource for the minimal set of data to query and retrieve patient demographic information.
35IBCM Fetal Record Profilehl7.fhir.uv.ibcm#currentR5Profile to represent a fetal record which will be used to collect data around the unborn child/fetus (e.g. headcircumference, fetal heart rate and position of the fetus)
36ICSR Patienthl7.fhir.us.icsr-ae-reporting#currentR4The fields required to identify a patient for an ICSR Report.
37IDI Patienthl7.fhir.us.identity-matching#currentR4(Base Level) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation. Only requires that 'some valuable data' be populated within the Patient resource and utilizes no weighting of element values.
38IDI Patient L0hl7.fhir.us.identity-matching#currentR4(Level 0 weighting) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation, and prescribe a minimum set of data elements which meet a combined 'weighted level' of at least 9
39IDI Patient L1hl7.fhir.us.identity-matching#currentR4(Level 1 weighting) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation, and prescribe a minimum set of data elements which meet a combined 'weighted level' of at least 10 and using attributes that are consistent with an identity that has been verified by the match requestor
40ImmDS Patienthl7.fhir.us.immds#1.0.0R4A patient for whom immunization forecast is being requested.
41Immunization Decision Support Patient Profilehl7.fhir.uv.immds#0.2.0R4Defines constraints and extensions on the patient resource for the minimal set of data to perform the Immunization Decision Support Forecast operation.
42IPA-Patienthl7.fhir.uv.ipa#currentR4Minimum expectations for a Patient resource when accessed via a International Patient Access API. This profile describes how applications fetch the Patient resource to check the patient identity and access basic demographics and other administrative information about the patient.
43LK Core Patientfhir.SLexampleIG#currentR4National core Patient FHIR profile published by the Ministry of Health Sri Lanka
44MIBasePatientProfilehl7.fhir.mi.base#currentR4MI Base Patient Profile
45MIPHRPatienthl7.fhir.mi.phr#currentR4MI PHR Patient Profile
46MyPatienthl7.fhir.us.vrsandbox#currentR4An example profile of the Patient resource.
47MyPatientch.fhir.ig.ch-ig#currentR4Test
48MyPatientch.fhir.ig.ch-vacd#currentR4An example profile of the Patient resource.
49no-basis-Patienthl7.fhir.no.basis#2.1.2R4Basisprofil for Norwegian Patient information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.
50Northern Region Patient profilefhir.org.nz.ig.northernregion#currentR4Represents Patient data exposed through the Northern Region APIs.
51NZ Patientfhir.org.nz.ig.base#currentR4The base New Zealand Patient profile
52Paciente Cohl7.fhir.co.CoreCO#currentR4Especificación de datos del recurso Patient, tomando como referencia las definiciones de la resolución 866
53PacienteMPIfhir.minsal.ListaDeEspera#currentR4Paciente definido para el Registro Maestro de Pacientes
54PAS Beneficiary Patienthl7.fhir.us.davinci-pas#currentR4A patient who is the beneficiary of an insurance plan.
55PAS Subscriber Patienthl7.fhir.us.davinci-pas#currentR4A patient who is the subscriber of an insurance plan.
56Patienthl7.fhir.nl.zorgviewer#currentR3Patient
57Patienthl7.eu.fhir.xpandh.lab#currentR4This profile defines how to represent Patient in FHIR for the purpose of the XPanDH project.
58Patienthl7.fhir.nl.fhir-ig-sandbox-stu3#currentR3Patient
59Patienthl7.eu.fhir.xpandh#currentR4This profile defines how to represent Patient in FHIR for the purpose of the XpanDH project.
60Patient (AU IPS)hl7.fhir.au.ips#currentR4This profile is based on the UV profile, with Australian rules added as well (by reference to the Australian profile)
61Patient (EHIC)hl7.fhir.eu.base#currentR4This profile represents the constraints applied to the Patient resource when sed with the EHIC coverage profile.
62Patient (GateKeeper)hl7.eu.fhir.gk-poc-ai#currentR4This profile represents the constraints applied to the Patient resource by the GateKeeper (GK) FHIR Implementation Guide and describes the minimum expectations for the Patient resource when used in the GK composition or in one of the referred resources.
63Patient (GateKeeper)hl7.eu.fhir.gk#currentR4This profile represents the constraints applied to the Patient resource by the GateKeeper (GK) FHIR Implementation Guide and describes the minimum expectations for the Patient resource when used in the GK composition or in one of the referred resources.
64Patient (IPS)hl7.fhir.uv.ips#currentR4This profile represents the constraints applied to the Patient resource by the International Patient Summary (IPS) FHIR Implementation Guide and describes the minimum expectations for the Patient resource when used in the IPS composition or in one of the referred resources.
65Patient - At Home In Vitro Testhl7.fhir.us.home-lab-report#currentR4This Patient profile represents an At-Home In-Vitro Test Patient.
66Patient - Child - Vital Recordshl7.fhir.us.vr-common-library#currentR4This Patient profile represents the subject patient (newborn/infant/child) for whom clinical data is included in the report.
67Patient - Child Vital Recordshl7.fhir.us.vrsandbox#currentR4The subject patient (newborn/infant/child) for whom clinical data is included in the report.
68Patient - Decedent Fetus - Vital Recordshl7.fhir.us.vr-common-library#currentR4This Patient profile represents a delivered fetus for which clinical data is included in the report.
69Patient - Decedent Fetus Vital Recordshl7.fhir.us.vrsandbox#currentR4A stillborn for whom clinical data is included in the report.
70Patient - Lab Reporthl7.fhir.it.lab-report#currentR4Descrive come rappresentare le informazioni del paziente nei documenti FHIR.
71Patient - Mother - Vital Recordshl7.fhir.us.vr-common-library#currentR4This Patient profile represents the woman who gave birth to, or delivered the infant.
72Patient - Mother Vital Recordshl7.fhir.us.vrsandbox#currentR4This Patient profile represents the woman who gave birth to, or delivered the infant.
73Patient profilehl7.fhir.uv.pocd#currentR4StructureDefinition for Patient resources that represent demographics and other administrative information.
74Patient Profilehl7.fhir.ca.baseline#currentR4Proposed constraints and extensions on the Patient Resource
75Patient Profile - General - Allowable Datahl7.fhir.uv.shc-vaccination#currentR4Defines a [fallback (AD) profile](./profiles.html#conformance-to-profiles) representing a patient in a health card related to infectious disease vaccination and testing issued in jurisdictions where no jurisdiction-specific profile is available. [See here for implementation details](./patient.html).
76Patient Profile - General - Data Minimizationhl7.fhir.uv.shc-vaccination#currentR4Defines a [primary (DM) profile](./profiles.html#conformance-to-profiles) representing a patient in a health card related to infectious disease vaccination and testing issued in jurisdictions where no jurisdiction-specific profile is available. [See here for implementation details](./patient.html).
77Patient Profile - United States - Allowable Datahl7.fhir.uv.shc-vaccination#currentR4Defines a [fallback (AD) profile](./profiles.html#conformance-to-profiles) representing a patient in a health card related to infectious disease vaccination and testing issued in the United States. [See here for implementation details](./patient.html).
78Patient Profile - United States - Data Minimizationhl7.fhir.uv.shc-vaccination#currentR4Defines a [primary (DM) profile](./profiles.html#conformance-to-profiles) representing a patient in a health card related to infectious disease vaccination and testing issued in the United States. [See here for implementation details](./patient.html).
79Patient-IEHRfhir.uv.crossborderdataexchange#currentR4
80Patient: Animalhl7.fhir.eu.laboratory#currentR4This profile defines how to represent an Animal as subject of care in FHIR for the purpose of this guide. This is used to identify the species when a specimen is collected from an animal
81Patient: HDRhl7.eu.fhir.xpandh.hdr#currentR4This profile defines how to represent Patient in FHIR for the purpose of the XpanDH project.
82Patient: IDEA4RChl7.eu.fhir.idea4rc#currentR4This profile defines how to represent Patient in FHIR for the purpose of the IDEA4RC project.
83Patient: Identified Personhl7.fhir.eu.laboratory#currentR4This profile defines how to represent an identified human Patient in FHIR for the purpose of this guide.
84Patient: PCSPhl7.eu.fhir.pcsp#currentR4This profile defines how to represent Patient in FHIR for the purpose of the PanCareSurPass project.
85Patient_eltsshl7.fhir.us.eltss#currentR4Patient resource mapping for eLTSS
86Patientenportal Patientfhir.qpath4ms#currentR4Profil eines Patienten im Patientenportal
87Pediatric Cancer Patienthl7.fhir.us.pedcan#currentR4A pediatric patient being treated for cancer
88Perfil Paciente Cardiohl7.fhir.cl.recetachile#currentR4Indica datos administrativos del paciente que se encuentra dentro del programa cardiovascular
89PetPatientfhir.zentricx-grupo-b#currentR4
90PhdPatienthl7.fhir.uv.phd#currentR4The patient information reported from personal health gateways (PHG)
91Pseudonymer Patientfhir.qpath4ms#currentR4Profil eines pseudonymen Patienten
92QICore Patienthl7.fhir.us.qicore#currentR4Profile of Patient for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
93RTPBC Patienthl7.fhir.us.carin-rtpbc#1.0.0R4This profile constrains the Patient resource for carrying the limited patient information required in the consumer real-time pharmacy benefit check (RTPBC) process. The profile differs from the US Core Patient profile in certain respects. It does not contain the us-core-race, us-core-ethnicity or us-core-birthsex extensions, and the Patient.communication.language and Patient.telecom elements are not set to Must Support; these variances reflects that clients in the exchange will typically be mobile consumer applications that do not posess this information, and that the information is not pertinent to this use case. The RTPBC profile further constrains certain US Core and base elements in a manner that is compatible with the the US Core profile (e.g., tightening element cardinality and further limiting allowed terminology).
94Specialty Rx Patienthl7.fhir.us.specialty-rx#currentR4This profile tailors the Patient resource for carrying the patient information needed to support specialty medication dispensing and enrollment in related programs.
95Swissnoso Patientch.fhir.ig.swissnoso#1.0.0R4This profile constrains the Patient resource to represent the characteristics of a patient in the context of a report to Swissnoso.
96TelemedicinePatienthl7.fhir.dk.hackathon.2022#currentR4An example profile of the Patient resource.
97UK Core Patientfhir.r4.ukcore.stu1#1.0.4R4Defines the UK Core constraints and extensions on the Patient resource for the minimal set of data to query and retrieve an individual’s demographic information.
98US Core Patient Profilehl7.fhir.us.core#currentR4The US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v3 'Patient Demographics' requirements. This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
99US Public Health Patienthl7.fhir.us.ecr#currentR4This Patient profile represents a US Public Health Patient. It is based on the **US Core Patient** profile with further constraints to require and/or allow masking of some data elements, and the addition of the US Public Health Gender Identity extension. For ONC’s USCDI requirements, it also adds Must Support constraints to the following: * contact detail (e.g. a telephone number or an email address) * a communication language * a race * an ethnicity * a birth sex
100US Public Health Patienthl7.fhir.us.ph-library#currentR4This Patient profile represents a US Public Health Patient. It is based on the **US Core Patient** profile with further restrictions to allow masking of some data elements and the addition of the patient-genderIdentity extension. For ONC’s USCDI requirements, it adds Must Support constraints to the following: * contact detail (e.g. a telephone number or an email address) * a communication language * a race * an ethnicity * a birth sex
101US Public Health Patienthl7.fhir.us.ph-library#currentR4This Patient profile represents a US Public Health Patient.
102US Public Health Patienthl7.fhir.us.central-cancer-registry-reporting#currentR4This Patient profile represents a US Public Health Patient. This proile is present in the IG to synchronize with common Patient profile being developed by public health profiles library IG. This profile is being used by the Cancer Patient profile. Implementers of the IG are expected to implement only the Cancer Patient profile. It is based on the **US Core Patient** profile with further restrictions to allow masking of some data elements and the addition of the patient-genderIdentity extension. For ONC’s USCDI requirements, it adds Must Support constraints to the following: * contact detail (e.g. a telephone number or an email address) * a communication language * a race * an ethnicity * a birth sex
103US Veteranhl7.fhir.us.military-service#currentR4US Veteran profile extends US Core Patient profile. It's intended to be used when the patient is Veteran was confirmed by the VA. This profile includes a ['US Veteran Status'] (usveteranstatus) extension to hold status information as a boolean (i.e. 'true' indicates that the patient's veteran status was confirmed).
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103
Patient C I D I I D D D I D I I I D I D I D I I D I D I D D I D D D D D D D D D
Patient.id C F C D C D D C
Patient.animal C
Patient.meta C C C C
Patient.meta.source D
Patient.meta.security S C (2)
Patient.meta.security.system C F
Patient.meta.profile C D S C F D (2) S C F D (2) S C F D (2) S C F D (2) S C F (2)
Patient.meta.lastUpdated C D C D
Patient.implicitRules C C
Patient.language C C
Patient.text C
Patient.contained C
Patient.extension C (3) S D (10) S (4) S C D (3) S C (5) S S C B M (5) S C I D (5) S (3) S C S C D (2) S C D (2) S C (3) S C (3) S C (4) S C (2) S C (2) S C S D (2) S C (9) S C (8) S C D (5) S C (10) S C S C S C (6) S C (5) S C (4) S C S C D B M (7) S C (4) S C (4) S C D (5) C S (2) S C (2) S C (2) S C (2) S C (3) S C (2) S C S C (4) S C D (9) S C (6) S C (6) S C (6) S C (7) S C (6) S C
Patient.extension.extension S D B M (2) C S C (2) S C (4)
Patient.extension.extension.value[x] C F (2) F (2)
Patient.extension.value[x] B M (2) B M D (3)
Patient.extension.value[x].country B M B M
Patient.extension.value[x].state B M B M
Patient.extension.value[x].city
Patient.extension.value[x].city.extension S C (2) S C (2)
Patient.extension.url
Patient.extension.valueCodeableConcept B M
Patient.modifierExtension C C
Patient.identifier S (2) C S C (4) S C D (2) S C D (3) S C F D (3) S C (5) S C F (2) S C F D (5) S C (3) S C (3) S C (2) S F (3) S C F (3) C D C D S C (2) S C (2) S C (6) S C (2) S C (2) C D C D S C D (2) S C F D (2) C I S C (7) S C (2) C S D (5) S C (3) S C (2) C D S C S C S C D (2) S C (2) S C (2) S C (8) S C (3) S C (3) S C D (2) C D C D C D S C (2) S C D (3) C S C (2) C S C (2) S C (2) C C C C
Patient.identifier.assigner C D C (2)
Patient.identifier.use D D C F C F (2) B M C F C (2) C F
Patient.identifier.extension S C D (8) S (2) S C (2) S C S C S C S C
Patient.identifier.extension.value[x] C F C F F C F
Patient.identifier.type C F B M (3) C (4) D B M D B M C F C (5) F F C B M C B M C B M C C D B M C F C F B M C F (2) C F (2) C F D (2) D C F C C F
Patient.identifier.type.text C (2)
Patient.identifier.type.extension S C D (2) S C D (2) S C D (2)
Patient.identifier.type.coding C (4) C (5) C C S C D (2)
Patient.identifier.type.coding.userSelected C (2)
Patient.identifier.type.coding.version C (2)
Patient.identifier.type.coding.display D D C F (2)
Patient.identifier.type.coding.code C F (4) D D C F (5) F C F C C F D C B M C F (2) C D
Patient.identifier.type.coding.system C F (4) D D C F (5) F C F C F D C F (2) C F D
Patient.identifier.value C C C C (2) D D C C C C C C (6) C C C D (4) C C C I D (2) C (2) C C (2) C C C C C
Patient.identifier.system C C F C F F C B M F C F (6) C C C F D (4) F (2) C F C B M C F B M (7) C (2) C F C F (2) C D C F C C F C
Patient.identifier.period C (2) C (2)
Patient.active C F C I C C C
Patient.name C C I D D D C C C C C C C S C D (3) S C D (3) S C D (3) C S C (2) C S C D (3) C D C I I I C I C C C C C C D C I I C C I C I C I C I S C (3) S C (3) C I C I D C I I D C C C C I C C C
Patient.name.id C
Patient.name.extension S C S C D B M C S C S C S C S C
Patient.name.extension.value[x] C F C F F C F
Patient.name.suffix C C C C D C
Patient.name.prefix C C C C (2) D C
Patient.name.use C F D (2) C F D (2) C F C F (3) C F (2) C F (2) C C
Patient.name.given C C C C C C D (2) C D (2) C (3) C C C C D C D C C C C D C
Patient.name.given.extension S C S C (2) S C (2) S C (2) S C (2)
Patient.name.family C C D C C C C D (2) C D (2) C C (3) C C C C D C C C C C C C C C C C C
Patient.name.family.extension S C S C D (2) S C D (2) S C (2) S C (2) S C (2) S C (2) S C (2)
Patient.name.period C C C C
Patient.name.text C C C C (2) C C D D C D C
Patient.telecom D S C (4) S (2) D D C C D S C (2) C C C S C (3) S C (3) S C (3) S C (3)
Patient.telecom.rank
Patient.telecom.extension S C D (3) S C S C S C S C (3) S C
Patient.telecom.extension.value[x] C F C F F C F
Patient.telecom.period
Patient.telecom.use D B M D B M B M
Patient.telecom.value C (2) D D C C C C I D C C
Patient.telecom.system C D B M D B M C C C C C F C B M C F (2) C F (2) F (2) C F (2)
Patient.telecom.system.extension S C (2)
Patient.gender C B M C C D D D C C B M C D C D B M D B M C C C B M C C C D B M I D C C C B M C D C C D B M C C B M
Patient.gender.extension S C (2) S C S C S C (2) S C
Patient.gender.extension.value[x] C F C F F C F
Patient.birthDate C I C C D D D C C C C I C D C D D C C C D C D C C C D I I C D C C C C D C D C C D D C C C C C I C C C C
Patient.birthDate.extension S D (3) S (2) S C (2) S C D (2) S C D (2) S C (4) S C (2) S C D (2) S C D (3) S C S C (2) S C D S C D (2) S C D (2) S C S C S C (2) S C
Patient.birthDate.extension.value[x] D C F C F F C F
Patient.deceased[x] S D (3) D S C D (2) C S C D (2) S C (2) S C (2) C F C F C C D C C
Patient.deceased[x].extension S D (2) S C
Patient.address D D C C S C (2) D C D I I I I C C I I D C C C D C D C D C D C D C D
Patient.address.text C C D
Patient.address.period C
Patient.address.district C I D
Patient.address.district.extension S C D (2) S C D (2)
Patient.address.extension S C (2) S C (7) S C (7) S C S C D (2) S C S C (2) S C D S C D S C D (3) S C D S C D (2) S C S C S C S C
Patient.address.extension.value[x] C F C F F C F
Patient.address.use C F C
Patient.address.postalCode D C C I D C C
Patient.address.state D C C C B M B M I D C B M C B M
Patient.address.state.extension S C
Patient.address.city D C C D I D C C
Patient.address.city.extension S C D (2) S C D (2)
Patient.address.line D C C D C D C C
Patient.address.country B M D C C B M B M D C C D B M
Patient.address.country.extension S C (2)
Patient.maritalStatus C D B M B M C B M B M B M B M B M C C C B M
Patient.maritalStatus.text
Patient.maritalStatus.extension S C S C S C
Patient.maritalStatus.extension.value[x] B M B M
Patient.multipleBirth[x] C D C S C (2) D D D D C C C
Patient.multipleBirth[x].extension S C D S C
Patient.photo C C C D C C
Patient.contact C D S C (4) D D C D C D C
Patient.contact.extension S (2) S C D (2) S C D (2) S C (3)
Patient.contact.modifierExtension
Patient.contact.relationship B M B M C F (3) C B M C B M C C B M D B M C C C C
Patient.contact.relationship.text
Patient.contact.relationship.coding C C
Patient.contact.relationship.coding.display
Patient.contact.relationship.coding.code C C
Patient.contact.relationship.coding.system C C
Patient.contact.name C (2) C D C D D C C
Patient.contact.name.extension S C S C S C S C
Patient.contact.name.extension.value[x] C F C F F C F
Patient.contact.name.given C D C D C
Patient.contact.name.family C D C D C
Patient.contact.name.family.extension S C D (2) S C D (2)
Patient.contact.name.use F D F D
Patient.contact.telecom C C D C C
Patient.contact.telecom.extension S C S C S C S C
Patient.contact.telecom.extension.value[x] C F C F F C F
Patient.contact.telecom.system
Patient.contact.telecom.system.extension S C (2)
Patient.contact.address D C C C
Patient.contact.address.extension S C S C S C S C
Patient.contact.address.extension.value[x] C F C F F C F
Patient.contact.gender
Patient.contact.organization
Patient.contact.organization.identifier
Patient.contact.organization.identifier.assigner
Patient.contact.period
Patient.communication C C D S C (2) D D C C C C C C
Patient.communication.extension S C (2)
Patient.communication.extension.extension S C (3)
Patient.communication.extension.extension.value[x] D (2)
Patient.communication.modifierExtension
Patient.communication.language C B M B M D B M D B M B M B M C B M D B M B M
Patient.communication.language.extension S C S C S C S C
Patient.communication.language.extension.value[x] C F C F F C F
Patient.communication.language.coding C C
Patient.communication.language.coding.display
Patient.communication.language.coding.code C C
Patient.communication.language.coding.system C C
Patient.communication.preferred C F C
Patient.generalPractitioner D C C D D S C (2) S C (4) C S C D (2) C
Patient.generalPractitioner.extension S C D
Patient.generalPractitioner.identifier
Patient.generalPractitioner.identifier.assigner
Patient.generalPractitioner.display D D
Patient.generalPractitioner.reference D D
Patient.managingOrganization C D C C C C C C
Patient.managingOrganization.identifier
Patient.managingOrganization.identifier.assigner
Patient.managingOrganization.reference C
Patient.link C D C S C (2) S C (2) C C D
Patient.link.extension
Patient.link.modifierExtension
Patient.link.other
Patient.link.other.identifier
Patient.link.other.identifier.assigner
Patient.link.type F F
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023