no-basis: Adresseregisteret do not provide a identifier for the Endpoints, so any identifier scheme is apropriate.

no-basis: the connection type should be coded according to http://hl7.org/fhir/ValueSet/endpoint-connection-type. However specific connection types used in Norway can be coded according to http://hl7.no/fhir/ValueSet/no-basis-endpoint-connection-type (amqp, ebxml etc.)

A coded value that represents the technical details of the usage of this endpoint, such as what WSDLs should be used in what way. (e.g. XDS.b/DICOM/cds-hook).

The organization that manages this endpoint (even if technically another organisation is hosting this in the cloud, it is the organisation associated with the data).

no-basis: In Norway this relates to the organization with the responsibility for the data e.g. "dataansvarlig". no-basis recommends the use of logical reference to an organization using ENH or RSH. To describe a top level organization. Departments within an organization could use a different reference scheme defined by the organization.

no-basis: for ebXML and AMQP messages in Norway one is expected to list all mesage types that the endpoint supports using the CodeSystem Meldingens funksjon (OID=8279). Version information (version of the payload document) shold be given in the coding.version element.

The payload type describes the acceptable content that can be communicated on the endpoint.

no-basis: Specific information about payload type and version. Information about the payload type and version for ebxml and amqp messages

The payload type describes the acceptable content that can be communicated on the endpoint.

no-basis: should we list relevant codes for ebXML messages? List appropriate media types for FHIR REST endpoints? XML: application/fhir+xml JSON: application/fhir+json RDF: application/fhir+turtle ebXML messages: text/xml

The mime type to send the payload in - e.g. application/fhir+xml, application/fhir+json. If the mime type is not specified, then the sender could send any content (including no content depending on the connectionType).

The uri that describes the actual end-point to connect to.

no-basis: for ebXML messages in Norway one is expected to use mailto: prefix for the endpoint. For AMQP messages in Norway one is expected to use "ampq://" or "amqps://" prefix. REST endpoints will have "http://" or "https://" prefix.

Example of category. Helsevirksomhet type (OID=9040), identifies the virksomhetstype used in Adresseregisteret. This element is usually not necessary to describe the HealthcareService adequately.

virksomhetstype 9040

no-basis: This element is usually not necessary to describe the HealthcareService adequately. Further coding can be used when common set of SNOMED codes are agreed for healthc care service types.

The specific type of service that may be delivered or performed.

The identification of the Fagområde (OID=8451) code system.

no-basis: In Norway endpoints for communication should be connected to a kommunikasjonspart-Organization identified with HERid and collected from the Norwegian Address register. Endpoints not registered in the Norwegian Address register can use other schemes of connecting endpoints to Organizations, PractitionerRole or HealthcareService.

Technical endpoints providing access to services operated for the specific healthcare services defined at this resource.

Technical endpoints providing access to services operated for the organization.

no-basis don't use this element to reference endpoints registered in the Norwegian Address register (endpoints connected to a kommunikasjonspart in tjenestebasert adressering). Endpoints registered in the Norwegian Address register should only be referenced through a kommunikasjonspart-Organization resource.

no-basis don't use this element to reference endpoints registered in the Norwegian Address register (endpoints connected to a kommunikasjonspart in tjenestebasert adressering). Endpoints registered in the Norwegian Address register should only be referenced through a kommunikasjonspart-Organization resource.

Technical endpoints providing access to services operated for the location.

Specifies the particular kind of document referenced using the codes defined in the valueset 'NoBasisDocumentReferenceType'. Such as:

• A00-1 Epikriser og sammenfatninger
• A01-2 Kriseplan
• A02-2 Individuell plan
• etc.

See valueset 'NoBasisDocumentReferenceType' in the Terminology section for more information on available types

Key metadata element describing the document that describes the exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents.

Specifies the particular kind of composition using the codes defined in the valueset 'NoBasisDocumentReferenceType'. Such as:

• A00-1 Epikriser og sammenfatninger
• A01-2 Kriseplan
• A02-2 Individuell plan
• etc.

See valueset 'NoBasisDocumentReferenceType' in the Terminology section for more information on available types