DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). 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) Practitioner Profile vs QICore-Practitioner

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
PractitionerStructureDefinition U.S. Data Access Framework (DAF) Practitioner Profile has a constraint that is not found in QICore-Practitioner and it is uncertain whether they are compatible (exists(f:name) or exists(f:identifier))
Notes about differences (e.g. definitions)
PractitionerElements differ in definition for short:
"DAF Practitioner"
"A person with a formal responsibility in the provisioning of healthcare or related services"
PractitionerElements differ in definition for definition:
"This is basic constraint on provider for use in DAF resources."
"A person who is directly or indirectly involved in the provisioning of healthcare."
Practitioner.identifierElements differ in definition for requirements:
"Either id or name is needed."
"Often, specific identities are assigned for the agent."
Practitioner.identifier.systemElements differ in definition for short:
"NPI could be used as the identifier system in the US."
"The namespace for the identifier"
Practitioner.identifier.systemElements differ in definition for definition:
"NPI could be used as the identifier system in the US."
"Establishes the namespace in which set of possible id values is unique."
Practitioner.name.givenElements differ in definition for comments:
"Can be first and middle name or initial."
"If only initials are recorded, they may be used in place of the full name. Not called "first name" since given names do not always come first."

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
.. Practitioner I0..*Practitionerleft: DAF Practitioner; right: A person with a formal responsibility in the provisioning of healthcare or related services
inv-1: Shall havePractitioner.name and/or Practitioner.identifier.
... 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 S1..1NarrativeText summary of the resource, for human interpretation
.... extension 0..*ExtensionAdditional Content defined by implementations
.... status S1..1codegenerated | extensions | additional | empty
Binding: NarrativeStatus (required)
.... div I1..1xhtmlLimited xhtml content
txt-2: The narrative SHALL have some non-whitespace content
txt-1: The narrative SHALL contain only the basic html formatting elements described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
txt-3: The narrative SHALL contain only the basic html formatting attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
... contained 0..*ResourceContained, inline Resources
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierA identifier for the person as this agent
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑1..1urileft: NPI could be used as the identifier system in the US.; right: The namespace for the identifier
Example: NPI could be used as the identifier system in the US.
.... value S ∑1..1stringThe 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 ∑0..1booleanWhether this practitioner's record is in active use
... name S ∑0..1HumanNameA name associated with the person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
.... text ∑0..1stringText representation of the full name
.... family S ∑1..*stringFamily name (often called 'Surname')
.... given S ∑0..2stringGiven names (not always 'first'). Includes middle names
.... prefix S ∑0..1stringParts that come before the name
.... suffix S ∑0..1stringParts that come after the name
.... period ∑0..1PeriodTime period when name was/is in use
... telecom S ∑0..*ContactPointA contact detail for the practitioner
.... system S ∑1..1codephone | fax | email | pager | other
Binding: ContactPointSystem (required)
.... value S ∑1..1stringThe actual contact point details
.... use ?! ∑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
... address ∑0..*AddressWhere practitioner can be found/visited
... gender S ∑0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate ∑0..1dateThe date on which the practitioner was born
... photo 0..*AttachmentImage of the person
... practitionerRole S0..*BackboneElementRoles/organizations the practitioner is associated with
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... managingOrganization S0..1Reference(DAF-Organization)Organization where the roles are performed
.... role S ∑0..1CodeableConceptRoles which this practitioner may perform
Binding: PractitionerRole (example)
.... specialty S ∑0..*CodeableConceptSpecific specialty of the practitioner
Binding: PractitionerSpecialty (example)
..... coding ∑0..*CodingCode defined by a terminology system
..... text ∑0..1stringPlain text representation of the concept
.... period S ∑0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
.... location 0..*Reference(QICore-Location)The location(s) at which this practitioner provides care
.... healthcareService 0..*Reference(HealthcareService)The list of healthcare services that this worker provides for this role's Organization/Location(s)
... qualification 0..*BackboneElementQualifications obtained by training and certification
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... identifier 0..*IdentifierAn identifier for this qualification for the practitioner
.... code 1..1CodeableConceptCoded representation of the qualification
Binding: ANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2 (example)
.... period 0..1PeriodPeriod during which the qualification is valid
.... issuer 0..1Reference(QICore-Organization)Organization that regulates and issues the qualification
... communication 0..*CodeableConceptA language the practitioner is able to use in patient communication
Binding: IETF BCP-47 (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
.. Practitioner 0..*Practitionerleft: DAF Practitioner; right: A person with a formal responsibility in the provisioning of healthcare or related 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 S0..1NarrativeText summary of the resource, for human interpretation
.... extension 0..*ExtensionAdditional Content defined by implementations
.... status S1..1codegenerated | extensions | additional | empty
Binding: NarrativeStatus (required)
.... div I1..1xhtmlLimited xhtml content
txt-2: The narrative SHALL have some non-whitespace content
txt-1: The narrative SHALL contain only the basic html formatting elements described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
txt-3: The narrative SHALL contain only the basic html formatting attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
... contained 0..*ResourceContained, inline Resources
... practitioner-classification 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/practitioner-classification
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierA identifier for the person as this agent
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑0..1urileft: NPI could be used as the identifier system in the US.; right: The namespace for the identifier
Example: NPI could be used as the identifier system in the US.
.... value S ∑0..1stringThe 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 ∑0..1booleanWhether this practitioner's record is in active use
... name S ∑0..1HumanNameA name associated with the person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! ∑0..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
.... text ∑0..1stringText representation of the full name
.... family S ∑0..*stringFamily name (often called 'Surname')
.... given S ∑0..*stringGiven names (not always 'first'). Includes middle names
.... prefix S ∑0..*stringParts that come before the name
.... suffix S ∑0..*stringParts that come after the name
.... period ∑0..1PeriodTime period when name was/is in use
... telecom S ∑0..*ContactPointA contact detail for the practitioner
.... us-core-direct S0..1booleanExtension
URL: http://hl7.org/fhir/StructureDefinition/us-core-direct
.... system S ∑0..1codephone | fax | email | pager | other
Binding: ContactPointSystem (required)
.... value S ∑0..1stringThe actual contact point details
.... use ?! ∑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
... address ∑0..*AddressWhere practitioner can be found/visited
... gender S ∑0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate ∑0..1dateThe date on which the practitioner was born
... photo 0..*AttachmentImage of the person
... practitionerRole S0..*BackboneElementRoles/organizations the practitioner is associated with
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... managingOrganization S0..1Reference(#2)Organization where the roles are performed
.... role S ∑0..1CodeableConceptRoles which this practitioner may perform
Binding: PractitionerRole (example)
.... specialty S ∑0..*CodeableConceptSpecific specialty of the practitioner
Binding: PractitionerSpecialty (example)
..... practitioner-primaryInd 0..1booleanExtension
URL: http://hl7.org/fhir/StructureDefinition/practitioner-primaryInd
..... coding ∑0..*CodingCode defined by a terminology system
..... text ∑0..1stringPlain text representation of the concept
.... period S ∑0..1PeriodThe period during which the practitioner is authorized to perform in these role(s)
.... location 0..*Reference(Location)The location(s) at which this practitioner provides care
.... healthcareService 0..*Reference(HealthcareService)The list of healthcare services that this worker provides for this role's Organization/Location(s)
... qualification 0..*BackboneElementQualifications obtained by training and certification
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... identifier 0..*IdentifierAn identifier for this qualification for the practitioner
.... code 1..1CodeableConceptCoded representation of the qualification
Binding: ANZSCO -- Australian and New Zealand Standard Classification of Occupations, 2013, Version 1.2 (example)
.... period 0..1PeriodPeriod during which the qualification is valid
.... issuer 0..1Reference(Organization)Organization that regulates and issues the qualification
... communication 0..*CodeableConceptA language the practitioner is able to use in patient communication
Binding: IETF BCP-47 (required)

doco Documentation for this format