Yosemite Crew
Replies: 1 comment
-
|
@SurbhiS8YC - This flow is worth checking out |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Pet service businesses — whether veterinary clinics, groomers, sitters, or breeders — rely on consent forms for legal, ethical, and operational protection. Today, these are often handled with paper forms or ad-hoc PDFs. Yosemite Crew can offer a Consent Management Module where businesses can create and manage customizable digital consent forms that pet owners can sign electronically. These signed forms would be securely stored, linked to the pet’s record, and auditable.
To maximize adoption and compliance, the e-signature feature must align with:
This ensures global legal recognition of signed consents.
Templates: Should Yosemite Crew ship with standard templates (e.g., surgery consent, grooming waiver, sitter emergency authorization), or just provide a form builder?
Customization: Should businesses be able to add their own logo, disclaimers, and clauses to forms?
Signature methods: Should we support typed signatures, drawn signatures, or external e-sign APIs (DocuSign, HelloSign)?
Audit trail: What events should be logged? (IP, timestamp, version of form signed, who signed).
Storage & linkage: Should signed forms be stored per visit, or globally in the pet/owner profile?
Cross-service forms: Should one module cover all business types (clinic, sitter, groomer, breeder), or separate by service?
Owner access: Should pet owners have a portal to view/download their signed consents?
Language & jurisdiction: Should forms support multi-language templates and jurisdiction-specific compliance (e.g., GDPR)?
Design
Form Builder: Drag-and-drop builder for businesses to create or customize consent forms.
Templates: Preloaded standard templates (e.g., General Treatment Consent, Anesthesia Consent, Grooming Waiver, Boarding Liability Release, Breeder Sale/Health Guarantee).
Digital Signature should have:
Audit Trail: Store metadata (IP, device, timestamp, form version, signer ID).
Assignment: Forms can be linked to appointments, treatments, or sales.
Owner Access: Signed copies visible in Pet Owner mobile app + downloadable PDF.
Business Dashboard: Track outstanding, signed, and expired consents.
Multi-Language Support: Businesses can issue forms in local language.
Proposed flow use case 1: Pet business wants to get a document signed by pet owner (most consents (treatment, grooming waiver, sitter emergency auth, breeder sale).**
Pet Business prepares & assigns → Staff selects a template (e.g., “Grooming Waiver v3”) in YC Web, pre-fills fields (pet, date, services), and assigns it to an owner (email/phone) and pet/appointment.→ Yosemite Crew creates a ConsentInstance (status=pending) and generates a secure sign link.→ YC sends invite→ Server sends the owner an email/SMS link: customlink/{token and includes due date (e.g., must sign before appointment)→ Owner authenticates (OTP/KBA)→ Owner opens the link → Yosemite Crew prompts OTP (email or SMS) and/or KBA (e.g., pet name, last invoice).
→ Server verifies → sets a short-lived sign session.→ Owner reviews & signs→ Page shows the exact form text + pet/context + ESIGN/UETA/eIDAS/ZertES consent checkbox. → Owner draws or types signature → clicks Sign.→ YC composes the final PDF & seals → Backend pulls the template version used, merges form data, embeds the signature image, and (optionally) applies a cryptographic → PDF signature (tamper-evident). → Computes SHA-256 of the final PDF.
Use case 2: Pet business wants to get a document signed by pet owner with Counter-signing i.e. Owner signs, then Business signs (breeder bill of sale, surgical estimate that requires clinic sign-off)
Pet Business prepares & assigns → Staff selects a template (e.g., “Grooming Waiver v3”) in YC Web, pre-fills fields (pet, date, services), and assigns it to an owner (email/phone) and pet/appointment.→ Yosemite Crew creates a ConsentInstance (status=pending) and generates a secure sign link.→ YC sends invite→ Server sends the owner an email/SMS link: customlink/{token and includes due date (e.g., must sign before appointment)→ Owner authenticates (OTP/KBA)→ Owner opens the link → Yosemite Crew prompts OTP (email or SMS) and/or KBA (e.g., pet name, last invoice).
→ Server verifies → sets a short-lived sign session.→ Owner reviews & signs→ Page shows the exact form text + pet/context + ESIGN/UETA/eIDAS/ZertES consent checkbox. → Owner draws or types signature → clicks Sign.→ YC composes the final PDF & seals → Backend pulls the template version used, merges form data, embeds the signature image, and (optionally) applies a cryptographic → PDF signature (tamper-evident). → Computes SHA-256 of the final PDF. → Countersign request created for a designated staff role. → Staff reviews → clicks Countersign (draw/typed or org seal). → Backend produces final PDF v2 (both signatures), new SHA-256, and appends to the AuditLog. → Status → fully-signed; both parties notified.
Development
Testing
Pet businesses: Unified system for all consent forms → no paper, less admin, legally sound.
Pet owners: Easy digital signing, all consents accessible in one place.
Platform: Competitive differentiation by offering global e-sign compliance in pet care context.
Beta Was this translation helpful? Give feedback.
All reactions