STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). 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) Location Profile vs QICore-Location

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)
Notes about differences (e.g. definitions)
Location.address.postalCodeElements differ in definition for short:
"US Zip Codes"
"Postal code for area"
Location.address.postalCodeElements differ in definition for definition:
"US Zip Codes."
"A postal code designating a region defined by the postal service."

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
.. Location 0..*LocationDetails and position information for a physical place
... 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
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierUnique code or number identifying the location to its users
... status ?! S∑0..1codeactive | suspended | inactive
Binding: LocationStatus (required)
... name S ∑1..1stringName of the location as used by humans
... description ∑0..1stringAdditional details about the location that could be displayed as further information to identify the location beyond its name
... mode ?! S∑0..1codeinstance | kind
Binding: LocationMode (required)
... type S ∑0..1CodeableConceptType of function performed
Binding: ServiceDeliveryLocationRoleType (extensible)
... telecom S0..*ContactPointContact details of the location
... address S0..1AddressPhysical location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... 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..2stringStreet 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..1stringleft: US Zip Codes; right: Postal code for area
Example: 9132
.... country ∑0..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"}
... physicalType ∑0..1CodeableConceptPhysical form of the location
Binding: LocationType (example)
... position 0..1BackboneElementThe absolute geographic location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization S ∑0..1Reference(DAF-Organization)Organization responsible for provisioning and upkeep
... partOf 0..1Reference(QICore-Location)Another Location this one is physically part of

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
.. Location 0..*LocationDetails and position information for a physical place
... 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
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierUnique code or number identifying the location to its users
... status ?! S∑0..1codeactive | suspended | inactive
Binding: LocationStatus (required)
... name S ∑0..1stringName of the location as used by humans
... description ∑0..1stringAdditional details about the location that could be displayed as further information to identify the location beyond its name
... mode ?! S∑0..1codeinstance | kind
Binding: LocationMode (required)
... type S ∑0..1CodeableConceptType of function performed
Binding: ServiceDeliveryLocationRoleType (extensible)
... telecom S0..*ContactPointContact details of the location
... address S0..1AddressPhysical location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... 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..1stringleft: US Zip Codes; right: Postal code for area
Example: 9132
.... country ∑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"}
... physicalType ∑0..1CodeableConceptPhysical form of the location
Binding: LocationType (example)
... position 0..1BackboneElementThe absolute geographic location
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?! ∑0..*ExtensionExtensions that cannot be ignored
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization S ∑0..1Reference(#2)Organization responsible for provisioning and upkeep
... partOf 0..1Reference(Location)Another Location this one is physically part of

doco Documentation for this format