Patient (156)

#	Name	Source	Ver	Description
1	ACC ICP Patient	hl7.org.nz.fhir.ig.icp#current	R4	The ACC ICP Patient resource based on NzPatient. Used to verify that an ICP Case has a valid claim.
2	ACT-NOW patient	actnow.canshare.co.nz#current	R4	ACT-NOW patient
3	ADHA Core Patient	au.digitalhealth.r4#current	R4	The purpose of this profile is to provide a core representation of a patient for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
4	ADHA Match Patient	au.digitalhealth.r4#current	R4	The purpose of this profile is to provide a representation of a patient to check and match patient identity the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
5	ADHA My Health Record Patient	au.digitalhealth.r4#current	R4	The purpose of this profile is to define a representation of a patient for exchange usage scenarios with the My Health Record system infrastructure in Australia.
6	ADHA Patient Demographics	au.digitalhealth.r4#current	R4	The purpose of this profile is to provide a representation of a patient's demographics to support the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
7	ANC Base Patient	who.fhir.anc-cds#current	R4	ANC Base Patient
8	ANC Patient	who.fhir.anc-cds#current	R4	ANC Patient
9	Argonaut Patient Profile	fhir.argonaut.r2#1.0.0	R2
10	AU Base Patient	hl7.fhir.au.base#current	R4	This 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.
11	AU Core Patient	hl7.fhir.au.core#current	R4	This 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.
12	AU Primary Care Patient	au.csiro.fhir.au-primarycare#current	R4	Details of a patient including identity, demographic and contacts. Extensions * Indigenous Status : Aboriginal or Torres Strait Islander origin status for the individual, usually self-identified. * Birth Place : Record of place of birth. * Date of Arrival : Record of date of arrival in australia. * Ethnicity : Use to record information about one or more cultural and ethnic identities, self described by the individual. * Gender Identity : Record of personal identity with respect to gender.
13	BePatient	ehealthplatform.be.r4.federalprofiles#1.3.3-beta	R4	Belgian 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.)
14	BePatient	hl7.fhir.be.core#current	R4	Belgian 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.)
15	Breast cancer patient	hl7.fhir.uv.ichom-breast-cancer#current	R4	A patient who has been diagnosed with or is receiving medical treatment for breast cancer. This profile includes the ICHOM patient characteristics and demographic factors.
16	C4BB Patient	hl7.fhir.us.carin-bb#current	R4	This 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.
17	C4DIC Patient	hl7.fhir.us.insurance-card#current	R4	The 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.
18	Cancer Patient Profile	hl7.fhir.us.mcode#current	R4	A 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.
19	CareCitizen	kl.dk.fhir.gateway#current	R4	Administrative information about a citizen receiving care or care related services.
20	CDex Patient Demographics Profile	hl7.fhir.us.davinci-cdex#current	R4	This 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
21	CDMH Patient	hl7.fhir.us.cdmh#current	R4	This is the Patient Resource profile for the IG.
22	Central Cancer Registry Reporting Cancer Patient	hl7.fhir.us.central-cancer-registry-reporting#current	R4	Patient Resource profile for Central Cancer Registry Reporting based off the US Public Health Patient profile with further restrictions on identifiers.
23	CH ALIS Patient Profile	ch.fhir.ig.ch-alis#current	R4	Base definition for the Patient resource in the context of ALIS-Connect.
24	CH Core Patient	ch.fhir.ig.ch-core#current	R4	Core 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
25	CH Core Patient EPR	ch.fhir.ig.ch-core#current	R4	Core 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).
26	CH CRL Patient	ch.fhir.ig.ch-crl#0.9.0	R4	Definition of the Patient for reporting to the cancer registry
27	CH ELM Patient	ch.fhir.ig.ch-elm#current	R4	This CH ELM base profile constrains the Patient resource for the purpose of laboratory orders and test reports.
28	CH EMED EPR Patient	ch.cara.fhir.epr.emed#current	R4	Definition of the patient for the eMedication context
29	CH EMS Patient Profile	ch.fhir.ig.ch-ems#1.9.0	R4	Definition of the patient
30	CH EPR mHealth Patient Profile for PIXm Mobile Patient Identity Feed	ch.fhir.ig.ch-epr-mhealth#current	R4	The 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.
31	CH Lab Patient	ch.fhir.ig.ch-lab-report#current	R4	This profile constrains the Patient resource for the purpose of laboratory test reports in Switzerland.
32	CH Lab Patient	ch.fhir.ig.ch-laboratory-report#current	R4	This profile constrains the Patient resource for the purpose of laboratory test reports in Switzerland.
33	CHMED Patient (Card)	ch.chmed.emediplan#current	R4	Profile for the Patient resource, referenced in the CHMED Medication Card Composition
34	CHMED Patient (Pre)	ch.chmed.emediplan#current	R4	Profile for the Patient resource, referenced in the CHMED Medication Prescription Composition
35	Citizen	kl.dk.fhir.ffbreporting#current	R4	Administrative information about a citizen receiving social services.
36	Citizen	kl.dk.fhir.core#current	R4	Citizen demographics, as expressed by dk-core
37	CL Paciente	hl7.fhir.cl.corecl#current	R4	Este 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
38	CL Paciente	hl7.fhir.cl.clcore#1.8.4	R4	Este 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
39	CPG Patient	hl7.fhir.uv.cpg#current	R4	Profile of Patient for use with CPG Implementation Guide
40	CRD Patient	hl7.fhir.us.davinci-crd#current	R4	This profile specifies additional constraints on the US Core Patient profile to support coverage requirements discovery.
41	Danish Core Patient Profile	hl7.fhir.dk.core#2.2.0	R4	HL7 Denmark core profile for a patient
42	Davinci ATR Patient	hl7.fhir.us.davinci-atr#current	R4	This is the Patient Resource profile for the IG.
43	Decedent	hl7.fhir.us.vrsandbox#current	R4	Decedent (USCorePatient)
44	Decedent	hl7.fhir.us.vrdr#current	R4	Decedent (USCorePatient)
45	DevDaysIGtutorial-Patient	devdays.r4.example.conformanceresources#1.0.0	R4	Profile for Patient used in an example use case in the DevDaysIGtutorial. Clients can use this profile to know which data it may receive. Server's response SHALL conform to this profile.
46	EEBase Patient	hl7.fhir.ee.base#current	R5	Patient 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.
47	FHIRcast Patient for Close Events	hl7.fhir.uv.fhircast#current	R4B	Provides 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.
48	FHIRcast Patient for Open Events	hl7.fhir.uv.fhircast#current	R4B	Provides 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.
49	FI Base Patient	hl7.fhir.fi.base#current	R4	This is the Finnish base profile for the Patient resource.
50	Finnish PHR Patient profile	SUPPORT.R4#3.0.0	R4	The profile for representing a Finnish person
51	HRex Patient Demographics	hl7.fhir.us.davinci-hrex#current	R4	Defines constraints on the patient resource for the minimal set of data to query and retrieve patient demographic information.
52	IBCM Fetal Record Profile	hl7.fhir.uv.ibcm#current	R5	Profile 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)
53	ICSR Patient	hl7.fhir.us.icsr-ae-reporting#current	R4	The fields required to identify a patient for an ICSR Report.
54	IDI Patient	hl7.fhir.us.identity-matching#current	R4	(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.
55	IDI Patient L0	hl7.fhir.us.identity-matching#current	R4	(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
56	IDI Patient L1	hl7.fhir.us.identity-matching#current	R4	(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
57	IHE Patient Master Identity Registry Merged Patient	ihe.iti.pmir#current	R4	StructureDefinition for Patient resource constraints for messages in the IHE PMIR Profile when the Patient is being merged.
58	IHE Patient Master Identity Registry Related Person Patient	ihe.iti.pmir#current	R4	StructureDefinition for Patient resource constraints for messages in the IHE PMIR Profile when the Patient is linked to a related person.
59	ImmDS Patient	hl7.fhir.us.immds#1.0.0	R4	A patient for whom immunization forecast is being requested.
60	Immunization Decision Support Patient Profile	hl7.fhir.uv.immds#0.2.0	R4	Defines constraints and extensions on the patient resource for the minimal set of data to perform the Immunization Decision Support Forecast operation.
61	IPA-Patient	hl7.fhir.uv.ipa#current	R4	Minimum 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.
62	KLGatewayChildrenCitizen	kl.fhir.dk.children#current	R4	Administrative information about a citizen receiving care or care related services.
63	LK Core Patient	fhir.SLexampleIG#current	R4	National core Patient FHIR profile published by the Ministry of Health Sri Lanka
64	MedComCorePatient	medcom.fhir.dk.core#current	R4	Patient/citizen resource to use as subject in MedCom communication.
65	MedNet Interface (MNI) - Patient	swiss.mednet.fhir#0.15.0	R4	MedNet Interface (MNI) - Patient Profile
66	MIBasePatientProfile	hl7.fhir.mi.base#current	R4	MI Base Patient Profile
67	MIPHRPatient	hl7.fhir.mi.phr#current	R4	MI PHR Patient Profile
68	MRI Patient	il.moh.mri.r4#current	R4	מטרת פרופיל זה היא להגדיר ייצוג של מטופל המבקש לקבל שירות MRI בהקשר של ניטור זמן רשימת ההמתנה של משרד הבריאות הישראלי.
69	My Favorite Patient Profile	example.fhir.uv.myig#current	R4	This will be the description for the patient profile within the profile page
70	MyPatient	hl7.fhir.us.vrsandbox#current	R4	An example profile of the Patient resource.
71	MyPatient	smart-immunizations-mini#current	R4	An example profile of the Patient resource.
72	MyPatient	smart-ig-empty#current	R4	An example profile of the Patient resource.
73	MyPatient	my-ig#current	R4	My Patient profile
74	MyPatient	ch.fhir.ig.ch-ig#current	R4	Test
75	MyPatient	dhis2-ig-empty#current	R4	An example profile of the Patient resource.
76	MyPatient	ch.fhir.ig.ch-vacd#current	R4	An example profile of the Patient resource.
77	nl-core-patient	nictiz.fhir.nl.stu3.zib2017#2.2.15	R3	A Patient resource as defined by the Dutch Health and Care Information models or HCIM (Dutch: Zorginformatiebouwsteen or ZIB) Patient, with additions from the HCIMs Nationality, MaritalStatus, ContactPerson, LanguageProficiency, HealthProfessional and HealthcareProvider (HCIM releases 2015, 2016 and 2017)
78	no-basis-Patient	hl7.fhir.no.basis#2.1.2	R4	Basisprofil 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.
79	Northern Region Patient profile	fhir.org.nz.ig.northernregion#current	R4	Represents Patient data exposed through the Northern Region APIs.
80	NZ Patient	fhir.org.nz.ig.base#current	R4	The base New Zealand Patient profile
81	NZCentralRegionPatient	nz.central.ihub.ig#current	R4	Patient resource for Te Whatu Ora, Central Region
82	Oncology Patient	arkhn.fhir.uv.osiris#current	R4	Oncology patient defined by Osiris.
83	OpenMRS Patient	openmrs.fhir.core#current	R4	A FHIR Patient as understood by OpenMRS
84	Paciente Co	hl7.fhir.co.CoreCO#current	R4	Especificación de datos del recurso Patient, tomando como referencia las definiciones de la resolución 866
85	PacienteMPI	fhir.minsal.ListaDeEspera#current	R4	Paciente definido para el Registro Maestro de Pacientes
86	Participant	d3b.kidsfirst.r4#0.1.0	R4
87	PAS Beneficiary Patient	hl7.fhir.us.davinci-pas#current	R4	A patient who is the beneficiary of an insurance plan.
88	PAS Subscriber Patient	hl7.fhir.us.davinci-pas#current	R4	A patient who is the subscriber of an insurance plan.
89	Patient	ndhm.in#current	R4	This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient.
90	Patient	hl7.fhir.nl.zorgviewer#current	R3	Patient
91	Patient	hl7.eu.fhir.xpandh.lab#current	R4	This profile defines how to represent Patient in FHIR for the purpose of the XPanDH project.
92	Patient	hl7.fhir.nl.fhir-ig-sandbox-stu3#current	R3	Patient
93	Patient	cara#current	R4	This profile extension is used to ensure the fields of the master patient index are properly used throughout the implementation.
94	Patient	hl7.eu.fhir.xpandh#current	R4	This profile defines how to represent Patient in FHIR for the purpose of the XpanDH project.
95	Patient (AU IPS)	hl7.fhir.au.ips#current	R4	This profile is based on the UV profile, with Australian rules added as well (by reference to the Australian profile)
96	Patient (CZ)	ncez.cz.fhir.core#current	R4	Information about an individual receiving health care services
97	Patient (EHIC)	hl7.fhir.eu.base#current	R4	This profile represents the constraints applied to the Patient resource when sed with the EHIC coverage profile.
98	Patient (GateKeeper)	hl7.eu.fhir.gk-poc-ai#current	R4	This 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.
99	Patient (GateKeeper)	hl7.eu.fhir.gk#current	R4	This 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.
100	Patient (IPS)	hl7.fhir.uv.ips#current	R4	This 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.
101	Patient (PS-CA)	ca.infoway.io.psca#1.0.1-alpha3	R4	This profile represents the constraints applied to the Patient resource by the PS-CA project to represent the minimum expectations for the Patient resource when used in the PS-CA composition profile or in one of the referred resources. It is informed by the constraints of the [Patient IPS-UV profile](http://hl7.org/fhir/uv/ips/StructureDefinition-Patient-uv-ips.html) and the [Canadian Baseline Profile](http://build.fhir.org/ig/HL7-Canada/ca-baseline/branches/master/StructureDefinition-profile-patient.html)
102	Patient - At Home In Vitro Test	hl7.fhir.us.home-lab-report#current	R4	This Patient profile represents an At-Home In-Vitro Test Patient.
103	Patient - Child - Vital Records	hl7.fhir.us.vr-common-library#current	R4	This Patient profile represents the subject patient (newborn/infant/child) for whom clinical data is included in the report.
104	Patient - Child Vital Records	hl7.fhir.us.vrsandbox#current	R4	The subject patient (newborn/infant/child) for whom clinical data is included in the report.
105	Patient - Decedent Fetus - Vital Records	hl7.fhir.us.vr-common-library#current	R4	This Patient profile represents a delivered fetus for which clinical data is included in the report.
106	Patient - Decedent Fetus Vital Records	hl7.fhir.us.vrsandbox#current	R4	A stillborn for whom clinical data is included in the report.
107	Patient - Lab Report	hl7.fhir.it.lab-report#current	R4	Descrive come rappresentare le informazioni del paziente nei documenti FHIR.
108	Patient - Mother - Vital Records	hl7.fhir.us.vr-common-library#current	R4	This Patient profile represents the woman who gave birth to, or delivered the infant.
109	Patient - Mother Vital Records	hl7.fhir.us.vrsandbox#current	R4	This Patient profile represents the woman who gave birth to, or delivered the infant.
110	Patient Card	ch.chmed20af.emediplan#2.0.0	R4	Profile on Patient for Medication Card document
111	Patient Context	ihe.rad.ira#current	R5	IHE IRA DiagnosticReport-open patient context
112	Patient Pre	ch.chmed20af.emediplan#2.0.0	R4	Profile on Patient for Prescription
113	Patient profile	hl7.fhir.uv.pocd#current	R4	StructureDefinition for Patient resources that represent demographics and other administrative information.
114	Patient Profile	hl7.fhir.ca.baseline#current	R4	Proposed constraints and extensions on the Patient Resource
115	Patient Profile - General - Allowable Data	hl7.fhir.uv.shc-vaccination#current	R4	Defines 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).
116	Patient Profile - General - Data Minimization	hl7.fhir.uv.shc-vaccination#current	R4	Defines 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).
117	Patient Profile - United States - Allowable Data	hl7.fhir.uv.shc-vaccination#current	R4	Defines 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).
118	Patient Profile - United States - Data Minimization	hl7.fhir.uv.shc-vaccination#current	R4	Defines 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).
119	Patient-IEHR	fhir.uv.crossborderdataexchange#current	R4
120	Patient: Animal	hl7.fhir.eu.laboratory#current	R4	This 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
121	Patient: HDR	hl7.eu.fhir.xpandh.hdr#current	R4	This profile defines how to represent Patient in FHIR for the purpose of the XpanDH project.
122	Patient: IDEA4RC	hl7.eu.fhir.idea4rc#current	R4	This profile defines how to represent Patient in FHIR for the purpose of the IDEA4RC project.
123	Patient: Identified Person	hl7.fhir.eu.laboratory#current	R4	This profile defines how to represent an identified human Patient in FHIR for the purpose of this guide.
124	Patient: PCSP	hl7.eu.fhir.pcsp#current	R4	This profile defines how to represent Patient in FHIR for the purpose of the PanCareSurPass project.
125	Patient_eltss	hl7.fhir.us.eltss#current	R4	Patient resource mapping for eLTSS
126	Patientenportal Patient	fhir.qpath4ms#current	R4	Profil eines Patienten im Patientenportal
127	Patientodm	example.fhir.uv.myig#current	R4
128	PatientPoC	uptis-fhir-poc#current	R5	Common MPI limitations on Patient resouce. MPI profiili replica.
129	PatientSEVendorLite	care.commonprofiles.fhir#current	R4	Simplified patient for identification for communication between systems in Sweden
130	PatientVerifiedPoC	uptis-fhir-poc#current	R5	Verified Patient. MPI profile replica.
131	PDQm Patient Profile	ihe.iti.pdqm#current	R4	The PDQm Patient Profile - when any element in FHIR Core Patient are known, and when authorized to return the element, then all elements that are core to FHIR Patient should be returned - forbids modifier extensions - so that all uses do not need to be concerned with changes to the meaning of the core elements of the Patient resource - adds the patient-mothersMaidenName extension as an extension available to hold the mothers maiden name
132	Pediatric Cancer Patient	hl7.fhir.us.pedcan#current	R4	A pediatric patient being treated for cancer
133	Perfil Paciente Cardio	hl7.fhir.cl.recetachile#current	R4	Indica datos administrativos del paciente que se encuentra dentro del programa cardiovascular
134	PetPatient	fhir.zentricx-grupo-b#current	R4
135	PhdPatient	hl7.fhir.uv.phd#current	R4	The patient information reported from personal health gateways (PHG)
136	PIXm Patient constraints for Feed	ihe.iti.pixm#current	R4	Profile for describing elements which have to be accepted by the Patient Identifier Cross-reference Manager for performing its cross-referencing function. - requiring name - mustSupport for identifier, name, telecom, gender birthDate, address and managingOrganization
137	PIXm Patient Profile example for additional Manager constraints	ihe.iti.pixm#current	R4	Example Profile StructureDefinition for describing additional Patient resource constraints (requiring birthDate) by the Patient Identifier Cross-reference Manager for performing its cross-referencing function. - requiring name and birthDate - mustSupport for identifier, birthDate, name, telecom, gender birthDate, address and managingOrganization
138	Pseudonymer Patient	fhir.qpath4ms#current	R4	Profil eines pseudonymen Patienten
139	QICore Patient	hl7.fhir.us.qicore#current	R4	Profile of Patient for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
140	RTPBC Patient	hl7.fhir.us.carin-rtpbc#1.0.0	R4	This 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).
141	RunSushiPatient	tewhatuora.govt.nz.fhir.guide#current	R4	Patient resource
142	SE base profil for patient	hl7se.fhir.base#1.0.0	R4	This is the base Patient profile to be used when profiling on Patient in a Swedish context
143	Specialty Rx Patient	hl7.fhir.us.specialty-rx#current	R4	This profile tailors the Patient resource for carrying the patient information needed to support specialty medication dispensing and enrollment in related programs.
144	Swissnoso Patient	ch.fhir.ig.swissnoso#1.0.0	R4	This profile constrains the Patient resource to represent the characteristics of a patient in the context of a report to Swissnoso.
145	TelemedicinePatient	hl7.fhir.dk.hackathon.2022#current	R4	An example profile of the Patient resource.
146	TW Core Patient	tw.gov.mohw.twcore#0.1.1	R4	此臺灣核心-病人(TW Core Patient) Profile說明本IG如何進一步定義FHIR的Patient Resource以呈現基本資料 [[FMM1](http://build.fhir.org/versions.html#maturity)] - 2023/8/25異動說明： 1. 「全國的個人識別碼」(identifier:idCardNumber.type)原使用https://twcore.mohw.gov.tw/ig/twcore/CodeSystem/v2-0203#NNTWN，改使用HL7總會的http://terminology.hl7.org/CodeSystem/v2-0203#NNxxx，xxx的部分為ISO 3166三位字母代碼，新增[Extension: 識別碼後綴詞(Identifier Suffix)](StructureDefinition-identifier-suffix.html)表示，以遵從國際用法。 2. maritalStatus取消綁定臺灣的婚姻狀態代碼，因臺灣的婚姻狀態代碼可[對應](ConceptMap-marital-status-tw.html)至總會的婚姻狀態代碼。
147	UK Core Patient	fhir.r4.ukcore.stu1#1.0.4	R4	Defines 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.
148	UKCoreAccessPatientIndexPatient	uk-core-access#current	R4	UK Core Access Patient resource profile for patient index lookup, supporting basic data for identification
149	US Core Patient Profile	hl7.fhir.us.core#current	R4	The 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.
150	US Public Health Patient	hl7.fhir.us.ecr#current	R4	This 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
151	US Public Health Patient	hl7.fhir.us.ph-library#current	R4	This 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
152	US Public Health Patient	hl7.fhir.us.ph-library#current	R4	This Patient profile represents a US Public Health Patient.
153	US Public Health Patient	hl7.fhir.us.central-cancer-registry-reporting#current	R4	This 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
154	US Veteran	hl7.fhir.us.military-service#current	R4	US 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).
155	WHO Patient	who.fhir.anc-cds#current	R4	WHO Patient
156	WHO-Core Patient	who.fhir.core#current	R4

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

