This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Abstract Profiles

These are profiles on resources or data types that describe patterns used by other profiles, but cannot be instantiated directly. I.e. instances can conform to profiles based on these abstract profiles but do not declare conformance to the abstract profiles themselves.

ParekPractitionerRole

PractitionerRole as used in Parek. Used to combine actors of type Practitioner and Organization. Practitioner and Organization are referenced by their Identifier. This is an 'abstract' base profile for ParekRequester and ParekCollector.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Parek Device	Device as used in Parek.
ParekCollector
ParekRequester
ParekServiceRequest	ServiceRecuest as used in Parek.
ParekSpecimen	Specimen as used in Parek.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Organization Id Type VS	Id types for organizations involved in DiagnosticReport/Observation
Person Id Type VS	Id types used to identify persons involved, other than the patient.
Public Id Type VS	Id types used to identify patients
Specimen Type VS	Type og material in specimen.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Organization Id Type CS	Id types used to identify organizations.
Person Id Type CS	Id types used to identify persons involved, other than the patient.
Public Id Type CS	Id types used to identify patients

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

RequesterDefinedUuid

NamingSystem for a required identifier that must be unique. Provides idempotency in case client systems tries to create same resource twice.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

A Device	Example of a device
A Request	Example of ParekServiceRequest
A Specimen	Example of ParekSpecimen
Parek Collector	Example of collector with only organization
Parek Requester	Example of requester with both practitioner and organization