Developers

Developer accounts are used to log into the Developer Console (opens in a new tab) and administrate Projects. When you sign up for a ZapEHR account (opens in a new tab), you receive a password reset email and become the first Developer in a new Project. As the first Developer in your Project, you are granted full permissions.

Developer accounts exist above the Project level to facilitate access to multiple Projects. Projects are completely independent from each other, having their own separate FHIR store, Applications, Users, etc. You might have separate Projects for testing, staging, and production environments.

ZapEHR information architecture, a chart with 'ZapEHR Platform' pointing to 'Developer (you!)'. 'Developer' points to 'Your Project (Telemed, EHR-lite, etc)'. 'Your Project' points to 'Z3', 'App', 'Zambda', 'User', 'Telemed', 'M2M', 'Messaging', 'Role', 'FHIR'. 'Role' points to 'Developer', 'M2M', and 'User'.

Invite your team of Developers to some or all of your Projects, with the level of permissions in each that is appropriate for them. For example, you may give only a subset of your Developers access to your production environment, and of those, you might give some read-only access and others more substantial permissions.

Invite a Developer

You can invite your team to your Project in the Developer Console here (opens in a new tab).

Invite a Developer from the Developer Console

When inviting a Developer, these fields are required:

Email — The invited Developer will receive an invitation email at this address with a link prompting them to set their password.
Practitioner — Provide a FHIR Practitioner (opens in a new tab) resource which will be created to represent the developer in the FHIR store. As the Developer creates and updates FHIR resources, Provenance resources are automatically created which credit this Developer's FHIR Profile. You can store as much or as little information about the Developer in the Practitioner resource as makes sense for your use case.
Access Policy / Roles — Access policies grant the Developer access to the services and resources that they need. You can grant a Developer their own one-off inline access policy, or you can assign Developers to one or more Roles. Roles are a convenient way to group access policies together and assign them to multiple actors.

As a security best practice, follow the principle of least privilege (opens in a new tab) by giving the Developer account access to no more than what they need to do their job. Learn more about access policies in ZapEHR.

Manage Developers

Besides inviting Developers to your Projects, you can also list, get, update, and delete Developers using the API, Typescript SDK, and Developer Console.

Grant Permission to Act on Developers

In order for actors to be allowed to act on Developers, they must be assigned an access policy with appropriate permissions.

Examples

Here are some examples of access policies you can use to grant permissions to act on Developers.

Permission to do all actions over all Developer resources in the Project.

{
  "rule": [
    {
      "action": "*",
      "resource": "IAM:Developer:*",
      "effect": "Allow"
    }
  ]
}

Read-only permissions over all Developer resources in the Project.

{
  "rule": [
    {
      "action": ["IAM:ListAllDevelopers", "IAM:GetDeveloper"],
      "resource": "IAM:Developer:*",
      "effect": "Allow"
    }
  ]
}

Permission to invite, list, get, and update Developers in the Project.

{
  "rule": [
    {
      "action": ["IAM:ListAllDevelopers", "IAM:GetDeveloper", "IAM:UpdateDeveloper", "IAM:InviteDeveloper"],
      "resource": "IAM:Developer:*",
      "effect": "Allow"
    }
  ]
}

You might give this access policy to a Developer so they can just get the configuration of their own Developer resource:

Read-only permission over a single Developer in Project.

{
  "rule": [
    {
      "action": "IAM:GetDeveloper",
      "resource": "IAM:Developer:23357fe8-3368-484d-a040-a6e672d59de1",
      "effect": "Allow"
    }
  ]
}

Developer Access Policy Actions

The following table details the different actions which grant permission to interact with Developer resources.

Service	Action	Resource Type	Description	Minimum Scope
IAM	InviteDeveloper	Developer	Grants permission to create an invitation to join the principal project as a developer user
IAM	UpdateDeveloper	Developer	Grants permission to update a developer in the project.
IAM	GetDeveloper	Developer	Grants permission to view details of a dev user within the principal project
IAM	ListAllDevelopers	Developer	Grants permission to list all users within the principal project	*
IAM	RemoveDeveloper	Developer	Grants permission to remove a developer from the project.

Additional Resources

IAM M2M Clients