Patient

I D

Patient.id

C F

C D

Patient.animal

Patient.deceasedDateTime

Patient.deceasedDateTime.extension

Patient.deceasedBoolean

Patient.meta

Patient.meta.tag

Patient.meta.security

S C (2)

Patient.meta.security.code

B M

Patient.meta.security.system

C F

Patient.meta.source

Patient.meta.versionId

Patient.meta.extension

S C (2)

Patient.meta.extension.value[x]

Patient.meta.extension.url

Patient.meta.profile

C D

S C F D (2)

S C F (2)

Patient.meta.lastUpdated

C D

Patient.implicitRules

C D

Patient.language

D B M

Patient.text

Patient.contained

Patient.extension

S (4)

S C

S (5)

S C D (3)

C (3)

S D (10)

S (4)

S D (3)

S C D (3)

S C (5)

S C B M (5)

S C I D (5)

S (3)

S C

S C D (2)

S C (3)

S C (4)

S D (2)

S C (2)

S C

S C (4)

S C D

S C (5)

S D (2)

S C (9)

S C (8)

S C (11)

S C D (3)

S C D (5)

S C (10)

S C

S C (2)

S C D (2)

S C

S C (6)

S C (5)

S C (4)

S C

S C D B M (7)

S C (4)

S C

S C D (5)

