Intersection of http://medcomehmi.dk/ig/eer/StructureDefinition/eer-ap-technical-details and http://medcomehmi.dk/ig/eer/StructureDefinition/eer-ap-technical-details

This is the set of resources that conform to both EER AP Technical Details (http://medcomehmi.dk/ig/eer/StructureDefinition/eer-ap-technical-details) and EER AP Technical Details (http://medcomehmi.dk/ig/eer/StructureDefinition/eer-ap-technical-details).

Structure

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
Device		0..*		Item used in healthcare
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
contained		0..*	Resource	Contained, inline Resources
extension		1..*	Extension	Extension
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	1..*	Identifier	Instance identifier
status	?!SΣ	1..1	code	If the AP is not 'active' it won't be registered in the SMP Binding: ?? (required): The availability status of the device.
manufacturer	S	1..1	string	Name of device manufacturer
deviceName	S	1..1	BackboneElement	Should follow this format: [owner of device] [type of device] e.g. 'Aarhus Kommune AP'
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
name		1..1	string	The name of the device and the name of the organization operating the device. Example: 'Aarhus AP - KIT'
type		1..1	code	The name should be user friendly as it is used to distinguish APs in the SMP Binding: ?? (required): The type of name the device is referred by.
type	S	1..1	CodeableConcept	The kind or type of device Binding: ?? (required)
owner	S	1..1	Reference(EER AP Organization Owner | #sd-7-eer-ap-organization-owner-eer-ap-organization-owner)	Organization responsible for device
contact		1..*	ContactPoint	The contact details, which will be included in the SMP registration. Used for troubleshooting and support
extension		0..*	Extension	Additional content defined by implementations
system	Σ	1..1	code	phone | fax | email | pager | url | sms | other Binding: ?? (required): Telecommunications form for contact point.
value	Σ	1..1	string	The actual contact point details
use	?!Σ	0..1	code	home | work | temp | old | mobile - purpose of this contact point Binding: ?? (required): Use of contact point.
rank	Σ	0..1	positiveInt	Specify preferred order of use (1 = highest)
period	Σ	0..1	Period	Time period when the contact point was/is in use
url		1..1	uri	The technical eDelivery URL address of the endpoint. This is the address that is used in the SMP
note		0..*	Annotation	Device notes and comments
Documentation for this format