Profile Comparison between http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patient vs https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient

Left:IPA-Patient (http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patient)
Right:BePatient (https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patient' vs 'https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient'
ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '2.1.2'
InformationStructureDefinition.nameValues for name differ: 'IPAPatient' vs 'BePatient'
InformationStructureDefinition.titleValues for title differ: 'IPA-Patient' vs 'BePatient'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-08-02' vs '2024-10-02T14:07:07+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Patient Care Work Group' vs 'eHealth Platform'
InformationStructureDefinition.jurisdictionRemoved the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#BE'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
InformationStructureDefinition.definitionValues for definition differ: 'An identifier for this patient.' vs 'An identifier for this patient. Typically, when SSIN is available it is used. Organizations will most likely want to also include a local identifier, using its own system. A type can be added if needed. When an identifier is given, a consumer SHALL NOT ignore it.'
InformationPatient.identifierElement minimum cardinalities differ: '1' vs '0'
WarningPatient.activeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.definitionValues for definition differ: 'A name associated with the individual.' vs 'A name associated with the individual. It is RECOMMENDED to give at least one familyname and at least one given name when possible and define an 'official' use. When names are given, a consumer SHALL NOT ignore it.'
InformationStructureDefinition.definitionValues for definition differ: 'A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.' vs 'A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. It is RECOMMENDED to at least add one phone or email address with clear indication using the .use element whether it is home use, private use,...'
InformationStructureDefinition.commentValues for comment differ: 'The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a 'hard' error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.' vs 'This is primarily the administrative gender. The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a 'hard' error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex. Special remarks for KMEHR users: Please note gender in KMEHR is typically expressed using CD-SEX. The two values that do not map directly to the HL7 dataset are 'undefined' (use 'other') and 'changed' (use the actual gender)'
WarningPatient.genderElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.definitionValues for definition differ: 'The date of birth for the individual.' vs 'The date of birth for the individual. It is RECOMMENDED to give the birthdate when available.'
WarningPatient.birthDateElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.definitionValues for definition differ: 'Indicates if the individual is deceased or not.' vs 'Indicates if the individual is deceased or not. It is RECOMMENDED to include deceased information when applicable'
InformationStructureDefinition.shortValues for short differ: 'An address for the individual' vs 'An address expressed using postal conventions (as opposed to GPS or other location definition formats)'
InformationStructureDefinition.definitionValues for definition differ: 'An address for the individual.' vs 'An address for the individual. It is RECOMMENDED to include an address when available. When needed to express the availablity of a Patient at home (e.g. only Wednesdays), another solution will be defined.'
InformationStructureDefinition.commentValues for comment differ: 'Patient may have multiple addresses with different uses or applicable periods.' vs 'Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the [Location](http://hl7.org/fhir/R4/location.html#) resource). Special remarks for KMEHR users: Note when .use and .type are used they SHALL use the FHIR defined valuesets as per their required binding level in the FHIR specification. In a KMEHR address, the use was defined by CD-ADDRESS but those values can be found in the FHIR valueset. KMEHR values 'careadress', 'other' and 'vacation' are not directly present in the FHIR address-use table but can be mapped to the value 'temp' in FHIR. In those cases, it is RECOMMENDED to also add a .period. In KMEHR, an address might be expressed using free text or a totally structured approach where the streetname and housenumber are put in separate fields. FHIR prefers a more pragmatic approach where the ‘text’ element is used to print on labels. Also, streetname and number are not separate fields as in KMEHR but in a structural approach are given as one or moren ‘line’ elements. It is however RECOMMENDED to use the Streetname, Housenumber and Postbox extensions to express them seperately. Note the FHIR address also allows to optionally define whether the address is a physical, postal or ‘both’ address using the .type field.'
InformationStructureDefinition.definitionValues for definition differ: 'This field contains a patient's most recent marital (civil) status.' vs 'This field contains a patient's most recent marital (civil) status. It is RECOMMENDED to include this when available. In a Belgian context, the concept ‘civil state’ , Dutch ‘burgerlijke stand’, French ‘état civil’ is more typically used and this might imply a more neutral concept to the reader. In HL7 semantics however this concept is described as ‘marital status’ and it SHALL be understood as the same concept.'
InformationStructureDefinition.definitionValues for definition differ: 'Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).' vs 'Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). Care SHOULD be given when exchanging Patient instances in a purely administrative flow.'
InformationStructureDefinition.definitionValues for definition differ: 'A contact party (e.g. guardian, partner, friend) for the patient.' vs 'A contact party (e.g. guardian, partner, friend) for the patient. It is RECOMMENDED to include this when available and considered relevant for the patientcare. (e.g. a parent of a young patient)'
InformationStructureDefinition.commentValues for comment differ: 'Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.' vs 'Contact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact. Special remarks for KMEHR users: A contact person for the patient is not part of the 'patient' element itself in KMEHR. As such, the base resource of this is considered sufficient here. The KMEHR standard defines a contact as a separate element using a value from the KMEHR CD-ITEM table and an appropriate value from CD-CONTACT-PERSON to describe the relation to the patient in the KMEHR message. When needed, using FHIR, the contactperson is included in the FHIR resource Patient. Use cases implementing this contact SHALL be aware not all information of CD-CONTACT-PERSON is covered by the base valueset. The codesystem ‘https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/CD-CONTACT-PERSON’ SHALL be used to refer to any codes previously used in a KMEHR context that cannot be covered by the base HL7 valueset.'
InformationStructureDefinition.definitionValues for definition differ: 'A language which may be used to communicate with the patient about his or her health.' vs 'A language which may be used to communicate with the patient about his or her health. It is RECOMMENDED to include this when available.'
InformationStructureDefinition.commentValues for comment differ: 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.' vs 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required. Special remarks for KMEHR users: The 'usuallanguage' element in a KMEHR message only refers to the use of W3C language codes. As such, the language codes as proposed in the FHIR standard should not present any interoperability issue. Note the KMEHR element implies it is the language usally used by the patient. As such, when this element from KMEHR would be mapped to a FHIR resource, the communication.preferred Boolean SHOULD be used.'
InformationStructureDefinition.definitionValues for definition differ: 'Patient's nominated care provider.' vs 'Patient's nominated care provider. Take note this does not automatically imply any legal form of therapeutic link or consent relationship with this GP. It is RECOMMENDED to include this when available if the flow is in any way medical. Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this GP can be found. Alternatively, there is only an internal reference and the GP is included as a ‘contained resource’ (cfr. the HL7 FHIR specifications in what cases this applies).'
InformationStructureDefinition.commentValues for comment differ: 'This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a 'fly-in/fly-out' worker that has the onsite GP also included with his home GP to remain aware of medical issues. Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.' vs 'This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a 'fly-in/fly-out' worker that has the onsite GP also included with his home GP to remain aware of medical issues. Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type. Special remarks for KMEHR users: The general practioner is in many KMEHR use cases known by being the author or sender of the message. This is however a functionally different concept from the generalPractioner as it is defined in the FHIR resource. (Consult the published definition on the HL7 webpage) It is also possible in KMEHR to add a general practioner via an item and using the correct value from CD-ITEM. That way is functionally closer to the general practioner referenced here. Note in the FHIR base definition of this element that the scope of this element might be wider then just the general practicioner.'
InformationStructureDefinition.definitionValues for definition differ: 'Organization that is the custodian of the patient record.' vs 'Organization that is the custodian of the patient record. This SHOULD be included when available.Please note this is an element of the Reference datatype. This means when it is available it will contain either a relative or absolute URL where this Organization can be found. Alternatively, there is only an internal reference and the Organization is included as a ‘contained resource’ (cfr. the HL7 FHIR specifications in what cases this applies).'
InformationStructureDefinition.commentValues for comment differ: 'There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).' vs 'There is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association). Special remarks for KMEHR users: The reference to the managing organization is the organization that is the custodian of the patient record. As there is no explicit ‘author of this record’ – like in a KMEHR message – this element functionally refers to the organization in charge. (Which might also be a GP practice of an individual.)'
WarningPatient.linkElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Patient
      .copyrightUsed by permission of HL7 International all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International all rights reserved Creative Commons License'
      .date2022-08-022024-10-02T14:07:07+00:00
      • Values Differ
      .descriptionMinimum 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.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.)
      • Values Differ
      .experimentalfalse
      • Removed the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
          • Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
          ..jurisdiction[1]urn:iso:std:iso:3166#BE
          • Added the item 'urn:iso:std:iso:3166#BE'
          .kindresource
            .nameIPAPatientBePatient
            • Values Differ
            .publisherHL7 International - Patient Care Work GroupeHealth Platform
            • Values Differ
            .purpose
              .statusactivedraft
              • Values Differ
              .titleIPA-PatientBePatient
              • Values Differ
              .typePatient
                .urlhttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patienthttps://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-patient
                • Values Differ
                .version1.0.02.1.2
                • Values Differ

                Structure

                NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                .. Patient 0..*PatientInformation about an individual or animal receiving health care services
                		0..*PatientInformation about an individual or animal receiving health care services
                  ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                    ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                      ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                        ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                          ... contained 0..*ResourceContained, inline Resources
                          		0..*ResourceContained, inline Resources
                            ... extension 0..*ExtensionAdditional content defined by implementations
                            		0..*ExtensionExtension
                            Slice: Unordered, Open by value:url
                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                              		?!0..*ExtensionExtensions that cannot be ignored
                                ... identifier SΣC1..*IdentifierAn identifier for this patient
                                ipa-pat-1: At least one of Patient.identifier.system or Patient.identifier.type or Patient.identifier.assigner SHALL be present
                                		SΣC0..*IdentifierAn identifier for this patient
                                Slice: Unordered, Open by value:system
                                be-inv-SSIN: SINN contains 11 digits without interpunction
                                • Element minimum cardinalities differ: '1' vs '0'
                                .... id 0..1stringUnique id for inter-element referencing
                                • Removed this element
                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                Slice: Unordered, Open by value:url
                                • Removed this element
                                .... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
                                Binding: ?? (required): Identifies the purpose for this identifier, if known .

                                • Removed this element
                                .... type Σ0..1CodeableConceptDescription of identifier
                                Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

                                • Removed this element
                                .... system Σ0..1uriThe namespace for the identifier value
                                Example General: http://www.acme.com/identifiers/patient
                                • Removed this element
                                .... value SΣ1..1stringThe value that is unique within the system.
                                Example General: 123456
                                • Removed this element
                                .... period Σ0..1PeriodTime period when id is/was valid for use
                                • Removed this element
                                .... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
                                • Removed this element
                                ... active ?!SΣC0..1booleanWhether this patient's record is in active use
                                ipa-pat-4: If Patient.link is present, then Patient.active SHALL be present                                		?!Σ0..1booleanWhether this patient's record is in active use
                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                ... name SΣC0..*HumanNameA name associated with the patient
                                ipa-pat-2: Either Patient.name.given and/or Patient.name.family and/or Patient.name.text SHALL be present or a Data Absent Reason Extension SHALL be present.
                                ipa-pat-3: To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present.
                                		SΣ0..*HumanNameA name associated with the patient
                                  ... telecom Σ0..*ContactPointA contact detail for the individual
                                  		Σ0..*ContactPointA contact detail for the individual
                                    ... gender SΣ0..1codemale | female | other | unknown
                                    Binding: ?? (required): The gender of a person used for administrative purposes.

                                    		Σ0..1codemale | female | other | unknown
                                    Binding: ?? (required): The gender of a person used for administrative purposes.

                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                    ... birthDate SΣ0..1dateThe date of birth for the individualΣ0..1dateThe date of birth for the individual
                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                    .... id 0..1stringxml:id (or equivalent in JSON)
                                    • Added this element
                                    .... Slices for extension 0..*ExtensionExtension
                                    Slice: Unordered, Open by value:url
                                    • Added this element
                                    .... value 0..1datePrimitive value for date
                                    • Added this element
                                    ... deceased[x] ?!Σ0..1boolean, dateTimeIndicates if the individual is deceased or not?!Σ0..1boolean, dateTimeIndicates if the individual is deceased or not
                                      ... address Σ0..*AddressAn address for the individual
                                      		0..*??An address expressed using postal conventions (as opposed to GPS or other location definition formats)
                                        ... maritalStatus 0..1CodeableConceptMarital (civil) status of a patient
                                        Binding: ?? (extensible): The domestic partnership status of a person.

                                        		0..1CodeableConceptMarital (civil) status of a patient
                                        Binding: ?? (required)
                                          ... multipleBirth[x] 0..1boolean, integerWhether patient is part of a multiple birth0..1boolean, integerWhether patient is part of a multiple birth
                                            ... photo 0..*AttachmentImage of the patient
                                            		0..*AttachmentImage of the patient
                                              ... contact C0..*BackboneElementA contact party (e.g. guardian, partner, friend) for the patient
                                              pat-1: SHALL at least contain a contact's details or a reference to an organization
                                              		C0..*BackboneElementA contact party (e.g. guardian, partner, friend) for the patient
                                              pat-1: SHALL at least contain a contact's details or a reference to an organization
                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                  		0..*ExtensionAdditional content defined by implementations
                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                    		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                      .... relationship 0..*CodeableConceptThe kind of relationship
                                                      Binding: ?? (extensible): The nature of the relationship between a patient and a contact person for that patient.


                                                      		0..*CodeableConceptThe kind of relationship
                                                      Binding: ?? (extensible)
                                                        .... name 0..1HumanNameA name associated with the contact person0..1HumanNameA name associated with the contact person
                                                          .... telecom 0..*ContactPointA contact detail for the person
                                                          		0..*ContactPointA contact detail for the person
                                                            .... address 0..1AddressAddress for the contact person0..1AddressAddress for the contact person
                                                              .... gender 0..1codemale | female | other | unknown
                                                              Binding: ?? (required): The gender of a person used for administrative purposes.

                                                              		0..1codemale | female | other | unknown
                                                              Binding: ?? (required): The gender of a person used for administrative purposes.

                                                                .... organization C0..1Reference(Organization)Organization that is associated with the contactC0..1Reference(Organization)Organization that is associated with the contact
                                                                  .... period 0..1PeriodThe period during which this contact person or organization is valid to be contacted relating to this patient0..1PeriodThe period during which this contact person or organization is valid to be contacted relating to this patient
                                                                    ... communication 0..*BackboneElementA language which may be used to communicate with the patient about his or her health
                                                                    		0..*BackboneElementA language which may be used to communicate with the patient about his or her health
                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                                        		0..*ExtensionAdditional content defined by implementations
                                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                          		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                            .... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
                                                                            Binding: ?? (preferred): A human language.

                                                                            Additional BindingsPurpose
                                                                            ??Max Binding
                                                                            		1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
                                                                            Binding: ?? (preferred): A human language.

                                                                            Additional BindingsPurpose
                                                                            ??Max Binding
                                                                              .... preferred 0..1booleanLanguage preference indicator0..1booleanLanguage preference indicator
                                                                                ... generalPractitioner 0..*Reference(Organization | Practitioner | PractitionerRole)Patient's nominated primary care provider
                                                                                		0..*Reference(BeOrganization | BePractitioner | BePractitionerRole)Patient's nominated primary care provider
                                                                                  ... managingOrganization Σ0..1Reference(Organization)Organization that is the custodian of the patient recordΣ0..1Reference(BeOrganization)Organization that is the custodian of the patient record
                                                                                    ... link ?!SΣC0..*BackboneElementLink to another patient resource that concerns the same actual person
                                                                                    		?!Σ0..*BackboneElementLink to another patient resource that concerns the same actual person
                                                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                      .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                      		0..*ExtensionAdditional content defined by implementations
                                                                                        .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                        		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                          .... other Σ1..1Reference(Patient | RelatedPerson)The other patient or related person resource that the link refers toΣ1..1Reference(Patient | RelatedPerson)The other patient or related person resource that the link refers to
                                                                                            .... type Σ1..1codereplaced-by | replaces | refer | seealso
                                                                                            Binding: ?? (required): The type of link between this patient resource and another patient resource.

                                                                                            		Σ1..1codereplaced-by | replaces | refer | seealso
                                                                                            Binding: ?? (required): The type of link between this patient resource and another patient resource.


                                                                                              doco Documentation for this format