S (2)

S C (2)

S C (3)

S C (2)

S C

S C (4)

S C D (3)

S C D (9)

S C (6)

S C (7)

S C (6)

S C

S C B M (5)

S C (5)

Patient.extension.id

C (6)

Patient.extension.url

(7)

Patient.extension.value[x]

S (3)

B M (2)

B M

D (3)

Patient.extension.value[x].text

C (4)

Patient.extension.value[x].coding

C (4)

Patient.extension.value[x].coding.userSelected

C (4)

Patient.extension.value[x].coding.display

C (4)

Patient.extension.value[x].coding.code

C (4)

Patient.extension.value[x].coding.version

C (4)

Patient.extension.value[x].coding.system

C (4)

Patient.extension.value[x].extension

C (3)

Patient.extension.value[x].country

B M

Patient.extension.value[x].state

B M

Patient.extension.value[x].city

Patient.extension.value[x].city.extension

S C (2)

Patient.extension.extension

S (2)

S D B M (2)

S C (5)

S C (2)

S C (4)

Patient.extension.extension.url

(2)

Patient.extension.extension.id

C (2)

Patient.extension.extension.valuePeriod

Patient.extension.extension.valueCodeableConcept

S B M

Patient.extension.extension.value[x]

(2)

B M

C F (2)

