Union of http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-endpoint and http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-endpoint

This is the set of resources that conform to either of the profiles US Public Health Endpoint (http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-endpoint) and US Public Health Endpoint (http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-endpoint). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Endpoint 0..*left: The technical details of an endpoint that can be used for electronic services; right: US Public Health Endpoint
... 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: ?? (preferred): A human language.
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierIdentifies this endpoint across multiple systems
... status ?!SΣ1..1codeactive | suspended | error | off | entered-in-error | test
Binding: ?? (required): The status of the endpoint.
... connectionType SΣ1..1CodingProtocol/Profile/Standard to be used with this endpoint connection
Binding: ?? (extensible)
... name Σ0..1stringA name that this endpoint can be identified by
... managingOrganization Σ0..1Reference(Organization)Organization that manages this endpoint (might not be the organization that exposes the endpoint)
... contact 0..*ContactPointContact details for source (e.g. troubleshooting)
... period Σ0..1PeriodInterval the endpoint is expected to be operational
... payloadType Σ1..*CodeableConceptThe type of content that may be used at this endpoint (e.g. XDS Discharge summaries)
Binding: ?? (example)
... payloadMimeType Σ0..*codeMimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this)
Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed.
... address SΣ1..1urlThe technical base address for connecting to this endpoint
... header 0..*stringUsage depends on the channel type

doco Documentation for this format