| Normal Services | ||
| Pending Confirmation |
The arrows points from the producer towards the consumer.
Dotted lines are planned, but not implemented, integrations.
Filter or focus service by name
Find APIs by tags
Find services or integrations by keywords
Find services by organization types
| Administrasjon | |
| Barnehage | |
| Barne- og Familietjenester | |
| Bo- og Aktivitetstilbud | |
| Botiltak Rus og Psykiatri | |
| Byutvikling | |
| Diverse | |
| Ekstern Tjeneste | |
| Familiebarnehage | |
| Finansforvaltning | |
| Helseenheter | |
| Helsehus | |
| Helse og Velferd | |
| Helse- og Velferdssentralen | |
| Hjemmetjenester | |
| Interne Tjenester | |
| Kulturtjenester | |
| Oppvekst og Utdanning | |
| Organisasjon - Interne Tjenester | |
| Politisk | |
| Skole | |
| Label |
Label of the integration edge. |
||
| Master data treatment |
Does the system handle master data. |
||
| Integration Intention |
Describe, in short, the intention behind this integration. |
||
| Integration criticality |
How essential/critical/important is this integration? |
||
| Data flow frequency |
Average information sync interval between involved systems. |
||
| API implemented: |
API used by the integration |
| Integration process: | |
| Planned, but not implemented | |
| Fully implemented | |
| Complexity |
Complexity of the integration. |
|
| Citicality |
Describe, in short, the intention behind the integration. |
|
| Load |
How important/necessary/critical is this integration? |
| System nr. |
What is the provided system number (e.g. ESA is TKS0018)? NB! Only systems managed by Sopra Steria have such a number! If you don't know of any, skip this field. |
|||
| System name |
Please provide name of the system (e.g. ESA or LDAP-bridge). |
|||
| System Description |
Describe the system's usage and function as well as you can. Example about ESA: "EDB Case and Archive is a case and document processing system, used mostly for.... |
|||
| System parts |
What parts does the system consist of? |
|
||
| System Description, Keywords |
Provide some keywords that accurately describe the system or its function. 'Whitespace' and 'enter' keys stores written value. |
|
||
| System Storage/Location |
Choose one... |
|||
| Decommissioned/transitioning |
Is the system transitioning (to be replaced), or being decommissioned? |
|||
| Transitioning info |
Decommissioning details (if relevant). |
|||
| System APIs |
What API s does the system provide? |
|||
| TIP Usage Index |
How much of a 'burden' is this integration on TIP? |
|||
| Number of Integrations |
Total incoming and outgoing integrations. |
| Data Business Description |
Describe typical usage of data. |
|
| Business Criticality |
Very high: Lives may depend on this software. E.g. medical equipment, infrastructure etc.
|
|
| Availability |
To what degree is the software available? Some days? Every day? |
|
| Confidentiality Level |
Describe the confidentiality level of the data processed by the system. |
|
| Organization Type |
What type of organization is this? |
|
| Organization Subtype |
Keywords that describe organization subtype. |
|
| Business User Type |
Who uses this system? |
|
| Access Control Mechanisms |
How is access distributed? Role Based: Automatic access control based on existing business roles. Centralized: Access control based on roles defined in Active Directory (administered by User Support). Distributed: Access control administered directly in application. |
|
| Access Allocation |
Describe how new users get access to the system. |
|
| Authentication TK-employees |
How are Trondheim Kommune's employees authenticated in this system? |
|
| Authentication TK residents |
How are Trondheim Kommune's citizens authenticated in this system? |
|
| Administration User Access |
What routines exist for revoking user access? |
| System Contact Name |
Name of person responsible for system. |
|
| System Contact Mail |
E-mail of person responsible for system. |
|
| System Contact Phone |
Phone number of person responsible for system (8 digits). |
|
| Owner Name |
System owner name. |
|
| Owner Mail |
System owner e-mail. |
|
| Owner Phone |
System owner phone number (8 digits). |
| Data Type |
What type of data does the system process/provide?
|
|
| Data Tags |
Tags that describe data handled by the system. |
|
| Data History (Volatility) |
How frequently is the data updated? |
|
| Contains Personal Sensitive Data |
Does the information processed by the system contain sensitive personal data? Check for yes. |
|
| Sourcecode |
Open source: The system's source code is available to everyone.
|
|
| Files and location |
Where is data stored?
|
|
| Network Zone |
In what network zone does the service exist?
|
|
| Database Type |
What type of database does the software use for data storage (if any)? |
| New/changed! |
This API is new or changed, and has not been approved by Admin. |
|
| Name |
API name. |
|
| API Description |
Describe API with a short text. |
|
| API Specification |
Eg. Noark. |
|
| Transport Protocol |
What protocol describes the transport of the data. |
|
| M2M |
Is this api designed for machine-to-machine interaction? |
|
| Version |
What version of the API is used one. |
|
| API documentation URL |
Link to documentation (for example Swagger). |
|
| Authentication |
What sort of security is used to secure that the client has access. |
|
| Input Format |
What format does a request body have? |
|
| Output Format |
What format does a response body have? |
|
| Data Type |
What sort of data does this API handle? Permanent (master)? Temporary (transaction)? |
|
| Message Exchange Pattern |
How does this API work? E.g. do you wait for a response, or is there a callback? |
|
| Authentication Mechanism |
What type of authentication does the API use? |
|
| Endpoint Environment |
Is the API linked to in Test, QA or Production? |
|
| WSDL URL |
WSDL documentation of this API (if applicable). |
|
| Endpoint URL |
Where can this API be accessed (root)? |
|
| Integrity Level |
How essential is this API? |
|
| Security Level |
How protected is the data handled by this API? |
|
| Confidentiality Level |
How confidential is the data handled by this API? |
|
| Tags |
Add some tags that describe this API. |
|
| Org Unit Title |
Group title/description. |
|
| Org Identifier |
Used internally to identify the group. |
|
| Color Specification |
How group is displayed in integration view (color). |
| Search for existing user |
Only checks the database for existing admins and moderators |
||
| User email |
Mail must end with "@trondheim.kommune.no" |
||
| Role |
Admin: Top level access. Can administrate other users and approve moderators edits.
|
||
| Name |
Self-explanatory |
||
| Owner Phone |
Must be norwegian 8 digit number |
| User email |
Mail must end with "@trondheim.kommune.no" |
|
| Role |
Admin: Top level access. Can administrate other users and approve moderators edits.
|
|
| Justification |
Moderators may edit the network. Why should you have access to this functionality? |
|
| Name |
Self-explanatory |
|
| Owner Phone |
Must be a norwegian 8 digit number (without spaces) |
A request has been sent to the system administrators and will be processed at their convenience. Please
return later.
If urgent access is required: Contact the system
admins
| There are no requests at this time. | |||
|---|---|---|---|
| Name: | Email: | Phone: | Role: |
| System | API | Tags |
|---|
| System | Description | Integrations |
|---|
| System | Description | Integrations |
|---|
| Change Type | Date of Change | System | Type | Changes | Author |
|---|