F (2)

Patient.extension.extension.value[x].text

C (2)

Patient.extension.extension.value[x].coding

C (2)

Patient.extension.extension.value[x].coding.userSelected

C (2)

Patient.extension.extension.value[x].coding.display

C (2)

Patient.extension.extension.value[x].coding.code

C (2)

Patient.extension.extension.value[x].coding.version

C (2)

Patient.extension.extension.value[x].coding.system

C (2)

Patient.extension.extension.value[x].id

C (2)

Patient.extension.valueCodeableConcept

B M

S C B M (2)

Patient.extension.valueCodeableConcept.coding

Patient.extension.valueCodeableConcept.coding.code

Patient.extension.valueCodeableConcept.coding.system

Patient.modifierExtension

C D

Patient.identifier

S (2)

S C (4)

S C

S C (4)

S D (2)

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 (2)

S F (3)

S C F (3)

S (3)

C D

S C (2)

S C (6)

S C (2)

C D

S C D (2)

C D

S C F D (2)

C I

S C (7)

S C (3)

S C D (3)

S C (2)

S (2)

S C D (2)

S D (5)

S C (3)

S C (2)

S C

C D

S C

S C D (3)

S C D (2)

S D (3)

S C (2)

S C (8)

S C (3)

S (2)

S C (2)

