> For the complete documentation index, see [llms.txt](https://docs.griaule.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.griaule.com/gbs/en/applications/babyid.md).

# BabyID

## What BabyID is

BabyID is a web app (PWA, installed directly from the browser) used by maternity ward or registry office operators to record the biometric collection of a newborn at the time of civil registration.

In a single registration, the app brings together: the baby’s birth document (Birth Certificate or DNV), the guardian’s signature, the photos and documents of the present parentage figures (mother, father, legal representative, or other), and the baby’s biometrics — face and fingerprints.

This manual describes the collection app, the first step in this chain. The app runs in the browser and is installed on the phone from Google Chrome itself, with no app store. After installation, it updates itself and keeps working without a connection.

### BabyID does not register the baby’s name, date of birth, or CPF

{% hint style="info" %}
This version is for collection only. The app gathers the images and biometrics, creates a biometric transaction, and sends it to the institution’s server. Civil data is filled in later, by another operator, directly in SMART — which even extracts the CPF or DNV number from the photographed document image itself. The link between the collection on the phone and the civil registration is a technical identifier (a UUID) generated at the start of the process, not a name or document number.
{% endhint %}

In this version, there is no biometric verification or comparison: no duplicate search is performed. The app only collects and forwards.

The app guides the registration in three steps, in this order: **Documents**, **Parentage** and **Baby registration**. When tapping **Send**, in the last step, the registration is saved on the device itself — in a protected local queue — and the screen returns to the start, freeing the operator immediately. Sending to the server happens automatically, in the background, as soon as there is a connection, with no separate screen and no additional action required. Details are in section 7 — *What happens when sending*.

***

### Before you start

### Install LiveCapture Connector

LiveCapture Connector is an app that gives BabyID access to the camera resources needed for biometric collection.

BabyID itself provides an installation button whenever needed, such as during the device’s first setup.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2FDnj4fyGZYYqm44YaU3A4%2Fimage.png?alt=media&amp;token=466ab958-dc08-424f-a716-033a1e2807a3" alt=""><figcaption></figcaption></figure>

After installing it, open the app and grant the requested permissions. When it is running, a notification will appear in the device’s notification bar indicating that it is running and ready to perform collections.

### Have these ready before opening a registration

* **Baby’s document:** the Birth Certificate or the DNV. Either one is enough.
* **Document from at least one parentage figure:** with front and back, because the app asks for both sides. Up to four can be registered (mother, father, legal representative, and other).
* **Physical presence of that parentage figure:** the app takes a face photo on the spot, using the device camera. Importing photos is not allowed.
* **The baby present:** the face and fingerprints are collected live, also through the device camera.
* **What is the CIN pickup location.** The list of locations is loaded from the server automatically. For it to appear, you must have signed in to the app with internet at least once. After that, it is saved on the device and works even offline.
* **System access account.** Access to the app is done through the institution’s identity provider (corporate single sign-on). You must be online to log in for the first time. After logging in, collection can continue even if the connection drops.
* **Battery and space on the phone.** The process includes several photos.

{% hint style="info" %}
**What is saved automatically:** each confirmed collection (one fingerprint, one face photo, one document) is saved on the device as soon as it is confirmed. You do not need to finish the entire registration to avoid losing what has already been done. Closing the app, losing the connection, or reloading the page does not erase what has already been collected and confirmed. When reopened, the registration continues from where it stopped. Only the "Discard registration" button (✕) or logging out deletes an in-progress registration, as per *Interrupt a registration*.
{% endhint %}

{% hint style="warning" %}
**No fingerprint reader is needed.** BabyID does not require a dedicated biometric reader: fingerprints are collected by the phone’s own camera, in a contactless mode, just like the face and documents. The operator photographs the baby’s little fingers following a guide on the screen.
{% endhint %}

***

## Log in to the app

BabyID does not have its own login screen. When you open the app without an active session, it automatically redirects to the institution’s authentication page.

* **No connection at the moment**, the app shows the message "No connection. You must be online to log in. The collections saved on this device are محفوظ and will be sent later." and waits for the network to come back to try again automatically.
* **With connection**, the organization’s login screen is displayed.
* **After authentication**, the app returns to step 1 of the registration, or to the point where a registration was in progress.

After logging in, the session remains valid on the device even offline for a while, and collection continues normally. If the session expires without a connection, this does not block collection, only sending to the server, which is then done in the background. If a new login is needed for that sending, the app asks automatically when the connection returns, without losing what has already been collected. The exception is a collection that was open and not confirmed at the exact moment of expiration, which must be done again.

{% hint style="success" %}
**Always use your own account.** Registrations are recorded under the name of whoever is logged in on the device.
{% endhint %}

### If "No permission to register" appears

Access to BabyID depends on a specific permission to create registrations. An account may be authenticated correctly and still not have this permission. In that case, instead of the normal collection flow, the message "No permission to register" appears.

Ask the system administrator at your institution to grant access. As soon as the permission is granted, the collection flow appears automatically, without needing to log out and back in.

***

## Interface elements

The blue header is always at the top and shows only:

* **"BabyID" and the app version**, on the left.
* **A circle with a person icon**, on the right. Tap to open the account menu.

Just below the header, in the three registration steps, there is a progress bar with three marks and the text "Step X of 3 - Step name". The blue mark is the current step, the green ones are already completed, and the gray ones have not been reached yet.

Above this bar, outside the blue header, a line with up to two buttons may appear:

* **"‹" (Back):** goes back to the previous step. Appears starting at step 2.
* **Red "✕" button (Discard registration):** appears at any step as soon as anything has been collected in the current registration, even if only the chosen pickup location. In a completely blank registration, this button does not appear.

### The account menu

Tap the circle in the header. It opens a full-screen view, not a dropdown menu, with:

* An avatar with the operator’s initials, or a generic icon if the name is not available, and the name.
* The "Log out" button.

Sending to the server is automatic and has no separate screen.

{% hint style="warning" %}
**Logging out discards the current registration.** When tapping "Log out" with an unfinished collection on the screen, the data collected up to that point is deleted from the device. Registrations already **sent or in the sending queue** are not affected, only what is still being filled in on the screen.
{% endhint %}

***

### The step-by-step registration

#### **Step 1 of 3 · Documents**

In this step, the CIN pickup location, the baby’s document, and the guardian’s signature are entered.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2FdtnDE4Yd6Q8BpPlAu0N8%2Fimage.png?alt=media&amp;token=61d849df-6851-4f23-984d-6e2bbfc1723f" alt=""><figcaption></figcaption></figure>

Choose the pickup location

1. Tap the field "Select pickup location".
2. Type part of the name to filter the list. Opening the field without typing anything shows the full list.
3. Tap the desired location. It disappears from the list with a "✓" beside it once selected.
4. To change it, tap the gray "✕" that appears inside the field and choose again.

If there are no options for the typed text, "No options available" appears.

#### Photograph the baby’s document

1. Under "CAPTURE", tap "Capture document".
2. The device camera opens with a framing guide on the screen. It is the same full-screen collection view, "Live Capture," used for the app’s other photos. Collection is done with the two concentric circles button in the bottom-right corner. It is the same on all collection screens, as is the circular arrow used to redo a collection.
3. Align the document within the guide. The image is cropped exactly by the guide, not by the document’s real edges, so a crooked document or one outside the guide will be cropped incorrectly.
4. Confirm the photo. The document block turns green, shows a thumbnail of the photo taken, and the text changes to "Document captured - tap to capture again".
5. Just below, under "Select the type of captured document," tap "Birth certificate" or "DNV". Neither one is preselected.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2FPCZS4WGfEFpEcN3aUHZV%2Fimage.png?alt=media&amp;token=9f316e6a-3576-41ad-84c0-70ba87d4a4f3" alt=""><figcaption></figcaption></figure>

#### Collect the signature

1. Tap the "Guardian signature" block.
2. The collection screen opens with the warning "Turn the phone sideways". Rotate the device.
3. Sign with your finger in the drawing area.
4. Tap "Clear" to erase and sign again, or confirm to continue.
5. After confirmation, the block shows "Signature captured - tap to redo".

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2FIqDG8GO5wxXIA4WwWhGh%2Fimage.png?alt=media&amp;token=f6325fa3-eb95-41cf-9ad2-4f071f186914" alt=""><figcaption></figcaption></figure>

The step is considered complete when the pickup location, the baby’s document, and the document type have been entered. Only then is the "Next" button in the footer enabled. The signature is not required to move on. While something is missing, the button stays disabled with no visible warning on the screen. The reason is announced only to screen readers.

***

#### Step 2 of 3 · Parentage

In this step, the face and document of each parentage figure are collected. The screen shows four cards: "Mother", "Father", "Legal representative", and "Other".

Each card has a counter that starts at "0/2". The two items are:

* the **face** of the person;
* the **document**; it only counts when both front **and** and back have been collected. It is one item, not two.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2Flm13JcD963hZ4dn3TKDj%2Fframe_elementos_interface.png?alt=media&amp;token=875a3285-a6e6-4351-87f8-0fd95b7712de" alt=""><figcaption></figcaption></figure>

**For each present parentage figure:**

1. Tap "Perform captures" on the person’s card.
2. The face capture opens ("Face capture"). Frame the face and take the photo.
3. Confirm. The sequence automatically advances to "Document - front (1 of 2)".
4. Photograph the front of the document and confirm. The sequence advances to "Document - back (2 of 2)".
5. Photograph the back and confirm.

**The card is considered complete** when the counter reaches "2/2", the card turns green, and the button changes from "Perform captures" to "Captures completed".

Fill in only the cards for the parentage figures present in the case and leave the others at "0/2".

{% hint style="warning" %}
**The sequence cannot be interrupted.** If you close the capture with the "✕" midway through, anything not yet confirmed in that sequence is lost and the card must be started over.
{% endhint %}

**The step is considered complete** when at least one parentage figure has the card at 2/2. It is not necessary to complete more than one.

***

#### Step 3 of 3 · Baby registration

In this step, the newborn’s biometrics are collected.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2F3BQxMP4zY7wQqmmXz9Al%2Fimage.png?alt=media&amp;token=47388b71-b0dc-4add-8a2d-ff3d9be338b8" alt=""><figcaption></figcaption></figure>

**Twin baby**

Check the "Twin baby" box if applicable. This marking is only a declaration recorded with the registration, whether selected or not, and does not change the rest of the collection flow.

**Facial biometrics**

1. Under "Biometrics", tap "Facial biometrics".
2. The camera opens with an oval guide on the screen and a quality bar.
3. Frame the baby’s face within the guide and wait for the quality to rise.
4. Collection happens automatically as soon as the quality becomes good and remains stable for a moment. There is no need to tap any button; just keep the baby’s face framed and still. Even so, the collection button remains visible on the screen and can be used to collect before the automatic trigger.
5. Check the captured photo. If it is not good, tap to redo it.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2Fhq11kRQVCWd4Xy3JMttK%2Fimage.png?alt=media&amp;token=e6e1b0f9-c75b-4822-8da7-675e5922595e" alt=""><figcaption></figcaption></figure>

**The process is considered complete** when the block turns green and the text changes to "Captured via camera - tap to redo".

#### Fingerprint biometrics

1. Tap "Fingerprint biometrics".
2. The sequential capture screen opens, with the map of both hands at the top. The sequence starts with the right hand, from thumb to little finger, then moves to the left hand in the same order.
3. Place the requested finger in the camera and wait for the app to focus.
4. Capture the finger. If the quality is not good, it is possible to capture the same finger more than once, and up to three attempts are saved per finger. Use the circular arrow button (Recapture) to redo the current finger, or tap the icon for that finger directly on the hand map to go back to it.
5. If a finger cannot be captured, for example because of a bandage, tap the arrow to the right (Skip). A reason is requested (amputated, bandaged, damaged, impossible to obtain print, or other) before the sequence advances.
6. Tap "Next" to move to the next finger.
7. Repeat for all possible fingers.

As soon as at least one finger has been collected, the "Finish capture" button appears in the footer. Tap it at any time to end the sequence. It is not necessary to complete all ten fingers.

<figure><img src="https://3757157672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7Bx0xNdsdGHpCZ20yxbn%2Fuploads%2F5atuAJmQb95vielKclsg%2Fimage.png?alt=media&amp;token=8f730423-c650-415a-b6c7-b7966397b9fd" alt=""><figcaption></figcaption></figure>

When you leave the fingerprint screen and come back later, the fingers already collected are still there: the sequence does not start over from scratch.

"Finish capture" appears only after at least one fingerprint has been collected. Fingers skipped on their own, with no real fingerprint, do not enable ending the sequence.

The step is considered complete when the "Facial biometrics" and "Fingerprint biometrics" blocks are filled in.

The registration can be sent when the baby’s face and at least one real, non-skipped fingerprint have been collected. Only then is the "Send" button in the footer enabled. While something is missing, the button remains disabled with no visible warning on the screen.

## Good captures

A bad capture means redoing the registration later. It is worth spending ten extra seconds.

### For all captures

* Look for good, even lighting. Avoid backlight.
* Do not use flash directly on laminated documents or on the baby’s face.
* Hold the phone with both hands and wait for the image to stop shaking.
* Clean the camera lens before starting.

### Document

* Place the document on a flat surface, without folds.
* Align the document within the screen guide. The photo is cropped exactly by the guide, so a crooked document or one partially outside it will be cropped incorrectly, even if the original image is correct.
* Photograph from above, with the phone parallel to the paper.
* Check that the names and numbers are readable before confirming.

### Face (parentage figures and baby)

* The screen shows quality in three levels: "Insufficient" (red), "Adequate" (yellow), and "Excellent" (green), with a guidance message below.
* At "Insufficient" the capture is not allowed. Improve the light and center the face.
* For the baby, capture tends to trigger on its own as soon as quality reaches "Excellent". Wait for a calm moment, without forcing the position.
* Entire face inside the guide, looking at the camera, without a cap, sunglasses, or a hand in front.

### Fingerprints

* The baby’s finger must be clean and dry.
* Gently straighten the little finger and keep it still during capture.
* If the finger slips or the capture is poor, use the circular arrow (Recapture) before moving to the next finger.

## What happens when sending

### When tapping "Send"

In step 3, tapping "Send" shows the screen "Recording the process for sending...". The registration is saved on the device at that moment.

> **Do not close the app during this message.** It is quick, but wait for the next screen to appear.

When it finishes, the "Done!" screen appears, with the message "The registration was processed and saved successfully on the device." and the button:

* **"Start new process":** clears the screen and returns to step 1, ready for the next baby.

There is no back button on this screen.

### The real sending happens automatically, in the background

As soon as the device has a connection, pending registrations are sent to the server automatically, with no action required by the operator. There is no queue screen or resend button. The result is indicated by a notice in the top-right corner of the screen:

| Message                                                     | When it appears                                                                                    |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| "Pending processes sent."                                   | At least one registration in the queue was sent successfully.                                      |
| "Failed to synchronize a process; we will try again later." | A specific registration failed to send: it remains in the queue and will be retried automatically. |
| "Synchronization failed."                                   | The sending process as a whole could not even read the local queue. Rare situation.                |

If the session has expired at the time of sending, the app asks for login again, without deleting the queue, and then resumes sending automatically.

***

## Interrupt a registration

The red "✕" button (Discard registration) appears at any step of the registration, as long as something has already been filled in: the chosen location, a photo, a fingerprint, the twin marking. In a completely blank registration, the button does not appear.

1. Tap the red "✕".
2. The "Abandon process" box appears, with the warning "Are you sure you want to abandon the process? All data will be lost".
3. To delete everything, tap the light "Yes" button at the top of the box.
4. To continue the registration, tap the red "Cancel" button just below.

When you confirm discarding, "Process discarded." appears and the app returns to step 1 with everything blank.

**What is lost:** the pickup location, the baby’s document and its type, the signature, all faces and documents of the parentage figures, the twin marking, the baby’s face and all fingerprints.

Registrations that have already been sent to the local queue are not affected by discarding. This button only exists during collection, before sending.

Other ways to interrupt:

* **Log out** also discards an in-progress registration, but not one that has already been sent. See *The account menu*.
* **Closing the app or losing the connection** does not erase anything that has already been confirmed. Only an open collection that has not yet been confirmed at that exact moment is lost.

## Frequently asked questions

**Why is there no field for the baby’s name, date of birth, or CPF?** Because BabyID handles biometric and document collection. Civil data comes from the images of the photographed documents and is resolved later in the chain, in SMART.

**Do I need both the Birth Certificate and the DNV?** No. Either one is enough. Photograph the available document and then tap the corresponding button to indicate which one it is.

**I entered the wrong document type after photographing it. Do I need to photograph it again?** No. Just tap the other option, "Birth certificate" or "DNV". Changing it only corrects the label, without requiring a new photo.

**What if only the mother is present?** Fill in the "Mother" card and leave the others at "0/2". The app allows you to move on with just one complete parentage figure.

**The face capture does not trigger. What do I do?** It remains blocked while the quality is "Insufficient". Improve the lighting and center the face. Capture tends to trigger automatically as soon as the quality reaches "Excellent".

**Do I need to collect all ten fingers?** No. Just one real, non-skipped finger is enough to send the registration. Collect as many as you can and tap "Finish capture".

**I captured the wrong finger or a poor-quality finger. How do I fix it?** Tap the icon for that finger on the hand map to go back to it, and then tap the circular arrow (Recapture).

**What does it mean when a finger appears in orange on the map?** It may be a skipped finger, or a finger that the system suspects is a copy of another already captured. Hold your finger on the icon to see the explanation and consider recapturing if it is a duplicate.

**I signed incorrectly and already confirmed the signature. How do I do it again?** Inside the signature screen, use "Clear" before confirming. After leaving the capture screen, tap the "Guardian signature" block again in step 1 to sign once more.

**I can’t sign right now. Can I skip it?** The signature is not required to move past step 1. If you do not want to collect it now, just do not open the "Guardian signature" block.

**I lost the connection halfway through the registration. Did I lose everything?** No. Each confirmed capture is already saved to the device immediately. Finish the registration normally and tap "Send". It is saved locally even without internet and is sent automatically to the server as soon as the connection returns, with no need for manual resending.

**How do I know if my registration has already reached the server?** By the notices that appear in the top-right corner. "Pending processes sent." confirms that something was sent. If there is no failure notice, the app keeps trying automatically in the background.

**Can I close the app during the "Recording the process for sending..." screen?** Avoid it. Wait for the "Done!" screen to appear.

## What happens next

After sending, the BabyID server creates the process in SMART with the documents and biometrics. The baby’s civil data is filled in at that stage, by another operator, already in SMART. None of this requires action in BabyID.

## Glossary

* **Live Capture:** name of the full-screen collection screen used for face, document, signature, and fingerprints.
* **Parentage:** each person linked to the baby in the registration, among "Mother", "Father", "Legal representative", and "Other".
* **DNV:** Live Birth Declaration, a document issued by the maternity ward, an alternative to the Birth Certificate.
* **CIN:** National Identity Card. The "Pickup location" is the place where it will be picked up, and the list of locations is automatically synchronized with the server.
* **SMART:** the system to which BabyID automatically forwards the process created from the registration.
* **"Insufficient", "Adequate", "Excellent":** the three quality levels for face capture. At "Insufficient" the capture is blocked.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.griaule.com/gbs/en/applications/babyid.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
