Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

U.S. Data Access Framework (DAF) Patient Profile vs QICore-Patient

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
(None)
Warnings about the comparison
Patient.address.postalCodeStructureDefinition U.S. Data Access Framework (DAF) Patient Profile has a constraint that is not found in QICore-Patient and it is uncertain whether they are compatible (f:matches(issued,[0-9]{5}(-[0-9]{4}){0,1} ))
Patient.contact.address.postalCodeStructureDefinition U.S. Data Access Framework (DAF) Patient Profile has a constraint that is not found in QICore-Patient and it is uncertain whether they are compatible (f:matches(issued,[0-9]{5}(-[0-9]{4}){0,1} ))
Notes about differences (e.g. definitions)
Patient.identifier.typeElements differ in definition for definition:
"Description of identifier."
"A coded type for the identifier that can be used to determine which identifier to use for a specific purpose."
Patient.identifier.valueElements differ in definition for short:
"The value that is unique within the system."
"The value that is unique"
Patient.identifier.valueElements differ in definition for definition:
"The value that is unique within the system."
"The portion of the identifier typically displayed to the user and which is unique within the context of the system."
Patient.telecom.extensionElements differ in definition for short:
"Additional Content defined by implementations"
"Extension"
Patient.telecom.extensionElements differ in definition for definition:
"May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."
"An Extension"
Patient.address.extensionElements differ in definition for short:
"Additional Content defined by implementations"
"Extension"
Patient.address.extensionElements differ in definition for definition:
"May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."
"An Extension"
Patient.address.extensionElements differ in definition for comments:
"There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone."
"Make general extension."
Patient.address.stateElements differ in definition for binding.description:
"2 letter state list"
"The state or region designation in an address"
Patient.contact.relationshipElements differ in definition for description:
"Type of relationship"
"The nature of the relationship between a patient and a contact person for that patient."
Patient.contact.address.stateElements differ in definition for binding.description:
"2 letter state list"
"The state or region designation in an address"
Patient.contact.address.countryElements differ in definition for short:
"ISO 3166 2 or 3 letter Country Code"
"Country (can be ISO 3166 3 letter code)"
Patient.contact.address.countryElements differ in definition for definition:
"ISO 3166 2 or 3 letter Country Code."
"Country - a nation as commonly understood or generally accepted."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 0..*PatientInformation about an individual or animal receiving health care services
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... birthPlace S0..1AddressExtension
URL: http://hl7.org/fhir/StructureDefinition/birthPlace
... us-core-ethnicity S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-ethnicity
Binding: Ethnicity group (required)
... us-core-race S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-race
Binding: MU Race Value Set (required)
... us-core-religion S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-religion
Binding: v3 Code System ReligiousAffiliation (extensible)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑1..*IdentifierAn identifier for this patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑1..1uriThe namespace for the identifier
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value S ∑1..1stringleft: The value that is unique within the system.; right: The value that is unique
Example: 123456
.... period ∑0..1PeriodTime period when id is/was valid for use
.... assigner ∑0..1Reference(Organization)Organization that issued id (may be just text)
... active ?! S∑0..1booleanWhether this patient's record is in active use
... name S ∑0..*HumanNameA name associated with the patient
... telecom S ∑0..*ContactPointA contact detail for the individual
.... iso21090-preferred 0..1booleanleft: Additional Content defined by implementations; right: Extension
URL: http://hl7.org/fhir/StructureDefinition/iso21090-preferred
.... system S ∑1..1codephone | fax | email | pager | other
Binding: ContactPointSystem (required)
.... value S ∑1..1stringThe actual contact point details
.... use ?! S∑0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... rank ∑0..1positiveIntSpecify preferred order of use (1 = highest)
.... period ∑0..1PeriodTime period when the contact point was/is in use
... gender S ∑0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate S ∑0..1dateThe date of birth for the individual
... deceased[x] ?! S∑0..1boolean, dateTimeIndicates if the individual is deceased or not
... address S ∑0..*AddressAddresses for the individual
.... iso21090-preferred 0..1booleanleft: Additional Content defined by implementations; right: Extension
URL: http://hl7.org/fhir/StructureDefinition/iso21090-preferred
.... use ?! ∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
.... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line S ∑1..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
.... city S ∑1..1stringName of city, town etc.
Example: Erewhon
.... district ∑0..1stringDistrict name (aka county)
Example: Madison
.... state S ∑1..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (required)
.... postalCode S ∑I1..1stringPostal code for area
inv-1: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
.... country S ∑1..1stringCountry (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (required)
.... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... maritalStatus S0..1CodeableConceptMarital (civil) status of a patient
Binding: Marital Status Codes (required)
... multipleBirth[x] S0..1boolean, integerWhether patient is part of a multiple birth
... photo 0..*AttachmentImage of the patient
... contact S I0..*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
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... relationship S0..*CodeableConceptThe kind of relationship
Binding: PatientContactRelationship (required)
.... name S0..1HumanNameA name associated with the contact person
.... telecom S0..*ContactPointA contact detail for the person
.... address S0..1AddressAddress for the contact person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... use ?! S∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
..... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
..... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
..... line S ∑0..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
..... city S ∑0..1stringName of city, town etc.
Example: Erewhon
..... district ∑0..1stringDistrict name (aka county)
Example: Madison
..... state S ∑0..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (required)
..... postalCode S ∑I0..1stringPostal code for area
inv-2: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
..... country S ∑0..1stringleft: ISO 3166 2 or 3 letter Country Code; right: Country (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (required)
..... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
.... gender 0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
.... organization 0..1Reference(QICore-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 patient
... communication S0..*BackboneElementA list of Languages which may be used to communicate with the patient about his or her health
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... language S1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: IETF BCP-47 (required)
.... preferred 0..1booleanLanguage preference indicator
... careProvider S0..*Reference(DAF-Organization | DAF-Pract)Patient's nominated primary care provider
... managingOrganization S ∑0..1Reference(DAF-Organization)Organization that is the custodian of the patient record
... link ?!0..*BackboneElementLink to another patient resource that concerns the same actual person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... other ?!1..1Reference(QICore-Patient)The other patient resource that the link refers to
.... type ?!1..1codereplace | refer | seealso - type of link
Binding: LinkType (required)

doco Documentation for this format

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 0..*PatientInformation about an individual or animal receiving health care services
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... birthPlace S0..1AddressExtension
URL: http://hl7.org/fhir/StructureDefinition/birthPlace
... patient-birthTime S0..1dateTimeExtension
URL: http://hl7.org/fhir/StructureDefinition/patient-birthTime
... patient-cadavericDonor 0..1booleanExtension
URL: http://hl7.org/fhir/StructureDefinition/patient-cadavericDonor
... patient-clinicalTrial 0..*(Complex)Extension
URL: http://hl7.org/fhir/StructureDefinition/patient-clinicalTrial
... patient-disability 0..*CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/patient-disability
Binding: Disability Value Set (preferred)
... patient-mothersMaidenName S0..1stringExtension
URL: http://hl7.org/fhir/StructureDefinition/patient-mothersMaidenName
... patient-nationality 0..*(Complex)Extension
URL: http://hl7.org/fhir/StructureDefinition/patient-nationality
... qicore-patient-militaryService 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/qicore-patient-militaryService
Binding: Military Service Codes (example)
... us-core-ethnicity S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-ethnicity
Binding: Ethnicity group (required)
... us-core-race S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-race
Binding: MU Race Value Set (required)
... us-core-religion S0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-religion
Binding: v3 Code System ReligiousAffiliation (extensible)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierAn identifier for this patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type S ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑0..1uriThe namespace for the identifier
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value S ∑0..1stringleft: The value that is unique within the system.; right: The value that is unique
Example: 123456
.... period ∑0..1PeriodTime period when id is/was valid for use
.... assigner ∑0..1Reference(Organization)Organization that issued id (may be just text)
... active ?! S∑0..1booleanWhether this patient's record is in active use
... name S ∑0..*HumanNameA name associated with the patient
... telecom S ∑0..*ContactPointA contact detail for the individual
.... extension 0..*Extensionleft: Additional Content defined by implementations; right: Extension
.... system S ∑0..1codephone | fax | email | pager | other
Binding: ContactPointSystem (required)
.... value S ∑0..1stringThe actual contact point details
.... use ?! S∑0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... rank ∑0..1positiveIntSpecify preferred order of use (1 = highest)
.... period ∑0..1PeriodTime period when the contact point was/is in use
... gender S ∑0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate S ∑0..1dateThe date of birth for the individual
... deceased[x] ?! S∑0..1boolean, dateTimeIndicates if the individual is deceased or not
... address S ∑0..*AddressAddresses for the individual
.... extension 0..*Extensionleft: Additional Content defined by implementations; right: Extension
.... use ?! ∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
.... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line S ∑0..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
.... city S ∑0..1stringName of city, town etc.
Example: Erewhon
.... district ∑0..1stringDistrict name (aka county)
Example: Madison
.... state S ∑0..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (required)
.... postalCode S ∑0..1stringPostal code for area
Example: 9132
.... country S ∑0..1stringCountry (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (example)
.... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... maritalStatus S0..1CodeableConceptMarital (civil) status of a patient
Binding: Marital Status Codes (required)
... multipleBirth[x] S0..1boolean, integerWhether patient is part of a multiple birth
... photo 0..*AttachmentImage of the patient
... contact S I0..*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
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... relationship S0..*CodeableConceptThe kind of relationship
Binding: PatientContactRelationship (extensible)
.... name S0..1HumanNameA name associated with the contact person
.... telecom S0..*ContactPointA contact detail for the person
.... address S0..1AddressAddress for the contact person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... use ?! S∑0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
..... type ∑0..1codepostal | physical | both
Binding: AddressType (required)
Example: both
..... text ∑0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
..... line S ∑0..*stringStreet name, number, direction & P.O. Box etc.
Example: 137 Nowhere Street
..... city S ∑0..1stringName of city, town etc.
Example: Erewhon
..... district ∑0..1stringDistrict name (aka county)
Example: Madison
..... state S ∑0..1stringSub-unit of country (abbreviations ok)
Binding: USPS Two Letter Alphabetic Codes (required)
..... postalCode S ∑0..1stringPostal code for area
Example: 9132
..... country S ∑0..1stringleft: ISO 3166 2 or 3 letter Country Code; right: Country (can be ISO 3166 3 letter code)
Binding: ISO Country Codes (required)
..... period ∑0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
.... gender 0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
.... organization 0..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 patient
... communication S0..*BackboneElementA list of Languages which may be used to communicate with the patient about his or her health
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... language S1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: IETF BCP-47 (required)
.... preferred 0..1booleanLanguage preference indicator
... careProvider S0..*Reference(#2 | #3)Patient's nominated primary care provider
... managingOrganization S ∑0..1Reference(#2)Organization that is the custodian of the patient record
... link ?!0..*BackboneElementLink to another patient resource that concerns the same actual person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... other ?!1..1Reference(Patient)The other patient resource that the link refers to
.... type ?!1..1codereplace | refer | seealso - type of link
Binding: LinkType (required)

doco Documentation for this format