S (2)

S C D (2)

C D

S C (2)

S C (4)

S C D (3)

S C (2)

S C (4)

S C (2)

S C D (5)

S C (2)

Patient.identifier.id

C (2)

D (4)

Patient.identifier.use

C F

C F (2)

B M

C (2)

C F

C (2)

C F

F D B M (4)

Patient.identifier.assigner

C D

C (2)

D (4)

Patient.identifier.assigner.display

Patient.identifier.extension

C (2)

S C D (8)

S (2)

D (4)

S C (2)

S C

Patient.identifier.extension.value[x]

C F

Patient.identifier.type

C F B M (3)

C (4)

D B M

C F

C (5)

C B M

C (2)

C D B M

C B M

C F D (3)

C F

B M

C F (2)

C F

C F D (2)

C F

C D B M (4)

Patient.identifier.type.id

D (4)

Patient.identifier.type.text

C (2)

Patient.identifier.type.extension

S C D (2)

Patient.identifier.type.coding

C (4)

C (5)

S C D (2)

Patient.identifier.type.coding.userSelected

C (2)

Patient.identifier.type.coding.version

C (2)

Patient.identifier.type.coding.display

C F (2)

Patient.identifier.type.coding.code

C F (4)

C F (5)

C F

C F D

C B M

C F (2)

C D

C F (4)

Patient.identifier.type.coding.code.extension

S C (2)

Patient.identifier.type.coding.system

C F (4)

C F (5)

C F

C F D

C F (2)

C F D

C F (4)

Patient.identifier.system

C F

C B M

C F

C F (6)

C F (2)

C F

C F D (4)

F (2)

C F

C (2)

C F (2)

C B M

C (3)

C F B M (7)

C (2)

C F

C F (2)

C D

C F

C F (3)

C F D (4)

C F

C (2)

Patient.identifier.value

(2)

C D

C (6)

C D (2)

C D

C D (4)

C (2)

C (3)

C I D (2)

C (2)

C I (3)

C (2)

C D (4)

C (2)

Patient.identifier.period

C (2)

D (4)

Patient.active

C F

Patient.name

C I D

S C D (3)

S C (2)

S C D (3)

C D

C I

S C (2)

S C D (2)

C D

C I

C I D

C I

S C (3)

C I

C I D

S C (2)

S C I D (5)

C I

Patient.name.id

D (4)

Patient.name.extension

S C

S C D B M

D (4)

S C

Patient.name.extension.value[x]

C F

Patient.name.extension.valueCode

Patient.name.suffix

C D (4)

Patient.name.prefix

C (2)

C D (4)

Patient.name.use

C F D (2)

C F

C F (3)

C F

C F (2)

C F D B M (4)

Patient.name.given

C D (2)

C (3)

C D

C D (4)

Patient.name.given.extension

S C

S C (2)

Patient.name.family

C D

C D (2)

C (3)

C D

C D (4)

Patient.name.family.extension

S C

S C D (2)

S C (2)

Patient.name.period

D (4)

Patient.name.period.end

Patient.name.text

C (2)

C D

C D (4)

Patient.telecom

S C (3)

S C (4)

S (2)

S (3)

S C (2)

S C (3)

Patient.telecom.rank

Patient.telecom.id

Patient.telecom.extension

S C D (3)

S C (2)

S C

S C (3)

S C

Patient.telecom.extension.value[x]

C F

Patient.telecom.period

Patient.telecom.use

D B M

B M

Patient.telecom.system

C F (2)

F (2)

D B M

C F

C D B M

C B M

C F (2)

F (2)

C F (2)

Patient.telecom.system.extension

S C (2)

Patient.telecom.value

(2)

I D

C D

Patient.gender

C B M

C D

B M

C D

B M

C B M

B M

C D

C D B M

B M

I D

B M

C D

C D B M

C B M

Patient.gender.extension

S C D (2)

S C (2)

S C

S C (2)

S C

Patient.gender.extension.value[x]

C F

Patient.gender.extension.valueCodeableConcept

S B M

Patient.birthDate

C I

C D

C I

C D

Patient.birthDate.extension

S (2)

S D (3)

S (2)

S C (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

S C (2)

S C

Patient.birthDate.extension.value[x]

C F

Patient.deceased[x]

S (3)

S D (3)

S C D (2)

S C (3)

S C D (2)

S C (2)

C F

Patient.deceased[x].extension

S D (2)

S C

Patient.address

S C (2)

I D

C D

Patient.address.type

Patient.address.id

Patient.address.text

C D

Patient.address.period

Patient.address.district

I D

Patient.address.district.extension

S C D (2)

Patient.address.extension

S C (2)

S C (7)

S C

S C D (2)

S C (4)

S C

S C (2)

S C D

S C D (3)

S C D

S C

S C D (2)

S C

S C D

Patient.address.extension.value[x]

C F

Patient.address.extension.url

Patient.address.use

C F

Patient.address.postalCode

I D

Patient.address.state

B M

I D

C B M

B M

Patient.address.state.extension

S C

Patient.address.city

I D

Patient.address.city.extension

S C D (2)

Patient.address.country

B M

C D B M

Patient.address.country.extension

S C (2)

Patient.address.line

C D

Patient.maritalStatus

D B M

B M

D B M

C B M

B M

D B M

B M

C B M

Patient.maritalStatus.id

Patient.maritalStatus.coding

S C (3)

Patient.maritalStatus.coding.userSelected

Patient.maritalStatus.coding.version

Patient.maritalStatus.coding.extension

Patient.maritalStatus.coding.id

Patient.maritalStatus.coding.display

(2)

Patient.maritalStatus.coding.code

C (2)

Patient.maritalStatus.coding.system

C F (2)

Patient.maritalStatus.text

Patient.maritalStatus.extension

S C

Patient.maritalStatus.extension.value[x]

B M

Patient.multipleBirth[x]

S C (2)

Patient.multipleBirth[x].extension

S C D

S C

Patient.photo

C D

Patient.photo.hash

Patient.photo.size

Patient.photo.url

Patient.photo.data

Patient.photo.contentType

Patient.contact

S C (2)

S C (4)

C D

Patient.contact.id

Patient.contact.extension

S (2)

S C D (2)

S C (3)

Patient.contact.modifierExtension

Patient.contact.relationship

B M

C F (3)

C B M

S C B M (3)

S D B M (3)

B M

D B M

B M

Patient.contact.relationship.extension

Patient.contact.relationship.id

Patient.contact.relationship.text

(2)

Patient.contact.relationship.coding

(2)

Patient.contact.relationship.coding.userSelected

Patient.contact.relationship.coding.version

Patient.contact.relationship.coding.extension

Patient.contact.relationship.coding.id

Patient.contact.relationship.coding.display

(2)

Patient.contact.relationship.coding.code

C F

C (2)

Patient.contact.relationship.coding.system

C F (2)

Patient.contact.name

C (2)

C D

Patient.contact.name.period

Patient.contact.name.suffix

Patient.contact.name.prefix

Patient.contact.name.text

Patient.contact.name.id

Patient.contact.name.extension

S C

Patient.contact.name.extension.value[x]

C F

Patient.contact.name.extension.valueCode

Patient.contact.name.given

C D

Patient.contact.name.family

C D

Patient.contact.name.family.extension

S C D (2)

Patient.contact.name.use

F D

D B M

Patient.contact.telecom

Patient.contact.telecom.period

Patient.contact.telecom.rank

Patient.contact.telecom.use

D B M

Patient.contact.telecom.extension

S C

Patient.contact.telecom.extension.value[x]

C F

Patient.contact.telecom.id

Patient.contact.telecom.system

C D B M

Patient.contact.telecom.system.extension

S C (2)

Patient.contact.telecom.value

C D

Patient.contact.address

Patient.contact.address.extension

S C

Patient.contact.address.extension.value[x]

C F

Patient.contact.gender

B M

D B M

Patient.contact.organization

Patient.contact.organization.identifier

Patient.contact.organization.identifier.assigner

Patient.contact.period

Patient.communication

S C (2)

Patient.communication.id

Patient.communication.extension

S D (3)

S C (2)

S C

Patient.communication.extension.extension

S (2)

S C (3)

Patient.communication.extension.extension.value[x]

D (2)

Patient.communication.extension.extension.valueCoding

S B M (2)

Patient.communication.modifierExtension

Patient.communication.language

C B M

B M

D B M

B M

C B M

D B M

B M

Patient.communication.language.text

Patient.communication.language.extension

S C

Patient.communication.language.extension.value[x]

C F

Patient.communication.language.id

Patient.communication.language.coding

Patient.communication.language.coding.userSelected

Patient.communication.language.coding.version

Patient.communication.language.coding.extension

Patient.communication.language.coding.id

Patient.communication.language.coding.display

Patient.communication.language.coding.code

Patient.communication.language.coding.system

C F

Patient.communication.preferred

C F

Patient.generalPractitioner

S C (2)

S C (4)

S C D (2)

Patient.generalPractitioner.type

Patient.generalPractitioner.id

Patient.generalPractitioner.extension

S C (2)

S C D

Patient.generalPractitioner.identifier

Patient.generalPractitioner.identifier.assigner

Patient.generalPractitioner.identifier.period

Patient.generalPractitioner.identifier.value

Patient.generalPractitioner.identifier.system

C F

Patient.generalPractitioner.identifier.type

Patient.generalPractitioner.identifier.type.text

Patient.generalPractitioner.identifier.type.coding

Patient.generalPractitioner.identifier.type.coding.userSelected

Patient.generalPractitioner.identifier.type.coding.display

C F

Patient.generalPractitioner.identifier.type.coding.code

C F

Patient.generalPractitioner.identifier.type.coding.version

Patient.generalPractitioner.identifier.type.coding.system

C F

Patient.generalPractitioner.identifier.type.coding.extension

Patient.generalPractitioner.identifier.type.coding.id

Patient.generalPractitioner.identifier.type.extension

Patient.generalPractitioner.identifier.type.id

Patient.generalPractitioner.identifier.use

Patient.generalPractitioner.identifier.extension

Patient.generalPractitioner.identifier.id

Patient.generalPractitioner.display

Patient.generalPractitioner.reference

Patient.managingOrganization

C D

Patient.managingOrganization.display

Patient.managingOrganization.identifier

Patient.managingOrganization.identifier.assigner

Patient.managingOrganization.type

Patient.managingOrganization.reference

Patient.link

S C (2)

C D

Patient.link.id

Patient.link.extension

Patient.link.modifierExtension

Patient.link.other

Patient.link.other.identifier

Patient.link.other.identifier.assigner

Patient.link.type

D B M

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